Architecture

The Architecture

After finishing collecting the requirements. You (as a Software Architect) and the team have a meeting to decide how we draw the system.

Currently, there are two directions to go: traditional SOA and Microservices architecture. Everyone seems already known and be familiar with SOA. So they want you to give them a glance of what Microservice is also the benefits and drawbacks of using this architecture.

"OK, before we start, you may want a cup of coffee as it is the best to enjoy my session with some caffeine".

What is a microservice? (https://kipalog.com/posts/Gioi-thieu-ve-Microservices--Phan-1--Dia-nguc-kien-truc-mot-khoi)

Then what is a microservices architecture?

The characteristics

Why microservices?

Costs and downsides

"OK, then we will go with Microservices!" - the team said.

Identifying and Scoping microservices

1

2

List of microservices for Tiki2

Got it! Now, let's take a look at the requirements to see what we have.

1. Business capabilities
2. Technical capabilities

Microservice collaboration

1

2

A complete picture

Overview of an microservice

Data ownership

Testing

Handling Cross-cutting Concerns