Discover and read the best of Twitter Threads about #outboxpattern
Most recents (2)
#ApacheKafka has integrations with most of the languages used these days.
@alexsotob covers its integration with #Java and discusses how to provision, configure & secure an Apache Kafka cluster on a #Kubernetes cluster: bit.ly/3HN0Tqw
#InfoQ
Series Contents 👇
@alexsotob covers its integration with #Java and discusses how to provision, configure & secure an Apache Kafka cluster on a #Kubernetes cluster: bit.ly/3HN0Tqw
#InfoQ
Series Contents 👇
2/6 ➡️ Apache Kafka is a stream-processing platform for storing, consuming, and processing data streams in real-time. Learn how to produce and consume data using Kafka and Quarkus: bit.ly/3HGby6x
#ApacheKafka #Quarkus #Java
#ApacheKafka #Quarkus #Java
3/6 ➡️ The Kafka Streams project consumes real-time streams of events as they are produced, apply transformations, join streams, etc. Learn how to use Kafka Streams and Quarkus: bit.ly/3RGUbqy
#KafkaStreams #Quarkus #Java
#KafkaStreams #Quarkus #Java
My blog post "Event Driven Architecture — 5 Pitfalls to Avoid" just crossed 45K views!
some important comments i've received in 🧵1/3
link: medium.com/wix-engineerin…
@WixEng
some important comments i've received in 🧵1/3
link: medium.com/wix-engineerin…
@WixEng
1. What about using #OutboxPattern?
While a good pattern to use, for @WixEng we decided that #WixGreyhound Resilient producer provides high enough evnt publishing guarantees that we can avoid the extra DB pressure and complexity of Outbox. We may go with #Debezium as well 2/3
While a good pattern to use, for @WixEng we decided that #WixGreyhound Resilient producer provides high enough evnt publishing guarantees that we can avoid the extra DB pressure and complexity of Outbox. We may go with #Debezium as well 2/3
2. Event-driven architecture #EDA and #EventSourcing are unrelated. one talks about services communication while the other on persistent layer
Yep, you're right! I should add a disclaimer here... but event-sourcing will affect how you communicate between services... 3/3
Yep, you're right! I should add a disclaimer here... but event-sourcing will affect how you communicate between services... 3/3
