#architectureweekly — Public Fediverse posts

What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming

What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming

What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming

What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming

What compilers have to do with event-driven pipelines? At first glance? Nothing! But after thinking about the new design in #Emmett, I changed my mind!

I wrote today on #ArchitectureWeekly on how building an Event-Driven pipeline led me to writing my own compiler. Oh well, small one, simple one, but still.

Read also about more surprising places besides programming languages when compiling happens, and helps your applications!

https://www.architecture-weekly.com/p/compilation-isnt-just-for-programming

I've been facilitating the #EventStorming sessions for years now, and something keeps catching my attention.

While teams naturally focus on mapping out those orange event sticky notes (the backbone of any EventStorming session), they often underestimate the power of two critical elements: Hot Spots and Notes.

What I value most about Hot Spots and Notes isn't just how they improve workshops - it's how they change team culture around uncertainty.

In technical discussions, we often feel pressure to know everything immediately.

Hot Spots create permission to say, "I don't know yet" while still making progress. They transform uncertainties from conversation-killers into clearly defined next steps.

I've seen teams evolve from hiding what they don't know to actively hunting for uncertainties as valuable information. Questions become assets rather than liabilities.

If you're incorporating EventStorming into your toolkit, don't underestimate these powerful elements. They might not get as much attention as domain events, but in my experience, they often separate a productive modelling session from a frustrating stalemate.

Read more in the latest #ArchitectureWeekly: https://www.architecture-weekly.com/p/the-underestimated-power-of-hot-spots

Object-oriented or relational? Why not both?

For many years, we tried to fit the business data into a normalised table structure. We used Object-Relational Mappers, which was a constant battle on how to map unfitting models.

Then document databases like MongoDB came along and got traffic.

Still, many people wanted guarantees they had in relational databases, they also wanted to reuse muscle memory related to operations and other tooling.

Now we have the choice as we have #JSONB data type implemented by #PostgreSQL and then by MySQL, SQLite.

The B in JSONB stands for binary. It looks like a JSON, it quacks like a JSON, but it's not JSON. And thanks to that, it's powerful.

When you're storing JSON data in JSONB, it's parsed, tokenised, and stored in a tree-like structure. Types are preserved, and a hierarchical structure is also preserved, and thanks to that, you can index it and efficiently query it.

I'm super happy that in recent years, I have had the opportunity to use Postgresql and JSONB, first in Marten and now in Pongo. I didn't look back. JSONB has its cons, but for most typical line-of-business applications, they're negligible.

I finally wrote an intro in #ArchitectureWeekly about how JSONB works, check it, tell me how you liked it and share with your friends!

And most importantly, play with it on your own 😊

https://www.architecture-weekly.com/p/postgresql-jsonb-powerful-storage

As I'm working on adding observability #Emmett and #Pongo, I decided to return to this idea and show how tests can drive predictable observability!

Check the latest #ArchitectureWeekly release to see my take: https://www.architecture-weekly.com/p/making-your-system-observability

As always, feedback is more than welcome!

4/4

#OpenTelemetry #Observability #softwareengineering