| Note |
|---|
During this discussion, we decided this book is not relevant enough to our current use cases. Unless that discussion interests you, you may wish to skip this. |
Discussion of the book https://learning.oreilly.com/library/view/building-event-driven-microservices/9781492057888/
Watch Recording: TODO: ADD LINK AFTER EVENT
Chapter 6 Outline
| Expand | ||
|---|---|---|
| ||
Chapter 6: Deterministic Stream Processing
|
Discussion Notes
...
It seems like if we need to make sure that multiple streams always have correct NTP-backed timestamps in order to avoid logic errors, this will never work satisfactorily in production over the long term.
The book is helpful in some places, terrifying in others; how can we flag which ones are which?
FYI: Arch-BOM has pivoted from a prototype using a credentials use case to using license-manager events instead.
This should be a very simple example that lets us just cover the basics first.
We do need to think about the fact that there will be latency
How much is acceptable?
Is this the wrong kind of book for what we need right now? Maybe enumerating the things we need to consider rather than offering advice on balancing them in practice?
No, even that would be more useful. More like “here’s a very complex solution, impractical for most use cases, that theoretically offers the best of all worlds but probably won’t in practice.”
Not clear about use cases, sort of assumes that all implementations will want to make the same trade-offs.
At least a few of us are struggling to keep up with the chapters, those who are keeping up aren’t sure how much they’re getting out of it.
Maybe something like https://www.confluent.io/dummies/ would be more useful? Unsure.
Seems to make the opposite choice for almost every item in the edX Architecture Manifesto
Links related to architectural goals related to event bus: