Introducing the Mobile-First Middleware
•Download as PPTX, PDF•
0 likes•679 views
This session introduces the concept of a mobile-first middlewar eand compares it with traditional traditional integration models in the enterprise
Report
Share
Introducing the Mobile-First Middleware
- 1. Introducing the Enterprise Mobile-First Middleware Jesus Rodriguez CEO, KidoZen
- 2. About Me • Hackerpreneur • Co-Founder KidoZen, Inc • Advisor to software companies (Microsoft, Oracle….) • Board member • Speaker, Author • Investor • http://jrodthoughts.com • http://weblogs.asp.net/gsusx • https://twitter.com/jrdothoughts • http://kidozen.com
- 4. A platform that powers the backend of the post-web enterprise
- 5. KIDOZEN A MOBILE APP PLATFORM FORTHE ENTERPRISE Enables Backend, Management and Lifecycle Capabilities Integration with On- Premise and SaaS Systems Access to Storage, Logging, Identity Management, SMS, Push Notification, etc. Public, Hybrid, Private Cloud Analytics, Data Virtualization, Data Visualization, etc. KidoZen Integration : Enterprise mBaaS Data Access: Mobile Data Virtualization Privacy: Mobile Data Management Distribution: Enterprise Mobile App Center Analytics: App Performance Monitoring Visualization: Mobile Data Visualization
- 8. 25+ Partners in 50 Countries Canada United States AustraliaSouth Africa Taiwan Philippines Argentin a Egypt Kuwait Saudi Arabia UAE Mexico India Malaysia Singapore Indonesia China Europe Austria Belgium Czech Republic France Germany Hungary Ireland Italy Luxembourg Netherlands Norway Portugal Slovakia Spain Sweden Switzerland United Kingdom Russia Geographic Coverage
- 9. Agenda • The need for a mobile-first middleware • The DNA of a mobile-first middleware • Capabilities
- 10. Enterprise Mobile Needs a New Middleware
- 12. Why????
- 13. Every relevant enterprise information worker trend produces a new type of middleware Historic Fact #1
- 14. The Evolution of Enterprise Middleware? B2B: EAI Relational Databases: ETL Software Oriented Architecture: ESB Cloud Computing: iPaaS Enterprise Mobility: ???
- 15. We always try to apply previous- generation middleware to new-generation problems Historic Fact #2
- 18. What makes mobile integration different?
- 19. One of the Endpoints is Always Mobile
- 20. App-Driven Integration:The app is part of the middleware
- 21. A Few Other Unique Characteristics • OfflineCommunications • Heterogeneous devices • Diverse networks • Real time data access • Small data payloads
- 22. We Haven’t HadThis Problem Before…
- 24. Homegrown APIs Enterprise Data Source Data SourceAPI Corp Data Center
- 25. Mobile Data Access via Homegrown APIs Pros: • Leverage existing skillsets and assets • Enabler for responsive-design models Cons: • Non-mobile-first infrastructure • Requires constant building of backend infrastructure • Hard to scale (development) and maintain • Challenging to manage & operate • No aggregation or orchestration models • Lack of standards: Different APIs for different data sources
- 26. MEAPs Enterprise Data Source Corp Data Center Enterprise Data Connector MEAP Server
- 27. MEAPs
- 28. Mobile Data Access via MEAPs Pros: • Default enterprise systems connectors Cons: • Heavy and proprietary infrastructure • Expensive • Require professional services & training • Challenging to manage & operate • Lack of standards: Different connectors for different data sources
- 29. We need a better model….
- 30. Introducing the enterprise mobile-first middleware…
- 31. A mobile-first middleware provides integration between mobile applications and enterprise systems Definition
- 32. Enterprise mobile backend as a service (mBaaS) platforms are the closest approximation to a mobile-first middleware and a foundational component of it
- 33. Enterprise mBaaS Enterprise Data Source Corp Data Center Enterprise Data Connector Enterprise Data Agent Enterprise SystemAPI Enterprise mBaaS Platform
- 34. Mobile Data Access via Enterprise mBaaS Pros: • Default enterprise system connectors • Private, hybrid and public cloud friendly infrastructure • Mobile platform agnostic • Lean and scalable models • Productized road map Cons: • Lack of standards: Different connectors for different data sources • Back-end system knowledge required
- 35. The DNA of a mobile-first middleware
- 36. Elements of a Mobile-First Middleware Mobile-first Middleware Mobile APIs Mobile App Distribution Mobile App Analytics Mobile Integration Pipeline Components
- 38. Types of Enterprise Mobile APIs
- 39. Enterprise Mobile APIs •Enable service access to mobile-first capabilities •Examples: • Push notifications • SMS • Voice • Image recognition • Location •Technological implementation: mBaaS
- 40. Mobile Infrastructure APIs • Provide compute, storage and messaging capabilities to mobile applications • Examples: • Storage • Queuing • Publish-Subscribe • Logging • Configuration • Technological implementation: mBaaS
- 41. Mobile Enterprise APIs • Provide integration between mobile apps and enterprise systems • Examples: • SAP • Siebel • Oracle DB • MS Dynamics • Epic • Technological implementation: mBaaS
- 42. Mobile Business APIs • Provide business logic functionalities that can be reused across different mobile apps • Examples: • Order placement • Pricing calculation • Inventory availability • Technological implementation: Server side code
- 43. Mobile Data Access APIs • Provide querying capabilities over enterprise data sources • Example: • Odata APIs • Technological implementation: mobile data virtualization
- 44. Mobile Integration Pipeline Components…
- 45. Mobile Integration Pipeline Components •Routing •Caching •Transformation •Reliable Messaging •Encoding •….
- 47. Mobile App Store • Enables distribution of native, hybrid and mobile-web applications • Integrates with existing MDM- EMM providers • Enables management versioning, auto-update capabilities
- 49. Mobile App Analytics • Provides telemetry and analytics about the performance of the enterprise mobile solutions: • App performance • API performance • Data performance
- 50. Other Interesting Capabilities • In-app analytics • APITesting • App auditing • Mobile continuous integration
- 51. Benefits of a Mobile-First Middleware • Abstracts enterprise system integration from mobile applications • Provides consistent system and data access from mobile applications • Enables distribution capabilities for mobile applications • Analytics about the performance of applications,APIs and data
- 53. The emergence of the IOT-first middleware…
- 54. IOT-First Middleware • Super-set of the mobile-first middleware • Enabling the integration between smart devices and enterprise systems • Relevant trends • Device management • Event driven integration • Real time analytics and data processing • Developer SDKs IOT-First Middleware `Event Integration Services Device Management Services RealTime IOT Performance Monitoring IOT SDKs
- 55. Summary • Enterprise mobile solutions need a new type of middleware • mBaaS is a key foundational piece to a mobile middleware platform • The main components of a mobile middleware are: • API hub • App Store • Mobile Analytics • Integration pipeline components