
Five nines uptime without developer burnout
About this episode
Like other folks we’ve talked to on the podcast, Chronosphere was born out of work pioneered at Uber. When you can’t find solutions to help you scale, sometimes you have to build them.
Everything in Chronosphere was built from scratch, from the ingestion tier to the query layer. If you’re going to build something cloud native from the ground up, the clear choice for the team was Go.
Cloud native observability changes the way developers interact with their code in production. Infrastructure is more complex, dev and test environments are gone, and data increases massively while data sources are more ephemeral.
Congrats to david, who won a lifeboat badge for their answer to Can we convert a byte array into an InputStream in Java?
See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Get every episode summarized
Each time The Stack Overflow Podcast publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from The Stack Overflow Podcast

Connecting the dots for accurate AI
The Stack Overflow Podcast

AI giveth and AI taketh CPU
The Stack Overflow Podcast

What (un)exactly do you mean by semantic search?
The Stack Overflow Podcast

Time is a construct but it can still break your software
The Stack Overflow Podcast