Please log in to watch this conference skillscast.
When identifying microservice boundaries, it is not enough to consider domains only. Other forces like organisational communication structures, and time, strongly suggest that you also should include other criteria in your considerations. Based on real world experience of numerous projects, this talk takes a pragmatic walk and explores some of these other heuristics which should also be shaping your microservice decomposition thinking. These considerations may not on the surface seem that obvious, but if ignored, can just as easily lead to project failure. So whether you’ve already been through a painful project which tried to decompose boundaries by the book and failed, or you’re looking for some insight into other considerations often not spoken about, this talk is for you.
YOU MAY ALSO LIKE:
Heuristics for Identifying Microservice Boundaries
Erich Eichinger is a Lead Consultant at Open Credo. As an architect and tech-lead, he has helped major clients in industries, most recently, a large car manufacturer, on successfully leveraging the advantages of a microservice-oriented approach.