Timeline for answer to What are the key architectural differences between microservices and modular monoliths, and when should each be used? by Arseni Mourzenko
Current License: CC BY-SA 4.0
Post Revisions
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| 2 days ago | comment | added | Arseni Mourzenko | @GregBurghardt: I should have mentioned Conway's Law, indeed. Now, back to the monolith you mention, one way to approach it is to think about one or two aspects that could be moved in a separate REST service—and the ROI of such operation. It should be doable in a single sprint, so shouldn't be something too complex. If this is successful, you can then envision what other parts could become separate services, and, step by step, end up with microservices architecture. Or something in-between—most large systems are a mix of different architectures. | |
| 2 days ago | comment | added | Greg Burghardt | A lot of questions about micro services on this site are caused by your second example of a project going bad. The initial decision might not have been wrong, but a lot of times people take the "micro" in micro services literally; they decompose things too much. I work on a 10-year-old monolith. I recently discussed breaking it into micro services with my team, and we discovered that we just didn't have something big enough to justify the added complexity, nor do we have multiple teams. It's a big app, but micro services just don't pull their weight for us. So monolith it is. | |
| 2 days ago | history | edited | Arseni Mourzenko | CC BY-SA 4.0 |
added 2853 characters in body
|
| 2 days ago | history | answered | Arseni Mourzenko | CC BY-SA 4.0 |