Відео

The original Agile Manifesto lays out 4 simple values: 0:00 Intro 0:30 Responding to change over following a plan 2:02 Customer collaboration over contract negotiation 3:23 Working software over comprehensive documentation 4:38 Individuals and interactions over processes and tools 5:25 Conway's Law It's not about sprints or standup meetings. agilemanifesto.org/

Message bus communication often uses Commands and Events. But, what's the difference between them? Aren't they both just messages? The difference is about grammar, intention, and also the direction of some different kinds of arrows... 0:00 Intro 0:18 What do the words mean? 0:34 When do they happen? 1:36 Who are they for? 2:53 Direction of control and dependency 4:19 Example third party provide...

The Transactional Outbox Pattern ensures a message is always published to a message broker when making changes to a database, even if the message broker fails initially. This is essential for event-driven architecture to ensure consistency when other services are rebuilding state from your events. 0:00 Network failures 0:54 Atomic Transactions 2:00 Publishing the event 2:52 At-Least Once delive...

The communication structures in your organisation influence your software architecture. We explore some examples of this and explain how it relates to Domain-Driven Design (DDD) and Microservices. 0:00 Definition 0:31 Layered teams example 2:04 Lifecycle teams example 3:07 Cross-functional teams & DDD 4:22 Inverse Conway Manoeuvre Conway's Law: www.melconway.com/Home/Conways_Law.html Inverse Ma...

What is Event Sourcing? Is it anything to do with CQRS and DDD? We explain the pros and cons compared to traditionally updating the current state in a database. We cover trade-offs with Eventual Consistency, problems with concurrency, and options to solve those with optimistic concurrency techniques. 0:00 Intro 0:40 Deleting 0:57 Analytics & Metrics 1:23 Concurrency 2:24 Calculating State 3:26 ...

Microservices, a Modular Monolith, or a Big Ball of Mud. This video explains the pros and cons of choosing a distributed system over one big monolith (whether that's a nicely structured Modular Monolith, or just a jumble of spaghetti code). 00:00 Definition of Microservices 00:14 Monoliths 00:35 Big Ball of Mud 00:52 Modules 01:30 Microservices 02:17 Network Communication 02:59 Distributed Ball...

Bounded Contexts, subdomains and strategic design from Domain-Driven Design explained. 0:00 Complex Systems 0:26 Ambiguous Language 1:26 Separating Contexts 2:06 Context Map 2:22 Types of Subdomains 3:11 Integrating Between Contexts

Explaining Aggregate Roots, Domain Events, Entities, Value Objects and Repositories - the building blocks in Domain-Driven Design. 0:00 Building Blocks 0:18 Ubiquitous Language 0:54 Value Objects 1:41 Entities 2:22 Domain Events 2:51 Aggregates 3:39 Repositories

The CQS and CQRS design principles explained. 00:00 CQS: Command Query Separation 01:29 CQRS: Command Query Responsibility Segregation 2:10 Separating reads and writes 2:37 Scaling independently

Three similar software architectures explained. 00:00 N-Tier Inversion 01:04 Hexagonal Architecture 01:50 Onion Architecture 02:58 Clean Architecture Hexagonal Architecture - alistair.cockburn.us/hexagonal-architecture/ Onion Architecture - jeffreypalermo.com/2008/07/the-onion-architecture-part-1/ Clean Architecture - blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html