Heuristics for Identifying Microservice Boundaries
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:
- Software Architecture for Developers Workshop with Robert Smallshire (in London on 9th - 10th September 2019)
- Functional Concurrency in .NET with C# and F# (in London on 9th - 10th September 2019)
- ProgNET London 2019 (in London on 11th - 13th September 2019)
- CloudNative London 2019 (in London on 25th - 27th September 2019)
- Keynote by Emily Jiang on On Stage Hacking: Build 12-Factor Microservices in an Hour (in London on 23rd July 2019)
- London Java Community July (in London on 24th July 2019)
- Browsers: Behind the Scene (SkillsCast recorded in July 2019)
- Cloud Native Node.js (SkillsCast recorded in July 2019)
Thanks to our sponsors
Heuristics for Identifying Microservice Boundaries
Erich Eichinger
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.
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:
- Software Architecture for Developers Workshop with Robert Smallshire (in London on 9th - 10th September 2019)
- Functional Concurrency in .NET with C# and F# (in London on 9th - 10th September 2019)
- ProgNET London 2019 (in London on 11th - 13th September 2019)
- CloudNative London 2019 (in London on 25th - 27th September 2019)
- Keynote by Emily Jiang on On Stage Hacking: Build 12-Factor Microservices in an Hour (in London on 23rd July 2019)
- London Java Community July (in London on 24th July 2019)
- Browsers: Behind the Scene (SkillsCast recorded in July 2019)
- Cloud Native Node.js (SkillsCast recorded in July 2019)
Thanks to our sponsors
Heuristics for Identifying Microservice Boundaries
Erich Eichinger
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.