You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2024. It is now read-only.
I have few question relating to Zalando architecture and Nakadi.
Zalando has hundreds of microservices and most of them must be running in K8S.
Zalando has an event-based architecture. Do the microservices follow the Choreography pattern? Kafka is hidden behind Nakadi and microservices read/write from/to Nakadi. Am I right?
Zalando uses Kubernetes a lot. For example, you have a Postgres Operator. Does Nakadi (including Kafka) also run in Kubernetes, if yes, is there any operator available? If not, how do you ensure its High Availability?
Thank you.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi
I have few question relating to Zalando architecture and Nakadi.
Zalando has hundreds of microservices and most of them must be running in K8S.
Zalando has an event-based architecture. Do the microservices follow the Choreography pattern? Kafka is hidden behind Nakadi and microservices read/write from/to Nakadi. Am I right?
Zalando uses Kubernetes a lot. For example, you have a Postgres Operator. Does Nakadi (including Kafka) also run in Kubernetes, if yes, is there any operator available? If not, how do you ensure its High Availability?
Thank you.
The text was updated successfully, but these errors were encountered: