https://github.com/cristim/serverless-failure-stories

Compilation of public failure/horror stories related to Serverless, inspired by hjacobs/kubernetes-failure-stories
https://github.com/cristim/serverless-failure-stories

Last synced: about 15 hours ago
JSON representation

Compilation of public failure/horror stories related to Serverless, inspired by hjacobs/kubernetes-failure-stories

• Host: GitHub
• URL: https://github.com/cristim/serverless-failure-stories
• Owner: cristim
• License: unlicense
• Created: 2019-01-20T09:02:55.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2019-09-24T04:37:17.000Z (about 5 years ago)
• Last Synced: 2024-08-08T23:20:48.932Z (3 months ago)
• Size: 7.81 KB
• Stars: 388
• Watchers: 39
• Forks: 10
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Serverless Failure Stories

A compiled list to public failure/horror stories related to serverless infrastructure, heavily inspired by [hjacobs/kubernetes-failure-stories](https://github.com/hjacobs/kubernetes-failure-stories/)

Most recent publications on top.

* [Serverless out of control](https://koptional.com/2019/01/22/serverless-out-of-control/)

* [Mo’ developers, mo’ problems: How serverless has trouble with teams](https://jaxenter.com/how-serverless-trouble-teams-150705.html)

* [Beware “RunOnStartup” in Azure Functions – a serverless horror story](http://blog.tdwright.co.uk/2018/09/06/beware-runonstartup-in-azure-functions-a-serverless-horror-story/)

* [Serverless: A lesson learned. The hard way.](https://sourcebox.be/blog/2017/08/07/serverless-a-lesson-learned-the-hard-way/)

* [Serverless: 15% slower and 8x more expensive](http://einaregilsson.com/serverless-15-percent-slower-and-eight-times-more-expensive/)

## Why

Serverless applications tend to be fairly complex with many albeit relatively simple moving parts.

Its ecosystem is constantly evolving and adding even more into the mix.

Considering this environment, we don't hear enough real-world horror stories to learn from each other!

This compilation of failure stories should make it easier for people dealing with serverless applications to

learn from others and reduce the unknown unknowns of running serverless in production.

## Contributing

Please help the community and **share a link to your failure story by opening a Pull Request!**

Failure stories can be anything like blog posts, conference/meetup talks, incident postmortems, tweet storms, ...

I would also be glad to hear about your failure stories on Twitter: my handle is [@magheru_san](https://twitter.com/magheru_san)