Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Liz McMillan, Elizabeth White, Pat Romanski, Cloud Best Practices Network, Lori MacVittie

Related Topics: Mobile IoT, @MicroservicesE Blog, Agile Computing, @CloudExpo Blog

Mobile IoT: Article

Democratizing Enterprise Mobility

Introducing the Enterprise Mobile Platform as a Service

For the last two years, enterprise mobility has had a high place on the technology agenda of most companies. However, the mobile enterprise remains a highly complex and expensive endeavor that can only be afforded by a small group of organizations. Even more importantly, the enterprise mobility stacks are technologically archaic compared to the equivalent consumer market technology which is causing companies to start embracing open, consumer-based technologies as part of the enterprise mobile applications.

If you agree that connected devices are becoming a predominant force in the enterprise, then you can also agree that the industry is in desperate need for technologies that provide simple, open and yet robust mechanisms to develop enterprise applications that can run on these devices.

Mobile Enterprise Is About the Back End not the Front End
Looking at the current enterprise mobility technology ecosystem, we can quickly notice a heavy emphasis on development tools and technologies that allow developers to build applications that can run on a diverse number of devices. While that type of technologies is certainly welcome, this is far from being a problem in the enterprise. The market is full of mobile frontend technologies that support multi-device applications which are very viable solutions in an enterprise environment. PhoneGap, AppAccelerator's Titanium, Xamarin's Monotouch and Mono for Android, Sencha Touch are just some of the examples of technologies that enable a cross-device experience and, what is more important, provide a far superior experience than the equivalent SAP, IBM or Antenna software technologies.

Based on the rapid evolution of the mobile technology landscape, enterprise developers have a very broad spectrum of technology options when it comes to implementing mobile client frontend interfaces. The challenge, however, remains in the backend infrastructure. Aspects such as security, identity management, storage, messaging, media exchange, and content management are among many some of the most important backend capabilities that are required by most enterprise mobile applications. Enabling these and many other backend features represent, by enlarge, the most important challenge in the current spectrum of enterprise mobile applications.

When designing an enterprise mobility strategy, the emphasis should not be on the client development technologies and tools and, instead, it should be focused on the backend services and management experience to enable enterprise-ready mobile applications.

Anatomy of an Enterprise Mobile Platform in 2012
Looking at the current enterprise mobility market, we can find a group of "platforms" that can serve as the foundation of an enterprise mobile infrastructure. Sadly, all these technologies look incredibly similar and mysteriously resemble the models pioneered by Research in Motion a few years ago. Without exception, the current generation of enterprise mobility platforms provides a series of components that compose the complete mobile application lifecycle from development to operational management. The following figure depicts the fundamental elements of a mobile enterprise platform in the current market.

As illustrated in the above figure, the DNA of a traditional enterprise mobile platform is based on the following components.

  • Cross Platform Mobile Application Development Tool: This component of an enterprise mobility platform enables a developer to implement mobile applications that can be deployed to multiple devices.
  • Mobile Application Server: Traditional enterprise mobility platforms include a server side infrastructure that serves as the fundamental gateway to abstract the interaction between mobile applications and the datacenter infrastructure.
  • Mobile Line of Business Adapters: Some enterprise mobility platforms include out of the box connectors to traditional line of business systems such as ERP or CRM applications. These components intend to streamline the integration of these platforms into enterprise mobile applications
  • Mobile Application Manager: Every enterprise mobility platform provides a component to manage and monitor the different applications running in the mobile application server.
  • Mobile Device Manager: Device management has been a traditional component of traditional enterprise mobility platforms since the early years. This component is typically responsible for managing the mobile devices running specific enterprise applications.

The components listed above represent the foundation of the current ecosystem of enterprise mobility platforms. Some of the characteristics of these components combined with the constraints of an on-premise delivery model introduce a series of challenges for organizations when embracing these platforms as the core of an enterprise mobility infrastructure.

The Challenges
The technical complexity and expensive delivery model of traditional enterprise mobile platforms combined with the novel and rapid evolving nature of mobile technologies makes enterprise mobility a really challenging experience for most organizations. Without getting into the specifics of any particular technology, we can refer to a number of challenges that are common across most enterprise mobile platforms.

  • High learning curve: By not relying on popular and open technologies, traditional enterprise mobility platforms require that most companies train their developers and IT professionals in the usage of the proprietary development tools and frameworks required by the platform.
  • On-premise infrastructure: Most enterprise mobility platforms require expensive on-premise infrastructures in order to host and manage the applications developed on the platform.
  • Lack of developer community: The closed nature of traditional enterprise mobile platforms has impeded the growth of developer communities around these technologies. This fact has reflected in a lack of tools, frameworks and even accessible talent around those platforms which directly translates into high implementation and maintenance costs for most companies.
  • Technology debt: The rapid evolution of mobile development technologies has made it impossible for most enterprise mobile platforms to keep up with the latest mobile trends. To cite an example, it took nearly a year after HTML5 became one of the most popular mechanisms for the implementation of mobile application before any of the major enterprise mobility platforms announced the native support for HTML5 applications.
  • Professional services: The complexity and lack of developer communities for most enterprise mobility frequently platforms requires the use of professional services when implementing solutions on these platforms.

The aforementioned challenges are just some the roadblocks encountered by organizations when implementing enterprise mobility solutions based on traditional platforms. Given the growing importance of connected devices, the industry is in a desperate need of simpler, open, rapidly growing platforms that can help to democratize the enterprise mobility ecosystem.

The Time for an Enterprise Mobile Platform as a Service
As mentioned in the previous section, the current technology models for enterprise mobility has proven to be highly inefficient to address the challenges in this rapidly growing space. As an alternative, we need new enterprise mobile technologies that embrace modern computing paradigms and a simple delivery model that enables organizations to easily embrace enterprise mobility initiatives. In a nutshell, here are some of the primary elements we believe a modern enterprise mobility platform should provide:

  • Freedom of tools and frameworks: A modern enterprise mobility platform should enable developers to use their favorite development tools and frameworks when it comes to implementing mobile applications.
  • Open and simple to use backend capabilities: Forget the frontend capabilities, a modern enterprise mobile platform should enable open, service-enabled and simple to use backend features that allow developers to build enterprise-ready mobile applications.
  • Cloud based delivery model: The on-premise model in enterprise mobile platforms have proven to be highly inefficient and cost prohibitive for most organizations. As an alternative, a modern enterprise mobility platform should leverage cloud computing as the fundamental mechanism to enable the backend and management capabilities of the platform.
  • Managed mobile web hosting and provisioning capabilities: As HTML5 and mobile web techniques become increasingly important in enterprise mobile applications, the ability of hosting, provisioning and managing mobile web applications should be a key component of the next generation enterprise mobile platforms.
  • Elastic and scalable computing model: While is true that user behavior is more predictable in enterprise mobile applications compared to consumer applications, the sole nature of mobile applications demands an elastically scalable hosting model in which infrastructure can be dynamically allocated based on user demands.
  • Open, Open, Open: Finally, a modern enterprise mobility platform must be open enough to nurture a developer community around it and to keep up with the rapid evolution of mobile technologies.

An almost axiomatic truth in software development is the fact that most software platforms are just a realignment of well-established computing paradigms. In that sense, we should look for well-established software models that can enable the next generation of enterprise mobile platforms. We can quickly find the answer in one of the fastest growing technology movements of the last few years: Platform as a Service (PaaS)

A Platform as a Service for Enterprise Mobile Applications
At a high level, an enterprise mobile platform as a service is a cloud platform that provides elements of the enterprise mobile application development lifecycle as multi-tenant services. Specifically, an enterprise mobile application provides enterprise-ready backend capabilities as cloud services and it facilitates the hosting, provisioning and management of mobile applications that use those services. As other technology movements, an enterprise mobile platform as a service can be seen as a combination of existing technology movements such as mobile Backend as a Service (BaaS), mobile enterprise application stores, and a few other emerging areas in mobile technologies.

Expanding beyond the conceptual level, we think of the first generation of enterprise mobile PaaS as three fundamental components: a series of enterprise cloud APIs, a mobile enterprise application store and an environment to deploy, provision and manage enterprise mobile applications. The following figure illustrates this concept.

One of the most important aspects of an enterprise mobile platform is its application centric nature. Different from traditional platform as a service model, the application is the center of the enterprise mobile PaaS model and resources and services are provisioned and managed within the context of an application. The following figure illustrates that concept:

In addition to its numerous advantages from the technology standpoint, an enterprise mobile PaaS embraces the commercial SaaS model in which customers pay a subscription fee based on the usage of the platform. These models allow organizations to start relatively small and scale organically their enterprise mobility initiatives. Also, the cloud delivery model of the enterprise mobile cloud APIs allows organizations to immediately take advantage of new services as soon as they become available in the platform.

Even though it is not a key characteristic of the model, it is very important to highlight the tool agnostic nature of Enterprise Mobile Platform as a Service. Different from traditional enterprise mobile platforms in which development tools are at the center of the stack, an Enterprise Mobile PaaS focuses on the backend, hosting, provisioning and management aspects of enterprise mobile applications and delivers those in a model that can be used from any development tool or framework. To make the experience even simpler, Enterprise Mobile PaaS typically include SDKs for some of the major mobile platforms.

The Inevitability of the Enterprise Mobile PaaS
Based on some of the arguments expressed in the previous section, we can easily conclude that Enterprise Mobile PaaS are an inevitable evolution of the existing unsustainable enterprise mobility models. At a high level, Enterprise Mobile PaaS offers significant advantages over traditional models:

  • Tool agnostic: Different from traditional enterprise mobile platforms, Enterprise Mobile PaaS allow organizations to build enterprise mobile applications using their favorite tools and frameworks.
  • No on-premise setup: Enterprise Mobile PaaS are delivered as a cloud based solution that requires no on-premise infrastructure.
  • No learning curve: The open nature of Enterprise Mobile PaaS makes it accessible to any developer with basic knowledge of mobile platforms.
  • Continuous upgrades: Like any good cloud citizen, Enterprise Mobile PaaS make the continuous release of new and upgraded features a key element of the platform.
  • Elastically scalable: An Enterprise Mobile PaaS allows organizations to scale organically based on the user demand of their enterprise mobile applications.
  • Cost: The pay as you go model of Enterprise Mobile PaaS allows organizations to quickly ramp up and organically scale enterprise mobility initiatives without incurring major costs.

Finally and more importantly, the Enterprise Mobile PaaS represents the only model in which organizations can practically keep up with the fast evolving pace of the mobile technology world without sacrificing the policies of enterprise applications.

Conclusion
Enterprise Mobile Platform as a Service represents the natural evolution of enterprise mobility platforms. Traditional enterprise mobility platforms have proven to be highly inefficient, hard to scale, slow to evolve models that impose a high technologically and financial cost to most organizations. An Enterprise Mobile PaaS combines emerging technology models such as mobile Backend as a Service with creative application delivery models like application stores to simplify and democratize enterprise mobility.

More Stories By Jesus Rodriguez

Jesus Rodriguez is a co-founder and CEO of KidoZen, an enterprise mobile-first platform as a service redefining the future of enterprise mobile solutions. He is also the co-founder to Tellago, an award-winning professional services firm focused on big enterprise software trends. Under his leadership, KidoZen and Tellago have been recognized as an innovator in the areas of enterprise software and solutions achieving important awards like the Inc 500, Stevie Awards’ American and International Business Awards.

A software scientist by background, Jesus is an internationally recognized speaker and author with contributions that include hundreds of articles and sessions at industry conferences. He serves as an advisor to several software companies such as Microsoft and Oracle, sits at the board of different technology companies. Jesus is a prolific blogger on all subjects related to software technology and entrepreneurship. You can gain valuable insight on business and software technology through his blogs at http://jrodthoughts.com and http://weblogs.asp.net/gsusx .

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Containers and Docker are all the rage these days. In fact, containers — with Docker as the leading container implementation — have changed how we deploy systems, especially those comprised of microservices. Despite all the buzz, however, Docker and other containers are still relatively new and not yet mainstream. That being said, even early Docker adopters need a good monitoring tool, so last month we added Docker monitoring to SPM. We built it on top of spm-agent – the extensible framework f...
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
SYS-CON Events announced today that the "Second Containers & Microservices Conference" will take place November 3-5, 2015, at the Santa Clara Convention Center, Santa Clara, CA, and the “Third Containers & Microservices Conference” will take place June 7-9, 2016, at Javits Center in New York City. Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities.
The causality question behind Conway’s Law is less about how changing software organizations can lead to better software, but rather how companies can best leverage changing technology in order to transform their organizations. Hints at how to answer this question surprisingly come from the world of devops – surprising because the focus of devops is ostensibly on building and deploying better software more quickly. Be that as it may, there’s no question that technology change is a primary fac...