Timeline for Clean Architecture with Microservices
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 19, 2023 at 14:25 | comment | added | JimmyJames | @ArcSpark76 "I was personally taught microservices have a very limited scope. so the area of concerns should be limited also" I hope you are not misunderstanding my answer here because that's exactly what I am saying. The problem is that people often take this too literally and do things like deploy each service independently but retain a shared datastore. You end up in a situation where when you change things, you now have many deployments to coordinate which is nearly the opposite of the goal. | |
| Sep 19, 2023 at 14:16 | comment | added | JimmyJames | @Ccm "The problem with sharing a database is about scaling the database." This is an issue, but I don't think it's the primary one. "A shared database usually comes with relations between tables belonging to different services," That's the key problem that makes it hard to manage. E.g., you want to change your tables but there are all kinds of dependencies from other parts of the system that will need to be changed. | |
| Sep 18, 2023 at 21:46 | comment | added | Ccm | At some point, microservices will need to know about each other and some common business rules. Completely abstracting the business rules is not productive. The problem with sharing a database is about scaling the database. A shared database usually comes with relations between tables belonging to different services, which in turn makes the database difficult to scale. The schema trick only works up to a point. | |
| Sep 18, 2023 at 21:42 | comment | added | ArcSpark76 | The 9 systems that look the same and operate on different subjects is a valid point. I was personally taught microservices have a very limited scope. so the area of concerns should be limited also. My understanding is, doing it that way can help with scaling the system. If Users is being hit hard, it can be independently scaled up as needed and that'd effect no other part of the system. | |
| Sep 18, 2023 at 20:57 | history | answered | JimmyJames | CC BY-SA 4.0 |