Serhat Can
where else to find them
what they talk about
all 6 in the filters
where they keep going back
no series more than once — all 6 in the filters
on a stage with
never shared a talk
who talks about the same things
- Julie Gunderson7 talks
- Grzegorz Sztandera7 talks
- Ayelet Sachto2 talks
- Matt Stratton30 talks
- Jeremy Edberg6 talks
- Gunnar Grosch17 talks
| title | conference | date |
|---|---|---|
| How DevOps changed the way we operate software | stackconf online 2021 | 2021-06-15 |
DevOps redistributes ops tasks so developers ship, get alerts and go on call, turning operations into engineering work using clouds, CI/CD, and infrastructure… | ||
| 4 Key takeaways from running Serverless on production for 4 years | ITNEXT Summit 2019 | 2019-10-30 |
Four years of running AWS Lambda at Opsgenie yields concrete lessons: production use hits concurrent execution limits and cold starts (Java + VPC used to… | ||
| Serverless Architecture on Production: Good, Bad and Ugly Parts | DevConf 2019 | 2019-09-25 |
Companies run production workloads on AWS Lambda with concrete tradeoffs: a fully serverless incident management system is built and runs but requires heavy… | ||
| How to Build a Healthy On-call Culture | DevOpsDays Boston 2019 | 2019-09-23 |
Shows concrete wins and failures: an Elasticsearch incident that required disabling a cluster and a 2:00 a.m. data fix, survey data linking on-call to cortisol… | ||
| Building a healthy on-call culture | OSMC 2018 | 2018-11-06 |
Study with 133 participants, increased cortisol shows on-call causes stress even with few pages; a data-center outage example costs $800 per minute outage so… | ||
| How do we use Serverless Architectures on AWS Lambda | Voxxed Days Microservices 2018 | 2018-10-29 |
Three years of running AWS Lambda in production at OpsGenie with Java, DynamoDB, SQS, SNS, API Gateway, VPC and SAM, showing a fully serverless feature… | ||
| Managing incidents in microservices | Voxxed Days Microservices 2018 | 2018-10-29 |
Argues that incident work must be driven by measurable SLOs, using 99.9% of HTTP calls under 100ms as an example and an explicit error budget to decide paging… | ||
| nothing matches | ||