Timeline for Decentralized Data Management - encapsulating databases into microservices
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 23, 2016 at 17:30 | comment | added | floer32 | Another link from Martin Fowler, on this topic: Monolith First | |
Jul 6, 2015 at 22:03 | comment | added | btilly | @dariol There is no good upgrade path from monolithic to full microservices through a middle ground of "we load a large common code base everywhere, then use what we need from it". However it is reasonable to do this as a temporary patch to get through an immediate need. And then begin splitting off real microservices, until the core can be replaced. The reason why that is hard has to do with dependency management. You will keep on hitting, "I just need this, but this depends on that, depends on that...and now I have the entire ball of spaghetti." | |
Jul 3, 2015 at 17:27 | comment | added | dariol | Is there a way between monolith and microservices? I have a multitenant monolith application. After some time I see that I should divide per tenant. Each tenant should have own instance of application but they are must share some data and it must be a single/central place. So, I can create separated service especially for that. It looks like I will have couple (not so micro) of app/services. Is it sounds reasonable to do this that way? | |
Dec 13, 2014 at 0:32 | comment | added | Whymarrh | Here's a recent talk from Martin Fowler (the 3rd one) that touches on a few of these points. | |
Dec 8, 2014 at 3:58 | comment | added | ThinkBonobo | An extremely insightful answer. Thank you for imparting this wisdom. | |
Dec 8, 2014 at 3:57 | vote | accept | ThinkBonobo | ||
Dec 7, 2014 at 20:04 | history | answered | btilly | CC BY-SA 3.0 |