Using FModel to Structure Architecture from Route to Event Store | Pim van Gurp

Controllers have been the centerpiece of our application for a long time. We connect them to routes, validate the request and call our domain logic in the model.

But more software starts making events and commands the core of their domain. This is still interoperable with MVC, but it doesn't fit is as nicely.

This talk explores an alternative. Looking at the full server request lifecycle and making events and commands first class citizens using Kotlin FModel at it's core

[avwie]

But how is this not MVC? Eventsourced and state sourced are just implementation details, as they should be.

EventSourcing is great but it gets complex with projections and eventual consistency. The simple becomes hard then.