Serlo Infrastructure

Our Infrastructure

We have a microservice architecture that looks like this (note: this pic is outdated):

We made this switch for a plethora of reasons:

• the monolith grew large and unwieldy
• with microservice infrastructure it is much easier to incorporate a new microservice that is suited to a specific problem without refactoring the entire code base (an example: it was no problem to insert a new database layer in Rust)
• in theory, integrating and working together with other learning software will be easier to do in the future
• serlo.org was not fast enough for our needs any longer

List of most important repositories

• frontend
• api.serlo.org
• cloudflare-worker