Hi all
In December Adrian Cockcroft presented some big names distributed
architectures in his talk State of the Art in Microservices at dockercon.
For each he put tooling/configuration/discovery/routing/observability on
top and then under datastores, orchestration and development. One can see
some
Hello
I've been reading about kafka and its use in a distributed system,
authentication handling remains a mystery to me.
Indeed, when the user connects to the website, many services are triggered
: how do they make sure the user is authenticated and authorized ?
I mainly see two options :
- eac
a store. You can use it to
> store
> > history of the queue (certainly a powerful use case for disaster
> recovery),
> > but it's still not really a data store.
> >
> > From the Kafka website (kafka.apache.org):
> > Apache Kafka is a publish-subscribe messagi
Hi
Having read a lot about kafka and its use at linkedin, I'm still unsure
whether Kafka can be used, with some mindset change for sure, as a general
purpose data store.
For example, would someone use Kafka to enforce an "unique constraint"?
A simple use case is, in the case of linkedin, unicity
