Microservices og Availability

Adam Lass og Rasmus Helsgaun

Abstract

Ensuring high availability in a monolithic application is almost impossible due to its deployment challenges and lack of flexibility. This poses a big threat to businesses with a monolithic system today, that want to scale tomorrow. The solution to this problem is called microservices, and in this article we will explore why this is the architecture to use when building large systems with a lot of user traffic. By implementing microservices in the right places, businesses stand to win big on flexibility, scalability and availability of their systems.

Abstract

Ensuring high availability in a monolithic application is almost impossible due to its deployment challenges and lack of flexibility. This poses a big threat to businesses with a monolithic system today, that want to scale tomorrow. The solution to this problem is called microservices, and in this article we will explore why this is the architecture to use when building large systems with a lot of user traffic. By implementing microservices in the right places, businesses stand to win big on flexibility, scalability and availability of their systems.

The Problem

Why the problem is a problem

The startling sentence

The implication of the startling sentence

Hvad indebærer availability?

Hvad er en monolitisk arkitektur?

Hvad er en monolitisk arkitektur?

Hvad er Microservices?

Hvad vælger man?

Spørgsmål?

Microservices og Availability

By Adam Lass

Microservices og Availability

  • 182