Event modeling and domain driven design go hand-in-hand, and learning both was a huge turning point in my development career. It helps align software to the bus

Event modeling and domain driven design go hand-in-hand, and learning both was a huge turning point in my development career. It helps align software to the business, and technical to non technical staff in a way where everyone speaks the same ubiquitous language (when a user registers) more than other approaches (rest - when I POST a user, crud - when I create a user). It took me a few books and a couple of projects before the penny dropped, but now everything else seems disorganised and difficult to keep a lid on complexity as projects grow. If your in Nodejs/typescript land and wanting to get started with DDD and eventing like the article, there's: https://github.com/node-ts/ddd https://github.com/node-ts/ddd - basics for domain modelling, read/write repositories, aggregates/roots https://node-ts.github.io/bus/ https://node-ts.github.io/bus/ - event/command service bus, supports workflows/sagas, queue technology agnostic (runs over sqs, rabbitmq etc)