Mobile First Middleware

56
Introducing the Enterprise Mobile-First Middleware Jesus Rodriguez CEO, KidoZen

Transcript of Mobile First Middleware

Introducing the Enterprise Mobile-First Middleware

Jesus Rodriguez CEO, KidoZen

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

About KidoZen

A platform that powers the backend of the post-web

enterprise

KIDOZEN A MOBILE APP PLATFORM FOR THE 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

Our Customers

Our Customers

25+ Partners in 50 Countries

Canada

United States

AustraliaSouth Africa

Taiwan

Philippines

Argentin

a

Egypt

Kuwait

Saudi Arabia

UAE

MexicoIndia

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

Agenda

• The need for a mobile-first middleware• The DNA of a mobile-first middleware• Capabilities

Enterprise Mobile Needs a New Middleware

Another #%#$!^^%Middleware??????????

Why????

Every relevant enterprise information worker trend produces a new type of

middleware

Historic Fact #1

The Evolution of Enterprise Middleware?

B2B: EAI

Relational Databases: ETL

Software Oriented Architecture: ESB

Cloud Computing: iPaaS

Enterprise Mobility: ???

We always try to apply previous-generation middleware to new-generation problems

Historic Fact #2

And It Never Works….

Middleware Requirements Evolve

What makes mobile integration different?

One of the Endpoints is Always Mobile

App-Driven Integration: The app is part of the middleware

A Few Other Unique Characteristics

• Offline Communications

• Heterogeneous devices

• Diverse networks

• Real time data access

• Small data payloads

We Haven’t Had This Problem Before…

Achieving Mobile Integration Today…

Homegrown APIs

Enterprise Data Source

Data Source API

Corp Data Center

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

MEAPs

Enterprise Data Source

Corp Data Center

Enterprise Data Connector

MEAP Server

MEAPs

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

We need a better model….

Introducing the enterprise mobile-first middleware…

A mobile-first middleware provides integration between mobile

applications and enterprise systems

Definition

Enterprise mobile backend as a service (mBaaS) platforms are the closest

approximation to a mobile-first middleware and a foundational

component of it

Enterprise mBaaS

Enterprise Data Source

Corp Data Center

Enterprise Data Connector

Enterprise Data Agent

Enterprise System API

Enterprise mBaaS Platform

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

The DNA of a mobile-first middleware

Elements of a Mobile-First Middleware

Mobile-first Middleware

Mobile APIs

Mobile App Distribution

Mobile App Analytics

Mobile Integration

Pipeline Components

Enterprise Mobile APIs

Types of Enterprise Mobile APIs

Enterprise Mobile APIs

•Enable service access to mobile-first capabilities

•Examples:• Push notifications

• SMS

• Voice

• Image recognition

• Location

•Technological implementation: mBaaS

Mobile Infrastructure APIs

• Provide compute, storage and messaging capabilities to mobile applications

• Examples:• Storage

• Queuing

• Publish-Subscribe

• Logging

• Configuration

• Technological implementation: mBaaS

Mobile Enterprise APIs

• Provide integration between mobile apps and enterprise systems

• Examples:• SAP

• Siebel

• Oracle DB

• MS Dynamics

• Epic

• Technological implementation: mBaaS

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

Mobile Data Access APIs

• Provide querying capabilities over enterprise data sources

• Example:• Odata APIs

• Technological implementation: mobile data virtualization

Mobile Integration Pipeline Components…

Mobile Integration Pipeline Components

•Routing

•Caching

•Transformation

•Reliable Messaging

•Encoding

•….

Mobile App Distribution

Mobile App Store

• Enables distribution of native, hybrid and mobile-web applications

• Integrates with existing MDM-EMM providers

• Enables management versioning, auto-update capabilities

Mobile App Analytics

Mobile App Analytics

• Provides telemetry and analytics about the performance of the enterprise mobile solutions:• App performance

• API performance

• Data performance

Other Interesting Capabilities

• In-app analytics

• API Testing

• App auditing

• Mobile continuous integration

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

Thinking Beyond Mobile

The emergence of the IOT-first middleware…

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

Real Time IOT

Performance Monitoring

IOT SDKs

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

[email protected]

http://jrodthoughts.comhttp://twitter.com/#!/jrodthoughts

http://www.kidozen.com