Hello Everyone,
I am looking for advice on how to decompose an application into microservices from business requirements. We are working on a green field project that needs to be decomposed into microservices since independent evolution of services is a key requirement.
I came across few decomposition techniques including "Functional decomposition using use case specifications", "Data driven decomposition using data flow diagrams with database per service being the key principle", "Message first approach from the book The Tao Of Microservices". I am mid-way in applying these techniques to our application and looking out for advice from someone who has done this exercise.
We have a domains diagram from our product managers that shows different components of the system with some marked as "independent offerings". The components are depicted as processes which have their functionalities noted as sub-processes. There is also an entity relationship diagram that displays relationships between business entities.
With the use case specification being worked up in parallel, I am trying to build up level-0 and level-1 DFD diagrams taking certain assumptions. Any guidance from someone who has done this system decomposition exercise would be really appreciated.
Thanks.
--
You received this message because you are subscribed to the Google Groups "DDD/CQRS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dddcqrs+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dddcqrs/44333287-8aa4-4ee8-be9a-a13a964eef7an%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dddcqrs/CAGsYEJ7pvBK5SZQ%2Bu9YnBNwqHeSaDKdVoVebW4VHN%2BWbB_RWuw%40mail.gmail.com.