rreppel

4 ms·

1.
by rreppel 9y ago
Yes ... it's a very powerful pattern and Redis streams look promising; building event sourced systems is still perceived as difficult, but I think a lot of that is because people are picking overly heavy, complicated plumbing for it wh
2.
WHAT IS a MICROSERVICE? An overdue clarification(adaptechsolutions.net)
2 points by rreppel 10y ago|0 comments
3.
It's a lot like SQL: Why Domain Driven Design witho core domains is mostly useless(adaptechsolutions.net)
3 points by rreppel 10y ago|1 comments
4.
by rreppel 10y ago
Open sourced ones? The largest example I'm aware of is https://github.com/MicrosoftArchive/cqrs-journey . There's a pretty extensive write-up of their experiences too. https://msdn.microsoft.com&#x2
5.
by rreppel 10y ago
Just don't do eventual consistency if the domain doesn't allow for it and if performance is OK. From a functional perspective there is no need for it in CQRS/ES systems. However ... if going with eventual consistency, it&#x27
6.
by rreppel 10y ago
I don't really do eventsourcing for technical reasons. To me it's about creating an environment for project delivery where teams can succeed because they own more of their stack, from an org chart & organizational perspective.
7.
by rreppel 10y ago
No, haven't tried them yet. Does look interesting for it, though.
8.
by rreppel 10y ago
Agree with the potential for complexity. Here's how we've dealt with this (on a so far / so good basis): Didn't seem necessary to go asynchronous and beef up on heavy infrastructure, so we went with simple in-thread, in
9.
by rreppel 10y ago
Always a problem with techie - acronymania. :) Thanks, noted. I'll do an edit.
10.
by rreppel 10y ago
We find that a simple in-memory synchronous message bus + event logging to files goes a long way. See e.g. https://github.com/robertreppel/hist for an in-memory bus + file system (and DynamoDB ...) helloworld which isn