Microservices, Archetypes and Exemplars

In a previous post, I stated that:

"a well formed Business Capability model is the foundation of a stable microservices catalogue".

And, just as your Business Capability model is the foundation for a stable microservices catalogue so is the definition of your domains Business Concepts to communication with and between those microservices.

I use the term 'Archetype' to classify business concept models that are used in different business domains. For example, 'Customer' (a type of Role played by an Individual or an Organisation) is a business concept that is used in Banking and Finance, Utilities, and Telecommunications.

And, I use the term 'Exemplar' to classify business concept models that are used within a particular business domain.

Note: When modelling archetypes and exemplars I am mindful of the magical number seven (plus or minus two) and the use of colour.

References:

• William Ulrich & Michael Rosen: The Business Capability Map
• Eric Evans: Domain-driven Design
• David Anderson: Advanced Domain Modeling
• Stephen R. Palmer: Peter Coad's 'Modeling in Color'
• Douglas English: Colour Modelling - Domain Modelling with the 3rd Dimension

References - Archetypes and Exemplars:

• David C. Hay: Data Model Patterns: Conventions of Thought
• David C. Hay: Data Model Patterns: A Metadata Map
• David C. Hay: Enterprise Model Patterns: Describing the World
• Martin Fowler: Analysis Patterns
• Jim Arlow, Ila Neustadt: Enterprise Patterns and MDA
• Len Silverstein, W. H. Inmon, Kent Graziano: The Data Model Resource Book
• Michael Blaha: Patterns of Data Modeling