The Delivery Hero - A Simpsons As A Service Storyboard
•
1 like•522 views
The way from monolithic to micro service architectures can hard. Overall micro services are not the all holy grail to just solve all your issues. You need to be aware that you need the right developers and the right toolset. Oh and not to forget, moving state to authorization systems doesn't mean your application is really stateless :) Anyhow micro services are a great architecture and this deck is a short introduction on why we need to change our application architectures and what pitfalls you you have when introducing the idea of micro services.
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to The Delivery Hero - A Simpsons As A Service Storyboard
Similar to The Delivery Hero - A Simpsons As A Service Storyboard (20)
More from Christoph Engelbert
More from Christoph Engelbert (20)
Recently uploaded
Recently uploaded (20)
The Delivery Hero - A Simpsons As A Service Storyboard
- 2. The Delivery Hero This motion picture is protected under the copyright laws of Springfield. The story, all names, characters, and incidents portrayed in this production are non-fictitious. Identification with actual persons (living or deceased), places, buildings, and products is intended and should be inferred. No animals were harmed but feeling were hurt during the making of this motion picture.
- 4. When I was young – books were still a thing…
- 5. …and those were delivered through book stores
- 6. Also in the early days of computers, delivering software was easy
- 7. Often enough software was shared at school or work
- 8. Who‘s too young to remember that time?
- 9. But hardware and software grew more complex
- 10. And publishers took on the problem - some of them got big in the game
- 12. More and more people buy online
- 14. Work remotely and use videocalls
- 16. …that better stay in the dark
- 17. Or don‘t you know this feeling,…
- 18. …when your better half just comes home? ;-)
- 19. And do not forget, smartphones became a thing, too
- 20. Some had a very secret plan to solve the change
- 21. But everyone tried to keep up with the change
- 22. Some even considered physical delivery by drones
- 23. But delivering hosted solutions is different
- 24. There‘s always a fire to fight
- 25. “Our server can‘t hold up to the load anymore!“
- 26. The amazing monolith just does not scale.
- 27. “We need a better, scalable architecture!“
- 28. People expect hosted software to be available DOH! NOOOO! I can‘t work that way!
- 29. Ever seen gamers going crazy during maintenance?
- 30. Ever seen gamers going crazy during maintenance?
- 31. Ever seen gamers going crazy during maintenance?
- 32. Ever seen gamers going crazy during maintenance?
- 33. Ever seen gamers going crazy during maintenance?
- 34. Crazy right?!?
- 37. So we need a new plan…
- 38. …and your dev team knows exactly what you mean!
- 40. So you try take on the story of little independent software elements…
- 41. …that can updated and scaled completely separated from others.
- 42. You seem like a rebel making such a proposal
- 43. And what seems a great idea…
- 44. …turns out to look stupid to others
- 45. In the end at least some people get it, but not all of them.
- 46. Ever tried to combine monolith and microservice? Director‘s comment:
- 47. Fortunately some cool devs get it
- 48. What we need is the holy grail precious, my precious
- 50. Minimize functionality in every single unit
- 54. And fast…
- 56. We want devops to party on every release
- 59. And if you manage, the night‘s long
- 60. Operation hates you if you put more work on them
- 61. So someone finally shows you…
- 62. …the cloud!
- 63. That is what we want to do today
- 64. Make you happy
- 67. Make your mom happy
- 69. And believe me, it‘s not dangerous at all
- 71. And put it together bit by bit
- 72. Alright, let‘s get started already!
- 73. PS: We know, the Simpsons are great on predicting the future…
- 74. …so is that it?
- 76. A big thank you to: Matt Groening