Choosing the right start for writing microservices?

Question

Java

Gentlemen and ladies, it means we decided to cut a new project, there will be a highly loaded system, such as a social network of a certain subject. Of the technologies, the main one is Spring + Kafka in Java. Actually, I need to offer the optimal sequence for developing services, or at least some, but I have something brainlag. I worked all the time in already existing projects, and somehow it turned out that a lot depends on my opinion. What do you advise? Who can have some advice, who started the project from scratch, namely a web-trick on applications.

PS It's clear about the Kafka server and writing a test interaction of services, so how to write the architecture further? How best to distribute the load among team members, etc. I understand that the question is in general and in general, but can someone share their experience.

Answer 1

https://microservices.io/ - many useful thoughts about microservices.
From experience - even with a great desire to file microservices, they really need to be needed to succeed. And it's good to go to the domain model.
Otherwise, you end up with several regular services, which you will call "micro".
No one will write the optimal sequence for you out of thin air - it depends directly on the product, goals, resources, priorities, and so on. Normal is such a constant and non-stop work of a product manager, if you have been assigned these duties and you don’t know what to do, study at least the basics, there is a lot of information on the net.
If you do not need to be responsible for the product, but you need to do exactly the architecture, then go to the one who is responsible and make at least some kind of roadmap with him for a couple of years. Based on it, you will already think what will depend on what, in what order to do it, and in general what functional blocks you need.
Until the product is described, the architecture will not work, except perhaps some very basic things. Even the choice of a database or a communication protocol between services depends on business requirements.
it's about team management.
If you have been charged with everything from design to architecture to team management, then good luck. If you do not fill up everything completely, it will be a cool experience.

Answer 2

Very vague question.
I recommend reading it then.
Distributed Systems Brendan Burns
and
Application Scaling by Lee Atchison
Easy and quick to read. On average, 250 pages.
And of course, ideally, you can also add
site reability engineering to Betsy Beyer (available in Russian)
Questions will disappear by themselves