Downloaded 12 times
Uploaded byJesus Rodriguez
Introducing the Mobile-First Middleware
The document introduces Kidozen, a mobile-first middleware platform designed to enhance enterprise mobile applications by providing backend services, integration capabilities, and analytics. It outlines the evolution and necessity of mobile-specific middleware, emphasizing limitations of existing solutions and advocating for a mobile backend as a service (MBAAS) as a foundational component. Key features include support for diverse devices, real-time data access, and access to enterprise data systems, ultimately defining the mobile integration landscape.
More Related Content
![Building A System That Never Stops [FutureStack16 NYC]](https://cdn.slidesharecdn.com/ss_thumbnails/buildingasystemthatneverstopsfs16nycv2-160815233101-thumbnail.jpg?width=640&height=640&fit=bounds)
![The Selfish Stack [FutureStack16 NYC]](https://cdn.slidesharecdn.com/ss_thumbnails/selfishstackpresentationfinal1-160815212335-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Introducing the Mobile-First Middleware
More from Jesus Rodriguez
Introducing the Mobile-First Middleware
- 1. Introducing the Enterprise Mobile-FirstMiddleware 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
- 3.
- 4. A platform thatpowers the backend of the post-web enterprise
- 5. KIDOZEN A MOBILEAPP 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
- 6.
- 7.
- 8. 25+ Partners in50 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 needfor a mobile-first middleware • The DNA of a mobile-first middleware • Capabilities
- 10. Enterprise Mobile Needs aNew Middleware
- 11.
- 12.
- 13. Every relevant enterpriseinformation worker trend produces a new type of middleware Historic Fact #1
- 14. The Evolution ofEnterprise Middleware? B2B: EAI Relational Databases: ETL Software Oriented Architecture: ESB Cloud Computing: iPaaS Enterprise Mobility: ???
- 15. We always tryto apply previous- generation middleware to new-generation problems Historic Fact #2
- 16.
- 17.
- 18. What makes mobileintegration different?
- 19. One of theEndpoints is Always Mobile
- 20. App-Driven Integration:The appis part of the middleware
- 21. A Few OtherUnique Characteristics • OfflineCommunications • Heterogeneous devices • Diverse networks • Real time data access • Small data payloads
- 22. We Haven’t HadThisProblem Before…
- 23.
- 24. Homegrown APIs Enterprise DataSource Data SourceAPI Corp Data Center
- 25. Mobile Data Accessvia 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 CorpData Center Enterprise Data Connector MEAP Server
- 27.
- 28. Mobile Data Accessvia 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 abetter model….
- 30. Introducing the enterprise mobile-firstmiddleware…
- 31. A mobile-first middlewareprovides integration between mobile applications and enterprise systems Definition
- 32. Enterprise mobile backendas a service (mBaaS) platforms are the closest approximation to a mobile-first middleware and a foundational component of it
- 33. Enterprise mBaaS Enterprise DataSource Corp Data Center Enterprise Data Connector Enterprise Data Agent Enterprise SystemAPI Enterprise mBaaS Platform
- 34. Mobile Data Accessvia 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 ofa mobile-first middleware
- 36. Elements of aMobile-First Middleware Mobile-first Middleware Mobile APIs Mobile App Distribution Mobile App Analytics Mobile Integration Pipeline Components
- 37.
- 38. Types of EnterpriseMobile APIs
- 39. Enterprise Mobile APIs •Enableservice 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 AccessAPIs • Provide querying capabilities over enterprise data sources • Example: • Odata APIs • Technological implementation: mobile data virtualization
- 44. Mobile Integration PipelineComponents…
- 45. Mobile Integration PipelineComponents •Routing •Caching •Transformation •Reliable Messaging •Encoding •….
- 46.
- 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
- 48.
- 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 aMobile-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
- 52.
- 53. The emergence ofthe IOT-first middleware…
- 54. IOT-First Middleware • Super-setof 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 mobilesolutions 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
- 56.