For me, the term Microservice in conceptual level is not new. I think it not much different from SOA. The different is just about how the term define how deep to decoupling/separate in programming level. Recently, with many development teams working on different features. Without causing and impact when changes, they have to be separate to each other which is not new. But now with the technogy improved, and tools are much more powerful. they help a lot to develop with Microservice architecture from start to finish a feature without worry in impact to other features.
Recently, I started to read and research more in details because of facing this problems. There are many sub features/modules in 1 product. Each have to work with different teams. In order to reduce an impact when deploy. I started to think about Microservice.
Concepts:
- Microservices architecture? What, Why and How.
- Microservice Architecture at Medium
- Microservices a definition of this new architectural term
- Microservices — When to React Vs. Orchestrate
Before, I was thinking how they dealing with transactions because in monolithic software, it is usually connect to 1 or few data systems. So, they need to work around to cover and make it work by creating a rollback request.
Moreover, with many Microservices, I started to think about how they can working together. Because if many services working together and we have 1 service to Orchestrate them. I think this part will be tightly couple as same as monolithic software did. The link below is not solve the issues. It just talking about how many services can connect in easiest way, less impact and effort by using Kubernetes.
Programming:
