Download to read offline
More Related Content
Similar to Battle Tested Event-Driven Patterns for your Microservices Architecture - Developer Week
Battle Tested Event-Driven Patterns for your Microservices Architecture - Developer Week
- 1. natansil.com twitter@NSilnitsky linkedin/natansilnitskygithub.com/natansil Battle-tested event-driven patterns for your microservices architecture Natan Silnitsky Backend Infra Developer, Wix.com
- 2. >200M registered users(website builders) from 190 countries 5% of all Internet websites run on Wix 1,500 Microservices 1,500M Kafka messages produced / Day @NSilnitsky At Wix * Event driven uses cases
- 3. Agenda Event-driven microservices Event-driven patterns: •Consume and Project • Event-driven from end to end • 0-latency KV Store • Events in Transactions
- 4.
- 5. @NSilnitsky * Separately Monolithto Distributed Microservices System Microservices
- 6.
- 7.
- 8.
- 9.
- 10. @NSilnitsky Request-reply communication Microservices Communication Request-Reply Model HTTP RPC HTTPRPC HTTP RPC Checkout Service Payments Service Inventory Service User Service
- 11. @NSilnitsky Request-reply communication * 1 by1- slow Microservices Communication Request-Reply Model Checkout Service
- 12.
- 13. Broker @NSilnitsky * Reliability Event-driven communications Introducea message broker in between services Message Consumer Message Producer
- 14. @NSilnitsky * Notineteract directly Order created Event-driven communications Introduce a message broker in between services Event-driven model Message Consumer Flow control is moved from the sender Broker Message Producer
- 15. @NSilnitsky Order created Event-driven communications Introduce amessage broker in between services Event-driven model Message Consumer Flow control is moved from the sender to the receiver. Broker Message Producer * more robust
- 16. Kafka Broker Topic Partition Partition Partition @NSilnitsky *Linear scaling Introduce a message broker in between services Distributed log broker Event-driven communications Message Consumer Message Producer
- 17. @NSilnitsky Append-only log Introduce amessage broker in between services Distributed log broker Event-driven communications Kafka Broker Topic Partition Message Consumer Message Producer 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5
- 18. Order Created Topic 01 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 @NSilnitsky * Data retained, Immutable Introduce a message broker in between services Distributed log broker Event-driven communications Message Consumer Message Producer Kafka Broker
- 19. @NSilnitsky * eventuallyconsumed Distributed log broker eventually consume Event-driven communications Order Created Topic 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 Message Consumer Message Producer Kafka Broker
- 20. Checkout Service Event-driven communications Microservices communication &data Event driven model User Service Inventory Service Cart Service Payments Service @NSilnitsky
- 21. Checkout Service Cart Service Inventory Service Payments Service User Service Event-driven communications Microservices communication &data Event driven model Kafka Broker Orders Partition Partition Partition Users Partition Partition Partition Cart Partition Partition Partition Inventory Partition Partition Partition
- 22. Agenda Event-driven microservices Event-driven patterns: •Consume and Project • Event-driven from end to end • 0-latency KV Store • Events in Transactions * used daily. blog
- 23.
- 24.
- 25. MetaSite RPC Wix Stores Wix Bookings Wix Restaurants RPC RPC @NSilnitsky Consume and Project Site installedApps? Site version? Site owner?
- 26. MetaSite RPC Wix Stores Wix Bookings Wix Restaurants RPC RPC @NSilnitsky Consume and Project Request overload Site installedApps? Site version? Site owner? (~1M RPM requests) Read + Writes Large MetaSite Object
- 27. Request overload MetaSite RPC Wix Stores Wix Bookings Wix Restaurants RPC RPC @NSilnitsky Consume and Project Site installedApps? Site version? Site owner? Read + Writes Large MetaSite Object (~1M RPM requests)
- 28. Kafka Broker Produce to Kafka Producer MetaSite Site Updated! Consumeand Project Entire MetaSite Context
- 29. Kafka Broker Filter Site installed AppsUpdated! Installed Apps Context Produce to Kafka Consume and Project MetaSite Consumer Reverse lookup writer Consume and Project Producer
- 30. Kafka Broker Installed Apps Context Produce toKafka Consume and Project MetaSite Reverse lookup writer Reverse lookup reader RPC RPC RPC Split Read from Write Consume and Project Producer Consumer
- 31. Consume and Project —Produce instead of serve - massive load reduction — Project - client-query-optimized “Materialized View” — Read/write split - only scale read-only DB. more resilient
- 32. Event-driven from end toend 02
- 33. Kafka Broker Consumer Browser Producer Contacts Importer Service Contacts Jobs Service Web Sockets Service @NSilnitsky Event-driven from endto end Use case: Long-running async business process
- 34. Subscribe for notifications Consumer Producer Browser @NSilnitsky Event-driven fromend to end Use case: Long-running async business process Kafka Broker Web Sockets Service
- 35. Import CSVs Consumer Producer Browser @NSilnitsky Event-driven from endto end Use case: Long-running async business process Kafka Broker Web Sockets Service
- 36. Web Sockets Service Consumer * Distributed Producer Browser done! Event-driven from endto end Use case: Long-running async business process Kafka Broker
- 37. Web Sockets Service Consumer * Distributed Producer Browser Cross DC! Event-driven fromend to end Use case: Long-running async business process Kafka Broker done!
- 38. Event-Driven from Endto End — No polling - notify the user on any status change — Scalable - spin up many import job workers — Replication - cross-DC requests are easy to set up
- 39.
- 40. Kafka Broker Configuration Topic 01 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 K1 V1 K2 V1 K1 V2 K3 V1 K4 V1 K5 V1 @NSilnitsky Producer Key - value Consumer 0-latency KV Store Compacted Kafka Topics
- 41. Kafka Broker Consumer KVStoreReader In-Memory Map CompactedTopic 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 K1 V1 K2 V1 K1 V2 K3 V1 K4 V1 K5 V1 Key Value K1 V1 K2 V1 * Startup 0-latency KV Store @NSilnitsky Compacted Kafka Topics
- 42. 0 1 23 4 5 0 1 2 3 4 5 0 1 2 3 4 5 0 1 2 3 4 5 K1 V1 K2 V1 K1 V2 K3 V1 K4 V1 K5 V1 @NSilnitsky 0-latency KV Store Kafka Broker Consumer KVStoreReader In-Memory Map Key Value K1 V1 -> V2 K2 V1 K3 V1 Compacted Kafka Topics * Finished Compacted Topic
- 43. Consumer Consumer Bookings Business Manager KVStoreReader Time Zones Key Value AlbaniaUTC+1 Algeria UTC+1 Andorra UTC+1 Time Zones KVStoreReader Countries Key Value Albania .al Algeria .dz Andorra .ad Countries @NSilnitsky 0-latency KV Store Kafka Broker
- 44.
- 45. Kafka Broker Producer Bookings KVStoreWriter Time Zones TimeZones Consumer KVStoreReader Time Zones Key Value Albania UTC+1 ... South Sudan UTC+3 *New* Time Zone for South Sudan *New* Country South Sudan @NSilnitsky 0-latency KV Store
- 46. Kafka Broker Producer Bookings KVStoreWriter Time Zones TimeZones Consumer KVStoreReader Time Zones Key Value Albania UTC+2 Algeria UTC+1 Andorra UTC+1 *New* Time Zone for Albania Consumer Events KVStoreReader Time Zones DST in-effect for Albania @NSilnitsky 0-latency KV Store
- 47. 0-latency KV Store —Loading the compacted topic to memory – a 0-latency kv store for dynamic configuration — Compacted topic is still a topic – other services can consume its update events — Small Datasets - for large datasets, the topic should be streamed to a disk-based DB + In-memory Cache
- 48. Events in Transactions 04 *idempotent
- 49.
- 50. Payments Checkout Kafka Broker ProducerConsumer Producer Order (Items) Completed Events in Transactions Classic Ecommerce Flow Payment Completed
- 51. Payments Checkout Inventory Kafka Broker ProducerConsumer Producer Consumer Delivery Consumer Consumer Invoices Events in Transactions Classic Ecommerce Flow
- 52. Producer Consumer ProducerConsumer Consumer Consumer Completed Orders Events in Transactions Kafka Broker Classic Ecommerce Flow
- 53. Producer Events in Transactions Kafka Broker Enable.idempotence= true Attaches offset to message Classic Ecommerce Flow
- 54.
- 55. Events in Transactions Kafka Broker Producer 01 2 3 4 5 0 1 duplicate! 1 Payments Idempotent Producer
- 56. Transaction Scope Consumer ProducerConsumer Consumer Consumer Producer Events in Transactions Kafka Broker
- 57. Events in Transactions —Events transactions are quite complex – More boilerplate, performance tuning via transaction size. — DB updates/3rd party calls are not covered – You can dedup by using Kafka record offset as version — Don’t turn on transactions by default - Use in critical flows like payments processing
- 59. Wix developers haveemployed these event-driven patterns to make their microservices more decoupled, resilient and scalable.
- 60. A Scala/Java high-levelSDK for Apache Kafka. 0.1.5 is out! github.com/wix/greyhound
- 61. Thank You natansil.com twitter@NSilnitskylinkedin/natansilnitsky github.com/natansil
- 62. Resources 6 Event DrivenArchitecture Patterns - Part 1 & Part 2 - by Natan Silnitsky The Data Dichotomy: Rethinking the Way We Treat Data and Services - by Ben Stopford Shared Database - by Chris Richardson Exactly once delivery - DevOpsDay TLV 2019 - By Natan Silnitsky @NSilnitsky
- 63.
- 64. Q&A natansil.com twitter@NSilnitsky linkedin/natansilnitskygithub.com/natansil