Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Microservices Expo, Java IoT, Mobile IoT, Machine Learning , Agile Computing

Microservices Expo: Article

Service Enablement of Enterprise Data through Mobile Devices

Leveraging Service Architecture in extending enterprise applications to mobile devices

It's well known that in recent times that consumption of data or a service through mobile applications is increasing exponentially due to the increase in the mobile customer base and the increase in the number of mobile devices connected to various systems disproportionately(1). That means in most of the cases, consumers of mobile devices are increasing more than traditional desktop browser based service model of consumption. These end users use a large number of different types of devices starting from standalone desktops, laptops, and tablets to mobile devices. It is expected that applications keep up the data or service while they move from one system to other, for example, if someone starts reading a book from Amazon Kindle and continues to read the same book from an iPad. So the continuity of the service or data is achieved and this is possible only when all the systems are connected with some sort of loose coupled integration. While it is possible for standalone systems to make it easier to get data or service connected, mobile applications also have to be ensured that the same data or service is provided and integrated. In this article, we are discussing the various ways of service-enabling the enterprise applications data in the mobile devices.

Before we discuss about service enablement (2, 3) of enterprise data through mobile devices, the following factors are considered when mobile enabling the enterprise data applications:

  1. Desktop services are accessed through http, while mobile devices predominantly follow WAP (Wireless application protocol).
  2. There are several device vendors in the market each with their own proprietary operating systems
  3. There is plethora of device models with wide range of form factor and screen sizes, hence GUI design to fit to all models is arduous task.
  4. Data security is big challenge, client side security validations are difficult to achieve on memory constraint mobile devices
  5. There would be significant increase in load on the servers.

Technical parameters considered for Service Enablement of Enterprise Data through Mobile devices
The following options are considered when building mobile-enabled services (4), each with its pros and cons.

  • Accessing the enterprise services through mobile browsers
  • Using mobile client by native application or through a framework

The complete application can be developed on the server side and mobile browsers can be used to access selected services. Which services are the best fit for mobile access depends on how critical the data being exchanged is. Unless strict security measures are enforced, sensitive data cannot be exchanged over the mobile network. The data needs to be exchanged through secured network (SSL) with access to authorized users only. This needs seamless integration with identity management systems.

Data such as the product details of inventory, promotional activities, special offers, etc., can be shared across mobile network as this is not security sensitive data. All financial transactions, personal data of users should be transmitted under careful security measures.

Lengthy operations like filling order or feeding sensitive data are not good candidates for operating with mobile browsers as they need a live connection to the server. In all such critical scenarios, mobile clients are best suited as they can operate in offline mode as well.

The JSF technology can be used to develop a presentation tier as it has protocol flexibility. The GUI developed (Component tree) for desktop access can be re-used to render on wireless mobile devices provided a WML (wireless Markup Language) render kit is available. There are some third-party render kits available such as myfaces that can be plugged-in. GUI development with JSF is very fast as most of the standard IDEs (RAD, MyEclipse, NetBeans, JBuilder, JDeveloper, JBoss Developer Wtudio ) support JSF drag & drop (WYSIWYG ) editors.

But there are some serious challenges while developing browser-based applications. The high latency and low bandwidth of networks in mobile environments affects application responsiveness for mobile users. Screens refresh slowly, diminishing the mobile user experience. Hence mobile application development should use Partial Page Rendering (PPR) to display only dynamically changing data without going for complete page reloading. Browsers that do not support AJAX (Asynchronous JavaScript and XML) use full page rendering instead of PPR, seriously choking the network bandwidth. The other important parameter is to take into account form factor and widely differing screen sizes while developing GUI for accessing through mobile browsers. While JSF stack provides a good toolkit for the faster development of GUI, one common opinion is that JSF components are heavy thus leading to slower loading of a requested page.

The other option is to access enterprise services through mobile clients. Mobile clients are small client-side applications hosted on mobile devices. But what is the right technology to develop mobile clients and how they communicate with the server side enterprise applications? As discussed, there are many vendors in the mobile market, each with their own operating systems and SDK. Developing mobile clients for every vendor is not only tedious but not recommended from a cost perspective. There are few mobile frameworks that  abstract the common functionality of different mobile operating systems, some of them are open source and others are proprietary. These mobile frameworks mostly operate using simple HTML, JavaScript, JQuery, JQuerymobile to develop mobile clients and support the SDK of all leading mobile vendors in the market.

Except for some device specific functionality, mobile frameworks can be used to achieve standard enterprise functionality. This promotes "Develop once and deploy on any device" concept of mobile application development.

But how will these mobile clients access enterprise data? Some of the selected services can be exposed as web services, which can be consumed by mobile clients. There are two options, one is SOAP based web services and the other is RESTful web services.

SOAP-based services need client-side stubs to consume services by a mobile client. The client-side stubs take the responsibility of de-marshalling and marshalling data while consuming the service and sending requests to the server. But this needs a SOAP engine to be installed on mobile devices. SOAP-based web services often exchange data using XML, which will have header and footer overheads. There are many tools available to generate WSDL given the details of Java classes whose methods are exposed as web methods. The client application can use WSDL to generate client-side stubs to consume web methods exposed by a server application.

On the other hand RESTful web services are simple and easy to develop. They exchange the data in the JSON format, which can be encoded on the server side while transmitting over the network. The mobile client can use JQuery calls to decode and manipulate the JSON object. The JSON objects are simple and lightweight and hence easy to transmit over the network. But RESTful web services are not meant for stateful transactions.

While mobile clients facilitate an online or offline mode of communication with a server-side application, mobile browsers only work with the online mode.

  • Decide which business processes available for mobility
  • Redefine needed business processes offline/online mode
  • Decide which functionalities should be available on mobile
  • Design a GUI for mobile devices
  • Service enables the functionalities for mobile
  • Create a framework like JSF enabled for java apps, azure developed for Microsoft etc
  • Communication middleware and processing

Service Enabling Framework for Enterprise Applications
The following framework provides the service enablement (5) of enterprise applications.

The simplest option is compatibility of mobile device browser for enterprise applications. However, with the increase of demand for mobile application installations on devices, integration takes significance and it can at web server layer or Application layer or at database layer as shown above. Layered approach of the applications is used for achieving the service enablement.

While the above describes about service enablement of enterprise apps for mobile applications, the following diagram describes various ways of application integration with mobile apps which will make mobile enabled applications.

Integration using APIs:
Mobile applications are driven by open APIs to expose the functionality and most are REST-based APIs, stateless APIs running over HTTP. The significance of Open APIs for integration comes with lot of opportunities in terms of creating visibility of the products for business. For example, The Facebook Auth API is being used by several applications for access of applications.

Conclusion
The mobile enabling of enterprise applications and data is significant with the number of mobile devices increasing every day. Web browsers and mobile client installations are increasing their usage of enterprise data. The integration of web apps to enterprise applications is significant in terms of WAP integration, wireless extended integration, peer-to-peer integration, and web-based integration, and API integrations are gaining significantly. However, going forward, with the advancement of technology, new ways of accessing enterprise data is considered.

References:

  1. http://mobithinking.com/mobile-marketing-tools/latest-mobile-stats
  2. http://clouddataanalytics.ulitzer.com/node/2112881
  3. http://sreekusumanchi.sys-con.com/node/837728
  4. http://www.ibm.com/developerworks/library/it-novcc00/
  5. http://msdn.microsoft.com/en-us/library/bb972953.aspx

More Stories By GVB Subrahmanyam

GVB Subrahmanyam an Application Developer, Lead, Project Manager, Development Manager and Delivery Manager in a wide variety of business applications as part of an IT service provider. He focuses on Development, Delivery and Sustenance of IT Applications in Supply Chain/Insurance/Banking/Finance. Albeit most of his projects are Java-based assignments, he is technology agnostic.

In his current role, Subrahmanyam is working as a solution provider for Commercial Healthcare, Insurance, banking and Financial systems with Mahindra Satyam. He is also TOGAF certified Enterprise Architect and IBM certified Ratioanal Software Architect.

GVB Subrahmanyam has an M.Tech. and Ph.D. from IIT Kharagpur in the area of Chemical Technology, India and MS in Software Systems from BITS Pilani. He is also a PMI certified PMP. He attended one year of the Executive Program in Business Management(EPBM) from IIM Calcutta.

More Stories By Sriramachandra Murthy C

Sriramachandra Murthy C is a senior Solutions Architect at Java Competency in Mahindra Satyam. He can be reached at [email protected]

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.