Timeline for Data Replication Across Microservice Domains
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2019 at 14:47 | comment | added | ZioBrando | We still have 2 Contexts, because contexts by definition are units of independent language. Choosing independent deployment units is a different matter. But I wouldn't follow "an update here requires an update somewhere else" as an architecture driver, because this is going to happen over and over. If you follow that path, you just turn back to the monolith. :-/ | |
| Feb 16, 2019 at 17:54 | comment | added | user3347715 | If issuing an update query for a Customer in the Registration context requires an update query to be issued to a different context, do we really have two contexts? More importantly, are we realizing the primary benefit (scaling) that a distributed architecture offers, or have we just added a whole lot of complexity? | |
| Feb 15, 2019 at 17:01 | comment | added | ZioBrando | In general, a few concepts from the DDD space will come in handy: I already mentioned Bounded Contexts, but also CQRS will provide some interesting insights on how to design your architecture. | |
| Feb 15, 2019 at 16:53 | comment | added | ZioBrando | @MarshallTigerus this one is not strictly about microservices, but it's the best 'punch' to get into the right mindset, it worked miracles with me. :-) infoq.com/presentations/SOA-Business-Autonomous-Components | |
| Feb 14, 2019 at 15:30 | comment | added | Laiv | @MarshallTigerus just for your info, while blogs and books use to provide us with the "insights", they leak on details of implementation (obviously). However, once you start getting familiar with the "ideas" around the MS architectural style you start to identify the "problems", the common ones. It's then when you have to start getting familiar with architectural styles and patterns to look for "approaches to the solutions". | |
| Feb 14, 2019 at 14:50 | comment | added | Marshall Tigerus | @Laiv TY, I will be sure to do both. | |
| Feb 13, 2019 at 22:04 | comment | added | Laiv | @MarshallTigerus despite recommending resources and books is off topic here, I would suggest read Nginx' blog and Sam Newman's book Building Microservices. Both are worth readings. Additionally, It makes a big deal if you get familiar with enterprise architecture patterns. | |
| Feb 13, 2019 at 20:15 | comment | added | Marshall Tigerus | are there any resources you can recommend that go over how to properly architect a microservice architecture? | |
| Feb 13, 2019 at 20:13 | comment | added | Marshall Tigerus | You are most likely correct, which is what we get for not having an in-house architect and blindly trusting the architecture of a contractor who seemed to only throw around buzzwords and not do any real work. Unfortunately, we're significantly built into what we have now, which means we're stuck until we can put forth the effort of a redesign. | |
| Feb 13, 2019 at 18:47 | history | answered | ZioBrando | CC BY-SA 4.0 |