Running an erlang based messaging system on AWS
3 likes2,650 views
Running an Erlang Based Messaging System on AWS provides an overview of MMGS, an Erlang-based mobile messaging gateway system that can be deployed on AWS. Key features of MMGS include optimized data channels for mobile messaging and email that reduce traffic by 70-80%, support for popular IM protocols and email services, and a scalable architecture with no single point of failure. The document also describes satellite systems for authentication, reporting, operations and maintenance, and real-time monitoring that provide control and visibility of the MMGS deployment. Performance benchmarks show the MMGS cluster supports over 150,000 users sending 12,600 messages per second while utilizing only 50-60% of system resources.
Ad
More Related Content
What's hot (12)
Similar to Running an erlang based messaging system on AWS (20)
Ad
More from Lahav Savir (12)
Ad
Recently uploaded (20)
Running an erlang based messaging system on AWS
- 1. Running an Erlang Based Messaging System on AWS Lahav Savir, Architect & CEO Emind systems Ltd. [email protected]
- 2. About Lahav Savir • 15++ years’ experience • Architect and CEO @ Emind Systems Emind Systems (est. 2006) • Highly professional system integrator • Dedicated Cloud Architects and DevOps teams • 24x7 SLA by DevOps Specialists • ~100 AWS customers • Partnerships with leading cloud vendors
- 3. Partnerships Amazon Advanced Consulting Partner https://aws.amazon.com/solution-providers/si/emind-systems-ltd
- 4. What is MMGS ? MMGS is an End-to-End Mobile Messaging Gateway System • Mobile Instant Messaging Gateway that enables optimized connection to various back-end community protocols • Mobile E-Mail Gateway that enables optimized communication between handset and any mail server • Control including Management, Authentication, Authorization, Billing and Reporting capabilities Mobile Messaging Gateway System (MMGS) WV / XHTML / AJAX IMAP4 / SMTP Wireless Network XMPP GTalk ISP Mail Server
- 5. MMGS Supported Features • Supported Clients – Ogo family of devices – Generic Handset Client (J2ME) – Web Client (Mobile & PC) • Instant Messaging Communities – Windows Live (MSP3.0) – ICQ, AIM – GTalk – Jabber (XMPP) – Facebook + Chat • E-mail Gateway Services – E-mail Push – IMAP, POP3, SMTP – Forward without Download (LEMONADE) – Hotmail through MSP3.0
- 6. • Optimized IM Data Channel – Secure access to IM Services – Enables data optimization between Client and MMGS – Reduces data traffic consumption by 70%-80% – Increases battery life time • Optimized E-mail Access Services – Secure access (IMAP + SSL, SMTP + SSL) – Email Push using IMAP IDLE (supports POP3, IMAP, Hotmail mailboxes) – E-mail attachments – E-mail content adaptation – Reduces data traffic consumption by 70%-80% Optimizations & Enhancements
- 7. Architecture Approach • Focus on GW features • 3 Tiers – Front-end, Router, Transport – High-Speed RPC System (eTunnel) • Security – No access to core switching & session data – Limited access to transport nodes – One way firewalls • Clustering – No single point of failure – Redundant components – In-memory replicated DB (minimal shared data) – Internal health system – Advanced failover • Load Balancing – Hash based distribution – Consistent paths – Least connections – URL load balancing
- 8. FIFO Queue (add & clear) Generic Transport node In-memory cache / Disk cache Notification Handler Throttle Community Servers Log SNMP O&M
- 9. System Architecture Windows Live Service ICQ Service AOL Service YMSG Service WV Plug-in Router MSP Plug-in ICQ Plug-in AOL Plug- in XMPP Plug-in WV Front-end CIR Front-end WBXML HTTP WVoTCP CIR Server XMPP Plug-in XMPP Front-end XMPP API Private IM Front-endRouterTransport 3rd Parties Web Front-end IM Client Web Plug-in User Interface GIS Plug-in SMTP Plug-in POP3 Plug-in IMAP Plug-in MSP AOL WV Proto. XMPP XMPP Proto. ICQ WV Proto. MSP MSP Proto. IMAP IMAP Proto. POP3 POP3 Prot. SMTP SMTP Proto. BOSH Mail Service Contact s XML/ HTTP Contacts Plugin Contact Service YMSG WV Proto. Profile Svc. Plug-in Cache Video Relay Plug-in Facebo ok FB Proto. Twitter Twitter Proto. Facebook Twitter Facebook Twitter IMAP Front-end IMAP SMTP Front-end SMTP SMTP Plug-inIMAP Plug-in Gtalk Service MMGS Available Componenet MMGS Future Component Legend 3rd Party System Content Convertor Reporting Authentication Management Monitoring Logging Satellite Systems
- 10. No single point of failure TransportsRoutersFront-ends Firewalls Firewalls Load Balancers Load Balancers eTunnel eTunnel
- 11. AWS Deployment
- 12. Performance Benchmark Measures Setup • Basic cluster built of 11 servers – m1.medium and m1.large instances Instant Messaging performance • 150,000 Connected users • 12,600 Messages per second • 45,000,000 Messages an hour System resources • 50%-60% system utilization
- 13. What Made the Difference? • High speed socket based RPC – eTunnel • Resource pools (eBalancer) • Minimal data sharing / Distributing the data • Hash based distribution between layers makes consistent path through layers • Health checks Integration with load balancer • Reduce destructive DB operations, especially on replicated tables • Internal health system integrated with topology manager • Extensive SNMP MIBs • Throttling – Control concurrency
- 14. Flexibility for business models • Reporting sys. integrated with authentication & authorization • Supports any business model • Daily / monthly pay • Per use • Per Message • Per data size • Per Service
- 15. Satellite Systems • Authentication – Authentication, Authorization & Control over the service delivered • Reporting – Nearly real-time usage reports aggregated to an hour cycle • Operation and Maintanance – Stop / Start, Watch real-time alarms, configuration – Traceability and troubleshooting – Software update - hot patch distribution and loading – Central log console – Central graphing system • Real Time Monitoring – Infrastructure, OS and App
- 16. Authentication System The Authentication System is a satellite system providing full Authentication, Authorization & Control over the service delivered by MMGS • Source IP based access • Device based access (enable / disable a device) • Service based access (enable / disable a service for a device) – MSN, ICQ, AIM, Jabber, Gtalk, IMAP, POP3, Hotmail, Facebook • Feature based access (enable / disable a specific feature for a service) – Nudge, Tiles, E-mail Push, E-mail Attachments • User friendly, secure and easy to use Web GUI • Feature Rich and secure XML over HTTP API to enable operators to manage the service delivered to their customer
- 18. Reporting System The reporting system provides a nearly real-time usage reports aggregated to an hour cycle • Operator based reports, summary of activities for an operator • Service based reports, summary of activities for a service • Device based reports, summary of activities for device • Secure Web Based User Interface • Secure XML over HTTP rich API to support Operators billing systems
- 20. Operation & Maintenance The Operation & Maintenance provides full control over the MMGS servers • Complete cluster management – Stop / Start, Watch real-time alarms, configuration – Traceability - trace system control over, stop / start device based trace, configure logging level – Troubleshooting – configuration mismatch, version mismatch, topology mismatch – Software update - hot patch distribution and loading • Central Log console • Central graphing system provides an in depth view into the systems counters (real-time and historical)
- 21. Operation & Management UI
- 22. Real-Time Monitoring Real-Time Monitoring system provides an in depth monitoring of the system’s resources and performance via Web Based UI • Service operator view • Customer view • Service counters thresholds (QoS, success rates, message latency) • Application Counters threshold (application concurrency) • Application Services (Protocols) • Operating System threshold (CPU, Mem, Disks, Net) • Hardware Resources
- 23. Graph system UI
- 24. Summary • Mobile Aware • Optimized data channels • Longer battery life • Protocol Conversion • Content Adaptation • Authentication & Authorization • Service, Device and Feature levels • Billing • Operator, Device and Service levels • Management & Control • User friendly operation • In depth system visibility • Redundancy & Scalability • Active/active (no single point of failure) • Linear scalability • Proven high performance • Security • One way firewall • 3 Physical layers