ast enough to allow
you to quickly skip through all the stuff you don't need...
On Mon, Mar 28, 2016 at 10:53 AM, Mark van Leeuwen wrote:
Hi all,
When using Kafka for event sourcing in a CQRS style app, what approach do
you recommend for mapping DDD aggregates to topic partitions?
Assign
oughput. And feel free to
replace ³publisherID² with ³TargetConsumerID² or ³OrderedEventBusID².
On 3/29/16, 7:38 AM, "Mark van Leeuwen" wrote:
Thanks for sharing your experience.
I'm surprised no one else has responded. Maybe there are few people
using Kafka for event sourc
ition granularity issue; another is the
lack of a way to guarantee exclusive write access, i.e. ensure that only a
single process can commit an event for an aggregate at any one time.
On Mon, 28 Mar 2016 at 16:54 Mark van Leeuwen wrote:
Hi all,
When using Kafka for event sourcing in a CQRS style app,
Hi all,
When using Kafka for event sourcing in a CQRS style app, what approach
do you recommend for mapping DDD aggregates to topic partitions?
Assigning a partition to each aggregate seems at first to be the right
approach: events can be replayed in correct order for each aggregate and
ther
om/about/contact.html>
On Mon, Mar 21, 2016 at 6:25 PM, Ben Stopford wrote:
It sounds like a fairly typical pub-sub use case where you’d likely be
choosing Kafka because of its scalable data retention and built in fault
tolerance. As such it’s a reasonable choice.
On 21 Mar 2016, at 17
nly mainly used in one region.
I recently went to a Firebase event, and it seems a lot more fitting. It
also allows the user to see it's own changes real-time, and provides
several authentication options, and has servers world-wide.
On Mon, Mar 21, 2016 at 7:53 AM Mark van Leeuwen wrote:
Hi
veral authentication options, and has servers world-wide.
On Mon, Mar 21, 2016 at 7:53 AM Mark van Leeuwen wrote:
Hi,
I'm soon to begin design and dev of a collaborative web app where
changes made by one user should appear to other users in near real time.
I'm new to Kafka, but
Hi,
I'm soon to begin design and dev of a collaborative web app where
changes made by one user should appear to other users in near real time.
I'm new to Kafka, but having read a bit about Kafka streams I'm
wondering if it would be a good solution. Change events produced by one
user would be
