solution architecture

In this week’s podcast, Thomas Betts talks with Chris Richardson, a developer, architect, Java Champion and author of POJOs in Action. Before his workshop on Microservices w/ Spring Boot and Docker at QCon San Francisco 2016, Richardson took time to discuss his ideas on how to use DDD and CQRS concepts as a guide for implementing a robust microservices architecture.

Why listen to this podcast:

 - "Microservice architecture" is a better term than "microservices".   The latter suggests that a single microservice is somehow interesting
 - The concepts discussed in Domain-Driven Design are an excellent guide for how to implement a microservices architecture
 - Bounded Contexts correspond well to individual microservices
 - Event sourcing and CQRS provide patterns for how to implement loosely coupled services
 - When converting a monolith to microservices, avoid a big bang rewrite, in favor of an iterative approach

Notes and links can be found on: http://bit.ly/2hZ8TM1

11m:51s - Microservices must be loosely coupled, usually creating a model with one database per service.
12m:45s - There is a business requirement to maintain data consistency across services, and using an event driven architecture is a good way to achieve that.
13m:38s - Event sourcing is specific technique for persisting domain objects as a series of events.
14m:11s - Just as transactions don’t like to be split across microservices, queries cannot simply join across multiple data sources. CQRS provides a solution that accommodates querying via microservices and materialized views.

More on this:
Quick scan our curated show notes on InfoQ. http://bit.ly/2hZ8TM1

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

InfoQ Podcast

Show Notes

Chris Richardson on Domain-Driven Microservices Design

In this episode of the O’Reilly podcast, Jon Bruner sat down with Rahul Kamdar, director of product management and strategy at TIBCO Software. They discussed the shift from the centralized enterprise service bus (ESB) to a distributed data architecture based on microservices, APIs, and cloud-native applications.

From Enterprise Service Bus to Microservices

Happy New Year and welcome to the first episode of the Cisco UKI Podcast. In this episode, we are discussing Software Defined Access (SDA) with experts James Harrop and Andy Dobson. They explain what it is, its benefits to an organization and considerations if you want to move to a SDA architecture.

Ep50 Software Defined Access Explained

In episode 33 of Mobycast, we begin a new micro-series on Event-Driven Architecture. In
particular, we discuss the how and the why as well as the Pub/Sub design pattern. Welcome to
Mobycast, a weekly conversation about containerization, Docker and modern software
deployment.

Event-Driven Architecture (Part 1)

In episode 34 of Mobycast, we dive into part 2 of our micro-series on Event-Driven Architecture. In particular, we discuss a few practical examples used at Kelsus. Welcome to Mobycast, a weekly conversation about containerization, Docker, and modern software deployment.

Event-Driven Architecture (Part 2)

Alan Boucher is the Director of IT for Software Product and Development and Architecture at IDEXX. IDEXX serves its veterinary customers on two business platforms; diagnostics business and reference lab business. As we unravel how they serve their clients, we see just how complex their platform is, serving the needs of veterinarians, farmers, and other companion animals facilities. Running a department that deals with such technologies requires lots of organization. Listen to this episode to hear Alan share how his methods of portfolio management make management in his industry possible.

solution architecture

Govi Sun