Patterns of Enterprise Application Architecture - Intro, Chapters 1 & 2

Patterns of Enterprise Application Architecture — Intro, Chapters 1 & 2

Martin Fowler

Introduction

Layering

Organising Domain Logic

1 / 13
volgende
Slide 1: Slide
newEditorSoftwareontwikkelingHBOStudiejaar 1

In deze les zitten 13 slides, met interactieve quizzen en tekstslides.

time-iconLesduur is: 45 min
Dit is niet oké

Onderdelen in deze les

Patterns of Enterprise Application Architecture — Intro, Chapters 1 & 2

Martin Fowler

Introduction

Layering

Organising Domain Logic

Introduction

Architecture a shared understanding of a system's design by the expert developers on a project.


Enterprise applications work with persistent, complex data together with business rules that fail all tests of logical reasoning.


Patterns describe a problem which occurs over and over, and then describes the core of the solution, in such a way the solution can be used multiple times without ever doing the same thing twice.

What does "Architecture" mean to you?

2

minute

00

second

Can you name any patterns we use in the LessonUp codebase?

2

minute

00

second

Chapter 1: Layering

Layering is an architectural principle for managing complexity. Organising systems into stacked layers, where a layer can only use the services of the layers immediately beneath it, ensuring separation of concerns.


The primary goal of layering is to reduce coupling between different parts of the application. By reducing dependencies, layering ensures that a change in one area requires minimal changes in other areas.

Thoughts on the three "principal" layers

Do you think the LessonUp codebase has appropriate separation of concerns?

A

Yes

B

No

C

Sometimes

D

I ain't concerned about separating anything

Chapter 2: Organising Domain Logic

Domain Logic is the business rules for an application, keeping this logic separate from the Presentation and Data Source layers is key to preventing code duplication.


No single solution works for every system; the strategy chosen for organising this logic must be directly proportional to the complexity of the underlying business domain.

LessonUp's Domain Logic

Within our own codebase, do you think our core business rules are primarily housed in simple, sequential blocks of code, or are they distributed across complex objects/components that contain both data and behaviour?

2

minute

00

second

The Service Layer

The Service Layer is designed to provide an explicit API and a clear boundary for the application, essentially defining its public contract for the rest of the world. Do you agree that creating a dedicated, explicit application boundary is a necessity for complex systems, or are there circumstances where the overhead of adding a Service Layer outweighs the benefits?

2

minute

00

second

What is your main takeaway from today's chapters?

2

minute

00

second

Next Time


Chapter 3: Mapping to Relational Databases

Chapter 4: Web Presentation