Software Reliability Engineering

1 readers

2 users here now

👋 Welcome to the SRE Community!

Whether you're just learning about Site Reliability Engineering/Software Reliability Engineering or you're a seasoned on-call warrior, you're in the right place.

SRE (Site Reliability Engineering - AKA Software Reliability Engineering) is a discipline that uses software engineering principles to ensure that systems are reliable, scalable, and resilient. It’s about balancing feature velocity with system stability—keeping things running even when they shouldn’t.

💬 What can you post here?

Here are a few ideas to get started:

War stories from production incidents and what you learned
Cool tools for observability, monitoring, alerting, and automation
Best practices around on-call, SLOs, blameless postmortems, and chaos engineering
Questions about reliability engineering and career advice
Infrastructure as code, CI/CD pipelines, and deployment strategies
Memes. Tasteful ones. SREs need to laugh too 😅

🌐 Be excellent to each other

This community is part of the programming.dev network. Please make sure to:

Read and follow the programming.dev code of conduct
Keep discussions respectful and inclusive
Assume good faith, and be generous in your interpretations

founded 5 days ago

MODERATORS

[email protected]

April Discussion: What problems are you working on. (programming.dev)

submitted 5 days ago by [email protected] to c/[email protected]

3 comments fedilink

Whether you're ironing out kinks in disk provisioning at scale or implementing service mesh for microservices. Let's talk about the problems we're currently tackling.

(Without violating NDA's of course)

SREsyphus (programming.dev)

submitted 5 days ago by [email protected] to c/[email protected]

2 comments fedilink

Maybe, one of these days, my SRE team can define SLOs that actually make sense. This "alert on whatever the customer wants" stance really really sucks.