sideway

> do event-driven architectures work at all, and has anyone "fully embraced" it. It doesn't have to be "fully embraced" to be successful.

For context, I've seen successful event-driven architecture implementations when it comes to data ingestion for analytics/ML purposes.

What I have yet to see is a successful implementation of microservices using local state stores built by joining streams owned by multiple domains. That's where the (arbitrary) "fully embraced" term came from.

Does everyone implement the outbox pattern themselves? Or treat their streams as the only source of truth, materialising the state that is already embedded in them?

Interesting, does serverless help with data ownership?

You are right, that's what I was referring to.

I have seen DDD working sufficiently well for some use-cases but issues started appearing when the business redefined what the domains are and how the org is structured. I guess there is not a single straight-forward solution to this.

Thanks for your answer, it really helps.

Does moving the DLQ messages back to the normal queue mean that all consumers can deal with out-of-order scenarios?

Thanks for your detailed answer, really appreciate it.

Two follow up questions if you don't mind me asking, even though I understand you were not on the publishing side:

1. Do you know if changes in the org structure (e.g. when uber was growing fast and - I guess - new teams/product were created and existing teams/products were split) had significant effect on the schemas that had been published since then? For example, when a service is split into two and the dataset of the original service is now distributed, what pattern have you seen working sufficiently well for not breaking everyone downstream?

2. Did you have strong guidelines on how to structure events? Were they entity-based with each message carrying a snapshot of the state of the entities or action-based describing the business logic that occurred? Maybe both?

And yes, one of the books I'm talking about is indeed Designing Data Intensive Applications and I fully agree with you that it's a fantastic piece of work.

> For us, it's either a function that will retry the messages after some time, or manual intervention.

What does manual intervention look like? Are all downstream consumers blocked until the DLQ is emptied or do all consumers know how to deal with late-arriving events?

> and, frankly, threatens to take down the entire stock market

Could you expand on that?

> ...applying the value investing style. I thought this style is pretty much dead, because market efficiency has increased compared to the times when Benjamin Graham analysed securities by hand

Do you mean the manual part has gone out of style or fundamental analysis altogether?

My knowledge on finance/accounting is extremely limited and after watching some of his videos back in November, I took for granted that this is how this type of investors operate.

I've been following many threads on Reddit (and one on HN) about people getting fired already. As there is no indication this trend will be reversed any time soon, I get the feeling that a) lots of industries have already been hit hard and b) things may get progressively worse in the following months.

It worries me that, as a huge percentage of the web runs on ads, if lots of industries get into trouble, the ad space will inevitably suffer as well. The cascading effect of that will most probably affect in a very obvious way every company I've worked for, layoffs will oversaturated the market and my current skillset will be insufficient to give me any competitive advantage.

Would you mind elaborating?

You mean natural languages, not programming ones, right?