Thread by @jessitron

Anyone who says to you “this architecture is universally applicable”
is probably selling something,
and not doing a very good job at selling something.

@tlberglund #DevoxxPL

Don’t use event-driven architecture for a small system or for an exploratory spike.
“learn what you’re trying to do before you elaborate your architecture.”
@tlberglund #DevoxxPL

Databases don’t go away when you’re using events.

If nothing else: when you need lookup by multiple keys, databases are necessary views on the system of record (which is the event log).

@tlberglund #DevoxxPL

the event log as system of record gives us relatively more opportunity to make this a more evolutionary architecture.

Yes you still need to care about schemas, and how they change over time.

~ @tlberglund #DevoxxPL

When you start with a database, you start by thinking about things.
When you start with events, you start by thinking about what happens (and then later you consider the things).

@tlberglund #DevoxxPL

You implement something a second time, then a third, then you want to build a framework
It’s a trap! Don’t build a framework!

@tlberglund #DevoxxPL

Your job is to deliver value to your business customers.
There are all kinds of infrastructure temptations that you must resist,
however fun they might be to solve.

(Don’t build the framework! And managing time in a distributed system is hard!)

@tlberglund #DevoxxPL