Reactive Microservices

In this post I teach you a first-approach method to designing microservices, giving you a workable foundation to build on. Following this, I introduce you to reactive whole systems that are composed of individual reactive microservices.

Do you ever get the impression that our industry is one of extremes? Sometimes I get that impression. Many seem to be polarized in their opinions about various aspects of how software should be written or how it should work, whereas I think we could find a better balance based on the problem space that we face.
Continue Reading →

Why Software Hasn’t Worked for You

This article is meant, not primarily for the software developer or project manager, but for the strategically qualified and motivated business professional. Its goal is to challenge the status quo of business software development and introduce an approach that may appear as novel in most enterprises. This approach focuses on delivering critically distinguishing solutions that are intended to propel business toward greater commercial success.

Clearly software has worked. We have reached the point in time when it is said that “software is eating the world.” Why, then, do I assert that software hasn’t worked? Please re-read the title carefully, and put the emphasis on Worked for You.
Continue Reading →

Summary of CRDTs

In this article I am going to introduce you to CRDTs, or Conflict-Free Replicated Data Types. You will see under what conditions CRDTs might be useful, why you might want to use such a data type, what kinds of CRDTs are available, and how you can use them.
Continue Reading →

Building a Reactive Process Manager, Twice

On February 24, 2015, I delivered a presentation by this title to a meetup in the Netherlands. The group name is DomCode, and we had a packed house of more than 80 attendees. This topic not only drew a lot of attendees but held their rapt attention throughout more than an hour.

The first half of the presentation introduces you to Actor Model with Scala and Akka, and also includes a bit of discussion on using Actor Model with C# and Dotsero. Dotsero is my Open Source toolkit that supports using Actor Model on the .NET Platform.
Continue Reading →

The Ideal Domain-Driven Design Aggregate Store?

At the 2014 DDD eXchange in NYC, a park bench discussion developed around storing Aggregates. The consensus among the DDD leadership was against Object-Relational Mapping (ORM) and the desire to come up with a better way to store Aggregates. There were comments about ORM in general being an antiquated approach. While some developers are still new to ORMs, the technology of shoehorning objects into relational databases is more than 20 years old. In 20+ years, why haven’t we found a better way to store Aggregates?
Continue Reading →

Effective Aggregate Design

This is a three-part series about using Domain-Driven Design (DDD) to implement Aggregates. Clustering Entities and Value Objects into an Aggregate with a carefully crafted consistency boundary may at first seem like quick work, but among all DDD tactical guidance, this pattern is one of the least well understood. This essay is the basis for Chapter 10 of my book, Implementing Domain-Driven Design.
Continue Reading →

0

Your Cart