Aaannd another release of REST Assured, this time it hits 5.5.5. It reintroduces a working bom project again. It was accidentally missing in 5.5.3 due to lots of changes in the sonatype/maven central release process. Hopefully it should be working again now.

Just released REST Assured 5.5.3 with improved csrf support. CSRF now automatically handles cookie propagation correctly.

REST Assured 5.5.2 was just released with improved cookie support and minor changes.

Awaitility 4.3.0 was just released with improvements to Kotlin DSL and new ways of using "untilAsserted".

REST Assured 5.5.1 was just released with some bug fixes and improvements. Enjoy!.

Thanks a lot @aws for sponsoring me on @github 🙏.

RT @_sara_p_: The aggregate has always been, for me, one of the most controversial and weakest elements of the DDD theory. I want to show y….

RT @bwaidelich: Just had a great talk with @johanhaleby and @Pkgrimshaw discussing #DynamicConsistencyBoundary ideas. I hope that we can re….

RT @owickstrom: I'll be looking for work soon! Starting early next year, remote from SE. Autonomous testing, distsyst, web, data eng, PL, a….

And of course, the whole point of DDD is to solve business problems, and one shouldn't get bogged down by non-essentials. But sometimes it's fun, and useful, to discuss esoteric things :). @maciejwalkowiak @waltervos. #DDDesign.

Another important thing: DDD aggregates are used in conjunction with (DDD) repositories and services, and the purpose is to enforce domain consistency while abstracting away technical concerns (like persistence).

. whether through methods or pure functions. In both cases, the aggregate’s consistency is maintained as a unit.". What I like about this definition, given that it's right, is that it works for both OOP and FP and doesn't talk about "objects" (which is an overloaded term).

"In the context of DDD, an aggregate is a consistency boundary within the domain, where business rules and invariants are enforced through a set of behaviors that operate on a cluster of related data. It ensures that all state transitions conform to business rules, . .

. many things, but I truly want to be less wrong :). So with that out of the way, here's my take on a definition:.

. context of DDD, which is all about context 🤣 However, I still find it useful for myself to do these kinds of mental gymnastics sometimes. First of all _I_ really enjoy it, given that it's done in good faith and a real sense of wanting to understand. I know that I'm wrong on. .

I get that this is true in general, I mean, try defining all aspects of a "Game" without a context. Socrates tried to do things like this, and failed, because it's impossible without context (like Wittgenstein pointed out). It's extra interesting that I missed this in the. .

FWIW, I think I've finally figured out my flaw in thinking about what an aggregate is :) Definitions of "aggregate", including the one posed by @VaughnVernon, must be seen in a greater context, the context of DDD. While this is obvious in hindsight, it made me a bit confused.

RT @wimdeblauwe: htmx-spring-boot is now on 🎉. Thank you @m_halbritter for making this possible. .

Awaitility 4.2.2 was just released with a single important bug fix for early-access JVM versions.

RT @u_map_prop: Yo, flix ( looks actually really good. It ticks all the boxes for an advanced, modern functional pr….