Microservices Architecture

Start with the foundations

The mind map Microservice introduces large systems built from loosely coupled processes and mentions service registration. It is a useful starting point if you want an overview before exploring individual design decisions. The flashcards in Microservices Talk offer another route in, with prompts about bounded context, calls between services and breaking up a monolith.

Read the map first, then use the flashcards to check which ideas you can explain in your own words. Return to the map when a prompt raises a concept you want to look at again.

Explore architecture and responsibilities

The page has two mind maps titled Microservices Architecture. One covers security, monitoring, development, communication between services and deployment. The other places microservices alongside architectural styles and patterns, with branches on core concepts, API gateways and architectural views.

For a more specific example, the quest-edge map lists services and describes routing, load balancing and authentication at the edge. Another map titled Microservices outlines responsibilities such as receiving requests and authenticating information, as well as qualities including autonomy and isolation.

Use the quiz with the maps

Microservices Foundations asks about topics including problems associated with monoliths and the workings of BPEL. Try it after reading an introductory map. When a question is difficult, look for a relevant branch in the maps and use it to organize what you want to study next. The quiz and maps offer different ways to work through the material.

Connect the topic to the unit

This topic sits within a wider unit in Computing and ICT. The architecture-focused map connects microservices with architectural styles, patterns and design, giving you a way to relate the topic to the unit's broader focus on software design.

Choose a map and follow a branch that interests you.