Leveraging an instant messaging protocol to build a scalable cloud architecture
summary
Builds a Mendix-based cloud that replaces SOAP polling with an XMPP-driven control plane: Python bots (SleekXMPP) and Java Smack clients log in as per-process XMPP accounts, spawn Java runtimes on demand, and use presence-based discovery to wait for app servers instead of constant polling. Web-bot is ~150-line web-bot; a NIOS monitor bot is under 100 lines. File-transfer Python libraries need custom plugins, but deployment, auth and service discovery work and simplify horizontal scaling.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:53Company background
- 4:24Developer deployment challenges
- 7:14Traditional cloud overview
- 8:40First cloud version
- 11:55XMPP protocol
- 13:41New XMPP architecture
- 17:29Database decoupling
- 19:16Lightweight bot benefits
- 21:08XMPP limitations
- 22:11Architecture improvements recap
- 24:17Q&A
related talks
24mEfficient Communication Between Python Microservices using LavinMQ
26mBuilding A Python Service Using Open Source Components That Connect, Transform & Deliver Data In RT
39mAutomate the Boring Stuff with Slackbot
24mMigration from On-Prem Messaging System to The Cloud
28mStop Fighting Your Services; import lymph
44mPython in the MicroServices world
12mDisruption demands democratization: Is your iPaaS ready?
01h 14mModernizing and Optimizing Applications for the Cloud