Saturday, May 18, 2013

Mobility - Let us engage Deliberately and not by accident!


As I meet many clients and team members I realized one thing, and that is:
 
Mobile  will not fix or bypass existing deficiencies in the enterprise, on the contrary Mobility will bring these concerns front and center to all Mobile discussions. So Mobility is NOT about an app running on a mobile device, but have far deeper implications when it comes to enterprise integration and mobilizing these services. I think our experience and out platform can serve as our competitive advantage in surfacing and addressing these in our Mobile Conversations. From a platform perspective competing products also have to have the enterprise DNA in them. ( More on this in next post)

Mapping Enterprise design points to Technical design points:
In the spirit of engaging with a purpose and deliberately, I wanted to discuss an approach that will lay the foundation and provide a structure before we get into product features. The approach I usually take is devising a “Enterprise Design points” and mapping to “Technical Design Points”. The idea with this approach is to  ensure we capture the LOB/Business design requirements and  use the tools at our disposal  to  define  a solution architecture to address the enterprise design points.


Enterprise Design Points:
a.     Deliberate and Intentional engagement
b.     Exposing back end services and data
c.     Data transfer and data growth considerations
d.     Bandwidth and TCP Socket chatter
e.     MEAP or MCAP?
f.      Enterprise Integration
g.     Security – enterprise and endpoint security
h.     Device and Platform support
i.      Legal responsibilities – Application store, client data and resulting exposure

 Which Maps to

Technical Design Points:
a.     Enterprise application integration (tools and libraries
b.     Device integration and peripheral support
c.     Application client runtime
d.     Device/OS platform support 
e.     Packaged mobile
f.      Hosting
g.     Architectural flexibility

As always I love to hear from you your critique and thoughts.


– Let us engage Deliberately and not by accident!

Have  a great week ahead.

;)
Nitin

Tuesday, May 7, 2013

Mobile is lot more than just a Mobile App and Cloud technologies are even more important than ever


Folks

 This post is long overdue, and IBM Impact 2013 was busy, amazing, productive and exhausting all at the same time.  I think many of these Conferences like IBM Impact2013 challenges  us in many ways, our bodies, our mind and ability to deliver a meaningful and tailored message is not an easy task.  I was amazed to meet many brilliant colleagues  and such events makes one humble and fortunate at the same time to be a part of interesting evolution in our lifetime.

Mobile
Yes it was a certainly a hot topic, and it was evident that we have moved our conversation from Why? To How?  Which indicates a certain level of Maturity. IBM MobileFirst message was loud and the relevance of the topic was very well received.
            Another Important thing that I learned is that Mobile is NOT just about Mobile application but more than that. The ‘System of engagement’ and/or ‘Internet of things’ that we talk about is real and here. Here are a few nuggets:
1.     Maturity in M2M or M2X and ‘Connected’ vehicle is seen a trend that will change the way we live. Networks are gearing up to provision the bandwidth and special 4G LTE offering and Auto Manufacturers  are ramping up the  Connected Vehicle’ offering. 

Google This: M2m Multi-Operator alliance – include NTT Docomo, Etilsalat, Telefonica are promoting a common standard.
Real ‘Smart cars” – Fords AppLink lets driver do interesting things with Glympse app. GM announced 4G LTE technology in their cars, Volvo ‘Connected Vehicle cloud’, Toyota ‘Friend’ – trends indicating that Cars may be ultimate Mobile devices and possibilities for commerce, retail, automobile and others are immense

2.     Internet of Things is also Mobile: This is real, where now the system of Interaction is the system of engagement i.e. my utility appliances can be instruments, intelligent and interconnected.

Google This: Qualcomm – Alljoyn – Open source software that enables this technology for these appliances to not only communicate but be controlled. – Intelligent.

3.     mHealth, mEducation. And so on… so I am now convinced that this is big 

 Thought:

Think Optimized Mobile Middleware: We need to think about  ‘Security’ and ‘Scalability’ – and from a ‘Systems’ perspective, I think we should look at all ‘touch points’ of my enterprise that includes the device as it is now an extension of my enterprise. Because: my application/app, an agent or a process that is ‘engaging’ with my enterprise is running on that ‘Device’. –something to think about!!



API Management:
 API Management is relevant. I think  this is not an accident but a trend that we should not only be aware of but also understand. API management I think like Cloud is an important part of the mobile story. Here is why:
1.     API management is – Well, let’s us say a ‘Public persona’ and provides Middleware services tool to manage and operate the services that are hit by Mobile devices and other applications.
2.     It is a contract between an API provider and consumer. This contract dictates the data packaging and/or business logic. With the volume and diversity of type of requests from different types of applications ( Mobile/web/cars etc) API management has become relevant and create a ‘Marketplace’ where producers and consumers thrive.
3.     This is vital to understand, I discuss the ‘unintended consequences’ of going mobile, which is known to increase the traffic and response time burden  by almost 10X. Think of increase in status checks, content download and like ‘Mobile Transactions’. So an unplanned  App or a mobile app without backing of a mobile strategy and planning  can swamp network, and connections to middleware services. API management  and ‘Marketplace’ also gives Mobile application developers  a rich choice of APIs to use for consistent and accessible interface that can be governed and managed. Forrester (think tank) suggests thinking of API management as Cloud Connect Technology that lets the data in the Cloud/data center get out and back to the Mobile app that needs it.. securely.

A typical API management solution will include :
a.     Developer Portal – signup and understand the use and consumption of APIs.
b.     API Gateway – tom mediate and govern the traffic between consumer and provider.
c.     API Lifecycle management – simple Governance enforcement.
Let us take time to understand how this can speed up development and deployment of Mobile and adaptive web applications.


Cloud – Increasingly important for Mobile presence.

So, I have always believed that  we can always do a better job in Cloud delivery than we have in the past. Cloud we define is a ‘Service Delivery and Consumption” model, and regardless of the medium, virtualization technologies involved  it  is about network and access to “Stuff” on demand.
We are seeing that clients expect a certain level of  Cloud integration  for things like Storage, profile access, application data, application provisioning, application  and runtime hosting and on and on… idea being that  we want the ‘enterprise’ to  consume data, APIs and quickly ‘compose’ application that can then be deployed quickly, forming of a web of services. While this seems enticing and natural extension to Mobile way of doing things, such initiatives require planning around security, governance, management and availability of network. But IMHO for us to success in marketplace a ‘cloud integration’ is a  must.

As always I would like to hear your thoughts,

Have  a great week!

:)
Nitin