Programmatic Ad Tracking: Let the power of Reactive Microservices do talking
0 likes37 views
The document discusses the transition from monolithic to microservices architecture in the context of programmatic ad-tracking at MIQ Digital, emphasizing the importance of reactive microservices and event-driven architecture. It outlines the technical aspects, advantages, and challenges of adopting such an architecture, including asynchronous communication and event storming. Key takeaways include avoiding microliths and embracing reactive principles for enhanced scalability and performance.
![18
Domain Driven Design
Aggregate Bounded Context
An Account
aggregate that
logically groups
account-related
commands and
events.
bounded contexts group
related language,
meaning, and culture
[bulkheads]](https://image.slidesharecdn.com/reactive-microservices-tech-triveni-sumita-mudgil-191127112415/85/Programmatic-Ad-Tracking-Let-the-power-of-Reactive-Microservices-do-talking-18-320.jpg){kind=tracking}
Programmatic Ad Tracking: Let the power of Reactive Microservices do talking
- 1. Reactive Microservices & Programmatic Ad-tracking Sumita Mudgil Tech Lead - MiQ Digital
- 2. 2 ❑ Miq & Programmatic Ad-tracking ❑ Monolith & Microlith ❑ What is Reactive Microservice? ❑ Microservices come in and as systems ❑ Event Driven Architecture ❑ Event Driven Services ❑ Event Storming ❑ Summary Agenda
- 3. 3
- 4. 4 The use of software to purchase digital advertising. Programmatic can apply to anything from display to digital out-of-home and television.
- 5. 5 Using computers to buy ads.
- 6. 6 Daily Scale at MiQ 10+ TB Data Avg response time per request < 7ms Real time data processing < 1sec 60+ Data sources integrations 900,000 CPU minutes everyda y 80 Billion Ad Impressi ons 750 million users 600+ advertiser s 2500+ campai gns Tech Stats Volume Scale Variety Velocity
- 7. 7 So we wanted to slice the Almighty monolith and move towards microservices
- 8. 8 How do you start your application migration?
- 9. 9 Are you settling for microlith? Single instance microservice, communicating over blocking protocol Resilient Scalable
- 10. 10 Why the Reactive Manifesto ?
- 11. 11 Reactive Microservices Isolate All The things Act Autonomously Do One Thing, Do It Well Own Your state, Exclusively Embrace Asynchronous Message-Passing Stay Mobile, but Addressable
- 12. 12 Microservices come in systems One microservice is no microservice Discovery Coordination Security Replication Consistency Failover Deployment Integration
- 13. 13 Event driven architecture is a design paradigm in which a software component executes in response to receiving one or more notifications. - GARTNER Event Driven Architecture To Rescue
- 14. 14 Event Driven Services Receive and react(or not) to the facts coming its way Publish new facts (as events) to the rest of the world Invert the control flow to minimize the coupling and increase autonomy Go Async, never block Always apply backpressure Fast system should never overload slow system
- 15. 15 Eventual Consistency Message buses No one wants, it’s an necessary evil AMAZING TEXT Central point of failure AMAZING TEXT Async Communication
- 16. 16 A CURE FOR CARDINAL SIN Discussing the flow of events in your organization and modelling that flow in an easy to understand way. Event Command Aggregate Input Policy External System Event Storming
- 17. 17 The Workshop Enter order details Order shipped Order placed Send order confirmation mail Order packed Command Cause events Event Flow Reaction This happens when that happens Policy Flow of events & Reactions Event EventEvent Event
- 18. 18 Domain Driven Design Aggregate Bounded Context An Account aggregate that logically groups account-related commands and events. bounded contexts group related language, meaning, and culture [bulkheads]
- 19. 19 Event Sourcing Advantages 2019 Disadvantages ➢ One single source of truth with all history ➢ Allows the memory image - durable in-memory state ➢ Avoids the object relational impedance mismatch ➢ Allows others to subscribe to state change ➢ Unfamiliar model ➢ Versioning of events ➢ Deletion of events (moral or legal reasons)
- 20. 20 Here we are JARVIS Connect your data & insight
- 21. 21 Takeaways ❑ Don’t build microliths ❑ Microservice come in/as (distributed) systems ❑ Embrace the reactive principles ❑ Embrace Event Driven Architecture ❑ Embrace Event Driven Persistence ❑ Profit!
- 22. 22 Q&A