GRPC is based on ProtoBuf and is build on contracts that each server or client can implement and rely on. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication.¹ GRPC is a modern open source high performance RPC framework that can run in any environment. While we liked the overall approach writing Atom feeds felt kind of old-school. Each service needs to reimplement the refresh and event persistence logic itself and in an ideal world provide the feed in an aligned architecture-wide format. Those feeds are backed by a persistence layer in the service itself. One decentralized approach is to work with Atom feeds where every service publishes a feed of changes that others can subscribe to and replicate the data. At the same time, it removes the need for one of our product teams to own and maintain the additional central component. With Kafka ruled out we made our minds up about a decentralized solution, not relying on that one central component, and which better fits our restrictions. That being said, adding Kafka to the operational model would be a nightmare for most of our customers as it would raise the operational costs by a lot. Still, we would need a reliable Kafka component that persists the events without gaps or outages otherwise, services are not in sync. Our customers in that model range from ten to over ten-thousand users. Next to our SaaS offerings we also offer an on-premises solution that is installable on the customer's own metal or virtual machines. While this is a very desirable target architecture for us, it is currently not implementable due to the operational model of our product here at COYO. Apache Kafka is a popular choice for this.
Most implementations of the EventSourcing concept heavily rely on a central component. These events reflect the made changes to the underlying domain data and can be subscribed to by consuming services that need a local representation of the data to be able to act on their own.
A producing service publishes state change events. One concept to deal with this is EventSourcing.
0 kommentar(er)
