For the past few decades, one of the most common approaches to software design has been to first focus on the domain model (application layer), then persistence (data layer) and finally the user interface (presentation layer). But what are the pros and cons of this approach? Are there other alternatives?
Ever wondered how honeybees have come to be some of the world’s most efficient architects? Learn how we can all use mother nature’s expertise to better architect our software solutions to be more reactive, responsive and resilient through reactive architecture frameworks using approaches like Domain Driven Design (DDD).
Conversations about architecture can now be summarized in simple words – you start a project, do microservices. The question is, is this a good approach? Is each problem to be solved using the ‘cloud application in microservice architecture’? Of course not! So why are we doing this? Is there a …
This talk covers basic concepts in domain-driven design (DDD), and we discuss why and how DDD can help create microservices with better autonomy, scalability, and reliability. Using examples, we navigate from a domain model to the design of both synchronous (REST-based) and asynchronous (reactive) microservices.
All software architectures have to deal with stress. It is simply the way the world works! Stressors come from multiple directions, including changes in the marketplace, business models, and customer demand, as well as infrastructure failures, improper or unexpected inputs, and bugs. As software architects, one of our jobs is …
As a software developer, you may have heard the terms “Microservices” and “Service-Oriented Architecture” (SOA) in the past. You have tried to understand them by googling and asking people and that only resulted in either an incomplete picture of how it works or, more likely, a bunch of wildly varied …
