frankdejonge

4 ms·

31.
by frankdejonge 5y ago
Any exposed information should be exposed deliberately. Although I didn't cover it in this post. In my event-driven setups, events are always wrapped in a message envelope data structure. Where a message is contains 1) the event/p
32.
by frankdejonge 5y ago
I've worked on a real-time dashboard for operational insights for an airport once where they initially used eventstore to do effectively the same thing. We ended up replacing eventstore with a similar setup using typescript and kafka,
33.
by frankdejonge 5y ago
For anyone who's interested in the outbox pattern, I also blogged about that: https://blog.frankdejonge.nl/reliable-event-dispatching-usin...
34.
by frankdejonge 5y ago
If I understand your forth type correctly, it's like snapshotting in an event-sourced system. For me those are only internal and not meant to be communicated, rather they are there to speed up reconstitution of an event-sourced aggrega
35.
by frankdejonge 5y ago
When domain events are the "trigger", RESTful events can exist without an explicit "trigger" type of event. If you look at the payload, they are different, but sometimes one is used for the same purpose as the other, int
36.
Types of events in event-driven systems(blog.frankdejonge.nl)
137 points by frankdejonge 5y ago|42 comments
37.
by frankdejonge 7y ago
My typing speed is not the bottleneck for me either, but the double bookkeeping certainly is. It takes me from "problem solver" to "code writer", a context switch I gladly live without. Type inference helps with that.