-
Notifications
You must be signed in to change notification settings - Fork 1
Architecture
johnlemon93 edited this page Sep 8, 2018
·
5 revisions
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)
"OK, then we will go with Microservices!" - the team said.
Got it! Now, let's take a look at the requirements to see what we have.
- Business capabilities
- Technical capabilities