How to properly organize the structure of microservices?

Question

Service Oriented Architecture

Good day everyone. I'm trying to organize a project by dividing the logic into many microservices. I do not understand how to organize the structure.
An example of how I would organize the structure using http.
There is a client that makes an http request to the authentication server (it will focus the authentication of the request), if the authentication server has completed the check successfully, the request is redirected to the service, while the authentication server will add information about users, etc. to the request body.

But I have no idea how to organize it correctly using kafka (or an analogue). Tell me what to read, what examples to look at, or an example of architectures. Thanks

Answer 1

almost nonsense, but now we'll fix it.
1. to the Identity Server account - it does not send any data about the user to anyone. There is a client, it passes authentication, during which it receives a token with which it goes to other services. Services measure the token themselves or through the Identity Server. For a better understanding, let's read about OpenID/OAuth2 Flow.
2. Kafka lives in its own world, but it has its own authentication methods
3. Users are not authenticated anywhere except the pediment. The maximum where there is an understanding that the action occurs on behalf of the user - API for the frontend (or application). After that, authorization goes to services because they communicate with each other

Answer 2

First, think about whether such a hemorrhoid is needed in development and maintenance as microservices (you haven’t started doing it yet and don’t know how).
in most cases, microservices are done because they are fashionable and not because they are of great use