CSE Roadmap

Common tier · about 3 hours · 9 parts

Part 1 of 9 · 1 min read

Why this page comes first after stateless services

In this module you will

  • Explain why services cannot rely on fixed addresses, and describe three ways a service can find another.
  • Describe a registry with registration, heartbeats and lookup, and work out how fast a dead server leaves it.
  • Say what an API gateway does: routing, composition, translation and cross-cutting jobs.
  • Work out how the availability of a composed call falls as the number of inner calls grows.
  • Place authentication at the gateway and authorization inside the services, and say why.
  • Name the costs of a gateway, and when a team should not build one yet.

Stateless servers can be started and stopped at will, so their addresses keep changing. When an application is also split into many services, two questions follow. How does one service find another? And what does the outside world see? This page answers both. It is marked Common rather than Core: it matters most once a system has several services (Level 7 goes deeper). The numbers on this page are made up to show the idea, unless the text names a book.