It's been 8 years since I started Adaptech Group. We're about to open another office in Quebec! What a great feeling being able to help so many clients and free them from the dysfunction of the software industry. They are ready for an incredible future!

Our clients:

- don't lose any data
- keep their costs constant as they add features
- actively collaborate across their entire organization
- slash their overhead in tooling, management and process
- have solutions built to scale with increased demand
- are not vendor-locked
- are leveraging open source to keep costs down
- and many, many more advantages

Our unique approach using the combination of #EventModeling and #EventSourcing is about to take off with what #AI is providing. I'm so happy that everyone that saw the light and believed in our approach - you're about to tap the benefits of building the right way.

Thank you to Nicolas, Jonathan and everyone that joined since. Here's to another 8 years!

I think that prototyping is an underestimated design skill. We immediately fall to whiteboard diagrams, sticky notes, or endless discussions when we think about the design.

But there's another way.

I showed that in my last article using the following ingredients:
- Type-Driven Design,
- Decider pattern,
- #EventSourcing
- and code that with C# and #Marten.

https://event-driven.io/en/prototype_underestimated_design_skill/

Do you prototype while designing or just sticking paper to the wall? 😀

I need your help! 🥺🙏
#EventSourcing adaption is growing. Yet we still lack resources taking you from point A to Z. I'd like to change that and provide an online course soon. Yet, I'd like to be sure that's something covering your needs.

I'd be grateful if you filled short survey: https://event-driven.io/en/online_course_survey/

Resharing and comments also count!

Hey #DDD and #EventSourcing community. Are there any event-sourcing databases that aim for simplicity? A bit what sqlite is for relational databases. But aimed at storing events.

Hell, even storing json-on-disk would work, I guess.

I doesn't need thousands of tps, nor load-balancing or redundancy and such. Like SQLite, storing on disk is fine for my use-case, and, like sqlite, having it integrated in the app preferable over a separate service.

Anything?

A new release of `fmodel-ts` library has been published 🎉 "v1.3.2" 🎉. It aims to bring functional, algebraic, and compositional domain modeling to #TypeScript. It is inspired by #DomainModeling, #EventSourcing, and Functional programming communities. 💙https://github.com/fraktalio/fmodel-ts/releases/tag/v1.3.2💙

Time to get hands dirty and check if #EventSourcing and #WebAssembly is a good matching 😎

A tragedy of the commons for data:

The idea that your single normalized model is "least bad" for each piece of functionality in your system - one model cannot be ideal for each piece of functionality. So, even for trivial cases, organizing of coupling by #EventSourcing is superior. No one particular functionality is going to dominate a model that others are forced to use.

Excessive coupling is almost immediately introduced to the simplest of CRUD systems where one tidy normalized model is forcing you to compromise on what can satisfy all your different needs in the system. It's making a trade-off in that a single projection into that canonical model that serves every screen or web page of your application is more efficient than managing multiple separate models per purpose.

1/2

#DomainModeling #EventSourcing #Kotlin #Multiplatform https://fraktalio.com/fmodel

@jeremydmiller was joking that I’m the Critter Stack #EventSourcing part Product Owner. It came from the fact that we were discussing a lot around design, but I haven’t got my hands dirty in #Wolverine. Time to change it!

Next Wednesday, 2nd of August, we’ll do a webinar for #ArchitectureWeekly paid subscribers taking my sample Helpdesk application and refactoring it live to fully benefit from #Wolverrine goodies.

https://www.architecture-weekly.com/p/invitation-to-webinar-with-jeremy-ad2

1/

The intriguing aspect is that #EventSourcing also can help in that, as your write model is ephemeral. That sounds posh, but it means that it's always build in memory from events.

Thanks to that we can change it and tune it to our needs as long as we have data in events.

Thoughts? 🤔

3/3

Back in 2009 I was doing nothing but #eventsourcing and some of the biggest names in the community and open source were ridiculing me publically. Those same people are trying to sell me their event sourcing frameworks today after running out of ideas on ways to avoid event sourcing and bring the same benefits.

I see the same thing happening with #EventModeling. It's funny to see effort on the different takes on modeling (including trying to add UX and UI and example data) and effort used to avoid mentioning EM.

I'm happy that I now have a company #adaptechgroup full of experts on these key ways of automating systems. It took a long time and a lot of effort to get here.

FModel v3.5.0 has been released. For more information take a look at https://github.com/fraktalio/fmodel/releases/tag/v3.5.0. FModel is a set of #Kotlin #Multiplatform libraries optimized for #EventSourcing, #CQRS, and #DomainModeling. Check out the reference guide https://fraktalio.com/fmodel/

I feel that the DevOps aspect of #EventSourcing tooling is not covered enough. Time to change it and get more content on it!

In my latest article, I recommended setting up a Docker image for the #Marten application. Not as complicated as it may seem, the most important is correctly configuring the code generation setup to get the best performance.

If you already did such a configuration, is it similar to yours?

https://event-driven.io/en/marten_and_docker/

I will share best practices for testing software systems that use modern software architecture patterns such as #EventCollaboration and #EventSourcing at #IPCon in October in Munich:

https://thephp.cc/dates/event-based-testing-international-php-conference

Look what I found in Gdynia! That looks like a good fit for the #EventSourcing fanboy like me 😄

Folks, I need your help. What would you like to find in docs when evaluating #EventSourcing tooling?

I’m planning to revamp our #Marten docs around #EventSourcing. I have an initial plan for how to do it, but any feedback with a fresh perspective would be super helpful 🙂

Thanks in advance for comments and regarding for reach 🙂

Learn how Building Blocks (like Aggregates, Sagas and Event Sourcing), enable developers to build domain-focused applications while abstracting away the complexities of integration.

https://medium.com/@dariuszgafka/building-blocks-exploring-aggregates-sagas-event-sourcing-with-ecotone-aadd6c00216f

#ddd #development #architecture #php #eventsourcing

Folks, #EventSourcing can be pragmatic, practical and straightforward, and I have a proof for that: https://m.youtube.com/watch?v=jnDchr5eabI

I know that’s a bold statement, but I believe that and tried to show that in my talk at #NDCOslo.

If you’re looking for a quick, practical, hands-on intro, I think that’s a decent starting point.

Btw. I’m super happy and proud that I gave talks back-to-back talks and #NDCOslo. A few years ago, I wouldn’t believe that!

Explore Business Oriented Architecture with Ecotone:
https://dariuszgafka.medium.com/revolutionary-boa-framework-ecotone-61e168dd55e6

#php #ddd #boa #eventsourcing #messaging

When I'm explaining #EventSourcing to my non-developer friends; then usually the look is: "ok, and why is it so special?". And the reason why they're saying that is intriguing.

It's "weird" because, for them, the need to keep all business information and store business facts is obvious. They're surprised that traditionally we're not doing that.

So they're rolling their eyes not because it's something unusual but because they believe that should be already a common thing from their perspective.