Scalable architectures

Table of contents

• Scalable architectures

  • Introduction

  • Learning focuses

    • Category

      • Learning tasks

Introduction

(from Canvas) You investigate architectural patterns and scalable architectures that perform well in enterprise contexts. Your chosen architecture should support relevant quality attributes from this enterprise context (for instance robustness, performance, availability, and responsiveness)

Your architecture consists of independently running parts (for instance microservices), which need to be deployed independently and communicate asynchronously (for instance using messaging).

You investigate which performance indicators you will need to measure and monitor those independent parts while they are running. You validate that your application automatically scales using your indicators while having realistic loads.

Your choice of technologies for the scalable parts should fit the quality requirements of the architecture.

You use techniques during analysis and design, which help in creating scalable architectures (for instance Event Storming). Your development process and platform should support the design and deployment of your scalable architecture. You use industry standards (for instance C4 model, UML) to communicate and justify your architectural choices to stakeholders and your own team.

Learning focuses

In order to shape the upcoming curriculum, I’ve chosen various learning focuses for scalable architectures. These are work in progress, and have to be developed out further.

---

Scalable architectures

Category

In the tables below the category tab depicts the nature of the skill concerning the listed task.

Additionally to the standard, I’ve expanded with a custom table with tasks I came up with.

• T = Technical skills

• N = Non-technical skills

• R = Research & development skills

• P = Professional skills

Learning tasks

Task#	Category	Requirement	Status	Description
#0	T	Must	Done	Event Storming
#1	TP	Must	Done	Architecture explained through C4
#2	T	Must	Done	First Microservice
#3	T	Must	Done	Second Microservice
#4	T	Must	Done	Non trivial Comment Microservice
#5	T	Must	Done	Horizontal Auto Pod Scaler
#6	T	Must	Done	Validation of Scalability