Microservices have many advantages: Efficiently implementing more features, bringing software into production faster, robustness and easy scalability are among them. But implementing a microservices architecture and selecting the necessary technologies are difficult challenges.

This book shows microservices recipes that architects can customize and combine into a microservices menu. In this way, the implementation of microservices can be individually adapted to the requirements of the project.

Eberhard Wolff introduces microservices, self-contained systems, micro- and macro-architecture and the migration to microservices. The second part shows the microservices recipes: Basic technologies such as Docker or PaaS, frontend integration with links, JavaScript or ESI (Edge Side Includes). This is followed by asynchronous microservices with Apache Kafka or REST / Atom. In the synchronous approaches, the book discusses REST with the Netflix stack, Consul, PaaS with Cloud Foundry, and Kubernetes. Finally, operations is discussed: Log Analysis with Elasticsearch and Kibana, Monitoring with Prometheus, and tracing with Zipkin.

The second edition is based on the feedback about the first edition. All chapters have been clarified, updated and extended. A new chapter discusses services meshes, in particular Istio with an example application. The second edition has about 35 pages more than the first edition.

For each recipe there are suggestions for variations and combinations. Readers can experience all technologies hands-on with a demo project on GitHub. The outlook picks up on the operation of microservices and also shows how the reader can start with microservices in concrete terms.

The book provides the technical tools to implement a microservices architecture. Demo projects and suggestions for self-study will complete the book.

This primer gives a quick overview of Microservives including:

What are Microservices?

• Size of Microservies
• Microservices, Domain-driven Design and Bounded Context
• Conway's Law and the impact on the Organization

Why Microservices?

• Scaling Agility
• Migrating Legacy Applications
• Sustainable development
• Robustness
• Continuous Delivery
• Independent scalability
• Technology freedom

At the end the primer gives hints how to start with Microservices. It is intended as a quick start into Microservices.

Dieses Booklet gibt einen kurzen Überblick über Microservices und bietet so eine gute Starthilfe für die Arbeit mit Microservices.

Was sind Microservices?

• Die Größe von Microservices
• Bounded Context und Domain-driven Design
• Das Gesetzt von Conway

Warum Microservices?

• Agilität skalieren
• Legacy-Anwendungen migrieren
• Nachhaltige Entwicklung
• Robustheit
• Continuous Delivery
• Unabhängige Skalierbarkeit
• Technologie-Wahlfreiheit

Das letzte Kapitel zeigt, wie man konkret mit Microservices loslegen kann.

Diese Broschüre zeigt Technologie-Rezepte für die Implementierung von Microservices. Die Beispiele stehen als Code zum Download bereit.

Inhalt

Was sind Microservices?

- Independent Systems Architecture Principles

- Self-contained Systems

UI-Integration

- Warum UI-Integration?

- Rezept: ESI (Edge Side Includes)

- Alternative Rezepte: Links und JavaScript

Asynchrone Microservices

- Definition: Asynchrone Microservices

- Warum asynchrone Microservices?

- Rezept: Kafka

- Alternatives Rezept: Atom

Synchrone Microservices

- Definition: Synchrone Microservices

- Warum synchrone Microservices?

- Rezept: Kubernetes

- Alternative Rezepte: Netflix, Consul, Cloud Foundry

Das letzte Kapitel zeigt, wie man das Wissen über Microservices-Technologien weiter vertiefen kann.

This brochure includes technology recipes for the implementation of microservices. The code for the examples can be downloaded for free.

Content

What are Microservices?

• Independent Systems Architecture Principles
• Self-contained Systems

Frontend integration

• Why frontend integration?
• Recipe: ESI (Edge Side Includes)
• Alternative recipe: links and JavaScript

Asynchronous microservices

• Definition: asynchronous microservices
• Why asynchronous microservices?
• Recipe: Kafka
• Alternatives recipe: Atom

Synchronous Microservices

• Definition: synchronous microservices
• Why synchronous microservices?
• Recipe: Kubernetes
• Alternative recipe: Netflix, Consul, Cloud Foundry

The last chapter explains how to deepen the knowledge about technologies for microservices further.