If you’re going to work on microservices projects, you need to learn these basic, yet crucial, tips.

Model - a set of concepts existing in the head of the customer/project creator and terms that reflect his understanding.

APIs are the blood vessels of digital business.

DDD is not about technology. Instead, it's about understanding the problem you’re trying to solve in a business context.

Achieving scalability and robustness in system design requires careful consideration of business and architectural needs, and a deep understanding of technology

Domain-driven design terminology, building blocks, and other concepts to get started.

Explore the parallels between scientific knowledge development and IT engineering, drawing insights from disciplines like physics and geometry.

Building a reliable, highly available, scalable distributed system requires adherence to specific techniques, principles, and patterns.

In this series of articles, I would like to share my practical experience implementing Domain-Driven Design to a complex legacy project.

Domain-Driven Design is not a specific software architecture or a strict set of rules but rather a collection of principles and ideas to manage complex domains.

DDD doesn’t prescribe a specific architectural approach, but certain existing solutions effectively help achieve the tactical goals of the methodology.

Implementation of domain driven design in a complex legacy project, focusing on potential mistakes, non-obvious nuances, and useful practical advice.

Value Objects are a useful approach that allows for both formalizing reusable data structures within the domain and designating terms from the subject area.

In this article, I will share the outcomes of adopting Domain-Driven Design in a large legacy project.

Ports and Adapters architecture was created by Alistair Cockburn in 2005.

Explore how Domain-Driven Design tackles concurrency issues in complex legacy systems, based on real-world experiences and practical insights.