The Core Of Google’s Recommended Flutter Feature DDD App Arch, Event Sourcing

No Flutter GDE seems to understand that to implement Google’s DDD Feature Flutter App Architecture hinted in the Flutter Skeleton App template one has to implement the CQRS-ES set of patterns. CQRS is command query responsibility segregation and the ES part is event sourcing.

This article will cover the event sourcing part, which of course implies reactive events using reactive programming.

The Reactive Programming Core, The App Observable Logger

It is ill-formed myths about antipatterns that can kill the UX responsiveness of our Flutter app, in this case it’s both singletons and event buses. In the case of singleton’s while the use cases of singletons are not as wide when it got introduced as an OOP pattern during C++ heyday; it still can be used for those use cases where it’s an OOP item that we never test in the first place such as app loggers.

In the event bus use cases, it was not the event bus itself that was the actual antipattern, but the fact that they were implemented in non-reactive programming ways that presented bottlenecks in the communication between application components.

And both things implemented in the right avoiding antipatterns way that form the Event…