Ad tech creative API - From Monlith to Microservice
Download as PPTX, PDF0 likes203 views
The document discusses moving an ad tech company's APIs from a monolithic application to microservices. It outlines the goals of helping advertisers spend money and publishers ensure ad quality. It also describes a pain point of delays in creative approval that took 36 hours in the old workflow. The proposed solution is to use an API to allow buyers to pre-submit creatives to eliminate delays. The document then provides best practices for splitting a monolith into microservices incrementally, building for failure, monitoring everything, and thoroughly testing changes.
Ad tech creative API - From Monlith to Microservice
- 1. Ad Tech APIs From Monoliths to Microservices
- 4. Goal - help advertisers spend $$$$
- 5. Goal - help publishers ensure ad quality
- 6. Pain Point – Delay in creative approval Old Workflow Set creative live Wait for approval Creative Rejected 36 hours
- 7. Solutions - API for buyers to pre-submit creatives Buyers submit creatives to TripleLift Buyers set creative live Creatives Rejected New Workflow API 0 delay Fixed before live
- 8. Current TripleLift Stack - Monolithic Application
- 9. Best Practices for Microservices
- 10. API gateway 1 / 5 Client API gateway Backend Service A Service C Service B Service D
- 12. Split Monolith incrementally (SRP) 2 / 5 Image Analysis SubmissionCreative Status Buyer Verification Monolithic Schema Submission Creative Status Buyer Verification Monolithic Schema 3p API Buyer Schema Image Processing
- 13. Build for failure 3 / 5 • Rate limiting • Set Request timeout • Return partial results • Return cached results
- 14. Monitor everything 4 / 5
- 16. Test everything 5 / 5 Load testing Automate testing before deployment
- 17. Q & A