Robert Baelde retweeted
Replying to @codeopinion
"Most developers have never seen a domain model, only a data model."
— @cyriux
Robert Baelde retweeted
Once you learn how to model an application based on behavior instead of CRUD (data bags and transaction scripts) it's FAR easier than using CRUD.
I absolutely CAN NOT be the only one to feel this way.
Robert Baelde retweeted
CRUD / data-centric software design doesn't scale.
Without behavioral modeling we can not succeed in designing distributed services.
The result of data-first distributed systems design is a 'distributed monolith', a too-typical anti-pattern.
Robert Baelde retweeted
Watch this talk with @RobertBaelde: buff.ly/49vIniA By the end of the talk, you will have a better understanding of the different strategies available and how to choose the one that best fits your requirements.
Join us for more at #DDDEU24!
Robert Baelde retweeted
If you’re running a business, “We need to refactor this module.” is not something you’d like to hear. It doesn’t mean anything unless you come from a technical origin. In fact, it’s a scary statement because that means you need to change something that was somehow working before.
Robert Baelde retweeted
Watch this talk with @RobertBaelde: youtu.be/0xb88_ugmn0 By the end of the talk, you will have a better understanding of the different strategies available and how to choose the one that best fits your requirements.
I recently had the opportunity to speak at KanDDDinsky about domain-driven design and scaling systems by minimizing transactional boundaries.
The recorded session is now available! 🍿
In today's #AdventOfTalks at #KanDDDinsky,
@RobertBaelde talks about Shrinking transactional Boundaries: Domain-Driven Design for High Traffic Scenarios
youtu.be/TaeKOKzW-Fc
7
231
Robert Baelde retweeted
The #EventSourcing struggle.
Robert Baelde retweeted
One of the most effective techniques for scaling the write ops in a software system is to shrink the consistency boundaries. How to do that? Asking business people how the process was working without computers! Great presentation by @RobertBaelde at @KanDDDinsky!
Robert Baelde retweeted
The one factor that made the most impact on my skill as an engineer was spending years pursuing DDD.
I went from a data-model first developer to a behavior-first developer and the benefits have been clear and profound.
oreilly.com/library/view/lea…
I recommend starting here.
Robert Baelde retweeted
📢 Exciting news!
Early bird tickets are still up for grabs this week! 🎟️✨ Don't miss out on the chance to hear from our stellar lineup of speakers!
Grab your spot now and get ready to collabolearn all about Domain-Driven Design and beyond.
#KanDDDinsky #DDDesign
Robert Baelde retweeted
I've seen people recently ask what Event Sourcing package they should use in PHP.
I exclusively recommend @eventsaucephp eventsauce.io/
It comes from a strong philosophical lineage and I've seen it rigorously battle-tested in high-scale environments.
Happy to be back at @ddd_eu again! This time I’ll be talking about replaying projections at the @EventSrcLive conference!
Robert Baelde (@RobertBaelde) is passionate about everything #EventSourcing and #DDD
Join him at #EventSourcingLive on June 7
🎟️ Get your tickets now: 2023.dddeurope.com/program/#…
youtu.be/DhMrqX_qrJE
10
314
Robert Baelde retweeted
🔥 This is one of the approaches to building a “decoupled from the framework” long term project with Laravel
Many people are wondering why?
It makes it easy to upgrade and maintain it in the long run.
You can’t see the full outcome now, but trust me, having worked on a project with hundreds, if not thousands of folders like the Role folder where many of them had a ton of complex and very important business logic, separating them like this makes sense.
I can already guess that this will be a complex project that Paul wants to keep maintaining it for years to come.
It may take a while to set things up in the beginning, it may look like over-engineering, and it may require a lot of thinking before writing the code but that’s the only way to make your life easier.
This does not mean Laravel or any framework is bad, but it means that the application is built with the framework as a tool, rather than the application becoming a chaotic mess wrapped inside of the framework’s structure and conventions.
I started building an API with #laravel. So far I've managed to avoid using the framework for 95% of the code
5% is thin controllers and routes
I'm using phpunit & phpstan
Zero eloquent, Zero models, just the query builder
I'm using TableGateway pattern, in the Repositories
Got inspired by @_sara_p_ 's talk, and implemented a basic implementation of it in php. Love the idea.
Biggest takes:
- An event can belong to multiple streams
- Consistency boundary changes per command
github.com/Robertbaelde/Mult…
Really enjoyed giving this talk, thanks for the opportunity @ddd_eu 🙌
Introducing bounded contexts often is a great first step to get started with DDD.
During this session, @RobertBaelde will teach you how a legacy application can be gradually refactored into bounded contexts.
youtu.be/DhMrqX_qrJE
Robert Baelde retweeted
Thanks to @RobertBaelde we finally got to see some #PHP8 code examples on #DDDesign at #DDDEurope
👏
Introducing #BoundedContexts in a monolithic application - Robert Baelde... youtu.be/DhMrqX_qrJE via @YouTube
Robert Baelde retweeted
If only more people knew how simple it can be to develop software without leaking relational databases throughout an application.
I remember teaching people to build object models mirroring normalized database schemas. I now regret that.
It's so much more complicated that way..
Robert Baelde retweeted
📦 EventSauce 3.0 is tagged! 📢
This release ships robust message replaying tools, championed by @RobertBaelde 🙌 The design supports rebuilding projections from long histories, even when replaying spans multiple deployments.
eventsauce.io/docs/advanced/…
Happy event sourcing!






















