DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together

This post is part of The Software Architecture Chronicles, a series of posts about Software Architecture. In them, I write about what I’ve learned on Software Architecture, how I think of it, and how I use that knowledge. The contents of this post might make more sense if you read the previous posts in this series. After … Continue reading DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together

Clean Architecture: Standing on the shoulders of giants

This post is part of The Software Architecture Chronicles, a series of posts about Software Architecture. In them, I write about what I’ve learned on Software Architecture, how I think of it, and how I use that knowledge. The contents of this post might make more sense if you read the previous posts in this series. Robert C. … Continue reading Clean Architecture: Standing on the shoulders of giants

Clean Architecture Is Screaming

Uncle Bob's Clean Architecture keeps your application flexible, testable, and highlights its use cases. But there is a cost: No idiomatic framework usage! Welcome to the fifth installment of little architecture series! So far we have covered layers, hexagons, onions, and features. Today, we’ll look at a close friend of all four – Uncle Bob’s Clean Architecture, initially introduced here. … Continue reading Clean Architecture Is Screaming

ESB Frameworks

Application integration is the biggest challenge today for many enterprises. Building an Enterprise Service Bus (ESB) is probably the quickest and most cost-effective way to address this challenge. In this article, you gain insight on ESBs, and how to model and construct ESB service-oriented architecture frameworks. Service-Oriented Architecture (SOA) is an approach to defining integration … Continue reading ESB Frameworks

J2EE And SOA Architecture

In this article, you’ll learn how to design and develop service-oriented architecture (SOA) frameworks using the Java 2 Platform, Enterprise Edition (J2EE). By adapting an SOA framework, your organization can maximize loose coupling and reusability between systems. This article will take a high-level overview of several iterations over an SOA framework that will meet the needs of … Continue reading J2EE And SOA Architecture

Difference between SOA, EAI and ESB

Today, let me see if I can try to point some good difference between EAI & ESB and perhaps SOA as all this is closely tied together while explaining how they are linked to each other too. SOA (Service Oriented Architecture) is an approach is to have software resources available (& discoverable) on network as … Continue reading Difference between SOA, EAI and ESB

Em muốn trở thành kiến trúc sư

Mình muốn kể cho mọi người nghe một câu chuyện là cuộc đối thoại ngắn giữa một anh chàng Developer trẻ và 1 anh Architect. Cậu ta đến gặp anh kiến trúc sư và tâm sự là muốn trở thành 1 kiến trúc sư như anh. Sau này em cũng muốn trở thành 1 Software … Continue reading Em muốn trở thành kiến trúc sư

Multilayered Architecture (5) – The Presentation Layer

by Marco Di Stefano Introduction The final piece of a MultiLayered Architecture, in term of development design and dependencies is the Presentation Layer. It has mainly the scope to create an Interface with the final User of the application. It can take the form of Desktop forms, Java Applet, Web application and any other possible solution provided … Continue reading Multilayered Architecture (5) – The Presentation Layer

Multilayered Architecture (4) – The Infrastructure Layer

by Marco Di Stefano Introduction What is Infrastructure? If we think at a building, Infrastructure is what brings light and water. You can build a wonderful house, but if you don’t connect it to the city infrastructures, you will never be able to live in it. Finally this building is able to receive water and light, but is not … Continue reading Multilayered Architecture (4) – The Infrastructure Layer

Multilayered Architecture (3) – The Application Layer

by Marco Di Stefano Introduction As Business Documents are considered the input for the Domain Layer, System Requirement Specifications are the main input document for the Application Layer. Scope of this layer is to provide an implementation of the defined requirements for the system. So it is easy to understand that most of the logic contained is process oriented and so linked to … Continue reading Multilayered Architecture (3) – The Application Layer