Thanks a lot for the link to book and to your list of resources!
As a side note to this:
Microservices are very hard to do right
While microservice architecture ceased to be novelty for some years already. I rarely found project nowadays which doesn't utilize this approach. However You are very right, it seems to me. But not only because of themselves. Lot of troubles comes from fact that projects get new requirements and features over time. Monolithic architecture suffers from such extensions. Microservices also suffer from these extensions. With microservices it is just somewhat easier to do housekeeping, partial updates etc. But still no way to do things "very right - and from beginning" because at beginning we don't know what exactly would be "right" some time later. (my meek personal opinion)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks a lot for the link to book and to your list of resources!
As a side note to this:
While microservice architecture ceased to be novelty for some years already. I rarely found project nowadays which doesn't utilize this approach. However You are very right, it seems to me. But not only because of themselves. Lot of troubles comes from fact that projects get new requirements and features over time. Monolithic architecture suffers from such extensions. Microservices also suffer from these extensions. With microservices it is just somewhat easier to do housekeeping, partial updates etc. But still no way to do things "very right - and from beginning" because at beginning we don't know what exactly would be "right" some time later. (my meek personal opinion)