Monoliths, Balls of Mud and Silver Bullets
•
0 likes•584 views
This document discusses monolithic architectures and microservices. It notes that while microservices are an improvement over monoliths and "balls of mud", they are not a "silver bullet" and care must be taken to realize their benefits. Specifically, having microservices share a monolithic database can cause issues around ownership and changing the database schema. The document provides some tips for implementing microservices including making services RESTful, assuming private APIs will become public, and emulating Johnny Cash by destroying monoliths "One Piece at a Time".
Recommended
More Related Content
More from Dave Cross
More from Dave Cross (20)
Recently uploaded
Recently uploaded (20)
Monoliths, Balls of Mud and Silver Bullets
- 6. Monoliths, Balls of Mud & Silver Bullets
- 8. Monolithic Balls of Mud are worse
- 11. Well...
- 12. I am old
- 13. Old people have long memories
- 14. “Those who refuse to learn from commit history are doomed to reimplement it”
- 16. “Adding manpower to a late software project makes it later.”
- 17. “Observe that for the programmer, as for the chef, the urgency of the patron may govern the scheduled completion of the task, but it cannot govern the actual completion.”
- 18. “There is no silver bullet”
- 21. Microservices are not a Silver Bullet
- 22. Disclaimer Please note that nothing I say over the rest of this presentation should be taken as me saying or implying that microservices are not an improvement over most software architectures that preceded them. I am merely pointing out that they are not the cure-all that some of their fans seem to think they are and that some care needs to be taken in order to get the most benefit from them. I’m also, of course, going for a few cheap laughs here. All advice is worth exactly what you paid for it. Satisfaction guaranteed or your money back.
- 24. Simplicity
- 25. Simplicity
- 26. Less complexity
- 27. Ownership
- 28. Autonomy
- 29. Faster releases
- 30. Inside your monolithic ball of mud
- 42. How do you change the database schema?
- 43. How do you ensure you that your changes to the database schema don’t affect other users of the monolithic database?
- 45. Simplicity?
- 46. Ownership?
- 47. How many stacks do you need?
- 56. AWS == £$€
- 57. Some tips
- 58. Microservices are REST over HTTPS
- 59. <SOAP/> Dodger
- 60. JSON is standard
- 61. HTTP is more than GET and POST
- 62. Use HTTP Verbs for CRUD CRUD REST over HTTP Create POST Read GET Update PUT Delete DELETE
- 64. Assume your private API will be public
- 65. Issue API keys
- 66. Version your API
- 67. Use HAL (Hypertext Application Language)
- 71. Emulate Johnny Cash Destroy the monolith “One Piece at a Time”
- 72. Emulate Johnny Cash Destroy the monolith “One Piece at a Time”