Jeremy Edberg

How do you #SRE? take this year’s Catchpoint survey and contribute to better tools and practices for reliability engineers everywhere

1

Whose CIDR is it anyway? A look at CIDR block ownership from a RIR-, country-, and organization level. Originally presented at RIPE88, now landing on an internet near you via my blog (with added graphs and links to the data and tools). (The answer is: if not the DoD's, then it's likely Amazon's.) https://lnkd.in/dv3hwg3E

14

1 Comment

One thing Coroot is great at is getting Observability quickly when you had none, and you need to fix things quickly! https://lnkd.in/dFQxPunJ #coroot #observability

2

Yes, our engineering team really did run CockroachDB on spot instances. I can explain. Our customers are running mission-critical workloads across clusters with hundreds of nodes, and it is paramount that our engineering team can test at a similar scale. But testing at this scale can get expensive. We need to be able to meet our customers where they are, but we also need to be able to control our costs as an organization. Spot instances can create significant savings over VMs, with savings of up to 90% a year. What if we could run long-running clusters on them? Besides saving money we would be able to leverage the unpredictable nature of Spot Instances for some exciting chaos testing! The effort to keep CockroachDB available and workloads predictable while nodes are rapidly disappearing would help us harden CockroachDB. Adam Storm's blog captures our entire journey, diving into the methodologies we chose, lessons learned, and yes—even the impact of preemptions. At Cockroach Labs, our engineering culture doesn't just push the boundaries of what's possible with a mission-critical database; it fuels technical innovation across the board. The results are fascinating, so give it a read if you're curious about running a distributed database on spot instances! Special thanks to Bilal Akhtar, Herko Lategan, David Taylor BabuSrithar M, Sambhav Jain, Shailendra Patel, Vidit Bhat, and Bhaskar Bora https://lnkd.in/et-aEjxm

78

4 Comments

🎃The October issue of #CheckpointChronicle is now out 🌟 It covers Ververica's Fluss, #ApacheFlink 2.0, Iggy.rs, Strimzi's support for #ApacheKafka 4.0, tons of OTF material from Jack Vanlightly, Christian Hollinger's write up of ngrok's data platform, nice detail of how SmartNews use #ApacheIceberg with Flink and #ApacheSpark, a good writeup from Sudhendu P. on #ApachePolaris, notes from Kir Titievsky 🇺🇦 on Kafka's Avro serialisers, and much more! https://lnkd.in/djc-HERy

18

Infusing resiliency into our applications typically introduces complexity. AWS Step Functions (SF) have been my go-to for managing more complex workflows, shifting some of that complexity to a managed service and away from our code. However, adopting SF comes with challenges and may not be a viable option depending on your context. The concept of persistent execution with Temporal is an interesting alternative to consider. You can check more here:

20

The legacy event indexing services (e.g. Datadog, Sumo Logic, etc.) need to make some big changes soon. Nextgen event storage and indexing services (e.g. Observe, Inc. and Axiom ) that are schema-on-read and backed by super cheap object storage (or snowflake), and are therefore MUCH cheaper, are going to absolutely eat their lunch. Nevermind the move to de-emphasize logs in general and focus on traces and high-cardinality data (e.g. honeycomb.io) that’s eating their lunch from the other side. And no “we now offer a cheaper tier and not all of your logs will actually be fast indexed, and hooray now you need to manage what is where” isn’t the answer.

22

2 Comments

I invite you to join me at the Seattle Postgres 2024 Conference! I’m excited to be one of the speakers, presenting two sessions: 1. Converting Your Schema from Oracle, MSSQL, and MySQL to PostgreSQL in Minutes with DataWharf 2. Tips and Tricks for Developers Moving to PostgreSQL I hope to see you there! #PostgreSQL #PostgresConf #Database #OpenSource #SeattleTech

19

6 Comments

After talking about Operability and Observability, I'm moving to my next big word, Controllability. In testing we usually focus on what we want to do (the Operability part), and what we want to see (observability). The last two attributes of testability discuss the "how" - How we're going to run the test, its environment, and how much we need to work to just get the test going. Here's the Controllability post: https://lnkd.in/dwKJwT-j Here's The operability post (when I still thought it was going to be 3 posts): https://lnkd.in/dAaispCn And the Observability post (when I got better): https://lnkd.in/dkEtKUJY #Testability #Testing #Development #microservices #apitesting

3

New Episode: 280: Evidently, The Cloud Pod Was Always Right https://bit.ly/3NU6UVL Evidently the newest episode of The Cloud Pod is available wherever you get your podcasts, and evidently you are not going to want to miss this one! More nuclear deals, some security shenanigans over at Microsoft, and - just in time for Halloween - we add another tombstone to the 2024 graveyard. It’s RIP to AWS CloudWatch Evidently, which genuinely had one of the worst names in the biz. In AI news we’ve got more staffing changes, Claude 3.5 Sonnet announcements, and even some new tools you’ll definitely want to hear more about for Gemini. Episode 280 out now! #aws #gcp #azure #cloud #cloudpodcast #podcast

13

Use Firebase Cloud Functions Generation 2 and Vonage Messages API to build a messaging system 💬 Receive messages via Vonage webhooks 📥 Queue them in Realtime DB 🤖 Automatically respond using Messages API. Amanda Cavallaro shows how! #mycompany #firebase https://gag.gl/NcXeME

3

🎙️Got a chance to chat with Gwen (Chen) Shapira on building Nile, a multi-tenant *first* database. This was such a fun conversation: ranging from the architecture of Nile to tackle the ubiquitous problem of multi-tenant sharding in a scalable way, Gwen's experience building cloud services at Confluent, and what it means to build a database to support modern RAG techniques in the age of AI. Full episode in the comments!

27

1 Comment

I'm speaking at SREday San Francisco 2024! Join me on June 22nd for a day full of Site Reliability, DevOps and Cloud! Keynote: Achieving DORA outcomes by building reliability capabilities into your platform Infrastructure breaks, but systems can persist! We really want systems that withstand unavoidable failures. Abstractly, we understand that. In this talk, Steve presents concepts like spanning failure domains and using generic mitigations, as well as introducing a lab environment where teams can experiment with these directly and a community where we can discuss it all, memes and all. Grab a ticket with 20% off with my code STEVE20. https://lnkd.in/gZAdxes7 #SREday #SiteReliability #DevOps #Cloud

157

5 Comments

If you're at #MSIgnite, this session with Eric & Brendan about open source for AI development should be good.

1

Check out Infostrux Engineering latest blog post https://lnkd.in/gT63tydN, where Balkaran Brar covers a Layered Terraform Architecture. Our Engineering team continues to publish weekly articles in our engineering blog around many different topics, including Data Engineering and Platform Engineering, and Snowflake #terraform #infostrux #cloudarchitecture #snowflake

13

Object storage direct-write Kafka topics are coming to Confluent. In data system design, cost is a kind of unstoppable force that rewrites architectures every decade or so, and that is happening right now for high-volume streams. https://lnkd.in/dHRFnrMB

39

1 Comment

Absolutely love this! Please watch if you have time. I think this short video does a wonderful job briefly explaining the importance of the Cloud Native Computing Foundation (CNCF), which Taylor D. does a wonderful job describing. I also think it helps shed light on how community is likely to play an increasingly important role in (1) software development and (2) ecosystem development for the future, *especially* in the era of Cloud and AI!

9