DDD vs Micro Service vs Data-Centric vs Hexagon?

Question

Software design

Familiarized with the last 2 at the level of articles from habr.
What, when and why should you use it? What else is there? Can I please have books on the topic?
https://www.packtpub.com/mapt/book/application_dev...

Answer 1

These concepts are not opposed to each other. These are just different approaches, which can also be used together.
DDD is an approach for highlighting the business logic (business model) in an application and all sorts of patterns around it.
Used accordingly, usually to deal with complexity, in an application with complex business logic.
The main books are "blue book" and "red book" , as well as material on habré and here
Micro Services is a very general pattern, the essence is in dividing logic into less related separate parts. For a general understanding, articles on Habré are enough, then specific implementations often vary greatly .
Data-centrican even more general concept. This is usually understood as a scenario approach, a bias towards procedural programming, manipulation of objects as data containers (DAO). The advantage is usually the ease of use of the approach on small and medium projects.
Hexagon is an approach to building a layered architecture, often referred to as "ports and adapters". Often used in the implementation of microservices. The bottom line is that the outer layer should be the boundary of interfaces and adapters that transform input protocols into information compatible with the internal interface. Articles on Habré should be enough.