Click here to close now.

Welcome!

Microservices Journal Authors: Liz McMillan, Kevin Jackson, Carmen Gonzalez, Yeshim Deniz, Jayaram Krishnaswamy

Related Topics: Microservices Journal, Java, Web 2.0, Cloud Expo, Big Data Journal, SDN Journal

Microservices Journal: Blog Feed Post

Connected Architecture for a Connected Planet

Or how to connect the architecture dots to support a smart connected planet

Or how to connect the architecture dots to support a smart connected planet.

Introduction
The notion of a connected planet is far from new. However, the number of connections as illustrated in figure 1 is growing at an exponential rate, and it is fast becoming a reality in which many organizations must operate.

However, I doubt many organizations are preparing for this in a systematic way. More likely, experience suggests that dozens of connected ‘solutions' will permeate the organization via myriad routes and just add to the complexity of the business and IT landscape, becoming yet more spaghetti that someone is left to untangle.

Architecture is key to dealing with this. However, architectural practices must evolve to themselves become more connected, and not a set of isolated disciplines as they are often practiced today. Hence, in this note as well as considering the challenges and opportunities provided by the connected planet, I outline the role of connected architecture.

The Connected Planet
The looming challenge, or for some the opportunity, facing organizations is how they cope with the scenario shown in figure 1.

Figure 1 - The Connected Planet

Namely, that there will be

  • Trillionsof connected things, sometimes dumb but increasingly smart
  • Used by billionsof people, socializing and interacting to evaluate and rate you, your products, prices, and competitors.
  • Generating quadrillionsof messages representing quadrillions of events, some significant but many insignificant
  • Connected to millions of APIs and services, hosted in the cloud
  • Accessing and creating petabytes of information, both current and historical

This is a scenario I first documented back in a blog in2009 [1]. IDC talk about this as the "3rd platform, built on mobile devices and apps, cloud services, mobile broadband networks, big data analytics and social technologies" [2], and paint a scenario in their research that reads remarkably similar to the above.

Winners and Losers on the Connected Planet
The key issue for organizations will be

  • How does the business cope with information overload, or derive value from it?
  • How does IT deliver business solutions that manage the resulting transaction and information explosion, in a cost-effective manner?

The winners in this scenario will be those that exhibit the characteristics outlined in Table 1.

Winners are:
Constantly Connected With their Customers. Anywhere, Anytime, Anyhow
Constantly Engaged To help customers (and themselves) make informed decisions
Agile Responsive to change Creating new opportunities
Decoupled Provider from Consumer Solution from Technology Application from Process from Capability
Responsive Sensing and predicting events Correlating events Autonomic response
Excellent Six-Sigma products and processes
Efficient Automated and Autonomic Low operational cost per event response (e.g. business transaction) Optimized processes
Federated Driving multi-party ecosystems (internal and external)
Focused On core capabilities Best sourcing and collaborative sourcing of non-core capabilities

Table 1 - Winners and Losers on the Connected Planet By implication, the losers will be those organizations that fail to exhibit these characteristics!

The Connected Architecture Solution
So, how does an organization make sense of trillions of connected things and billions of people accessing petabytes of information via millions of APIs and services? Firstly, organizations and their IT solutions need to become increasingly,

  • Autonomic, in the way they,
    • respond to events, and how they correlate events and information
    • discover new service providers and their APIs
    • manage resources, adopting the principle of ‘management of services, by services'
    • freeing up human resources to deal with exceptions and ‘special cases'
  • Analytical, in the way they,
    • make sense of events and information
  • Decoupled, in the way they,
    • participate in federated ecosystems, not tightly bound partnerships
    • separate service provider from service consumer
    • assemble solutions from services not implementations

Figure 2 - Connected Architecture

As stated earlier, architecture is key to dealing with this. However, there is no one architectural ‘style' that encompasses everything that is required to solve the problem. It would be tempting to say the answer is SOA, or the answer is WOA, or any other acronym that is or was flavor of the month, or for architects to believe that it all revolves around whatever is their ‘pet' approach. While SOA principles of encapsulation and separation will inevitably be at the heart of the connected architecture, the practical reality of a collaboration between disparate organizations and capabilities will mean a federated architecture involving different technical solutions.
As illustrated in figure 2 what is required is an agile federated approach to architecture that assembles a Connected Architecture consisting of the following,

  • Web 2.0 Architecture - enabling people to rapidly mash up user and community driven solutions, in turn assembled from millions of APIs and services, and generating quadrillions of events,
  • leveraging Enterprise Mobility to connect employees, partners and customers, and their devices, anytime, anywhere,
  • requiring Event Driven Architecture (EDA) to determine the autonomic response required to sensors and changes in state, and correlate events,
  • that are also placed into context by agile Business Process Architecture (BPA/BPM) and Information Architecture (IA), with Real-time Business Analytics (BA) to make sense of what is happening,
  • using capabilities provisioned through APIs and services in a Service Oriented Architecture (SOA) that provides a formal basis for the decoupling of Provider and Consumers resources,
  • combined with a Web Oriented, or Resource Oriented Architecture (WOA/ROA) exchanging information between those trillions of devices in an efficient manner that will likely be done in a more lightweight manner than full blown Web Service-based SOA, with their implementations defined in a Component Based Software Architecture (CBSA) - with the focus on right-grained software units enabling agile, federated software delivery, that is hosted anywhere, anytime on a Cloud Based Architecture (CBA) that describes the virtualized, federated infrastructure providing scalability, reliability.

No one of these styles covers the problem space by itself. Rather, the problem space needs to be decomposed and the appropriate architecture approach applied to each domain.

Connected Platform

Another key enabler will be the increasing use of ‘Connected Platforms'. Cloud ‘platforms' such as Salesforce, Facebook or Amazon are in wide use and are already dominant in their respective domains because their platforms provide a considerable benefit by way of platform capabilities in comparison to building their own, and more importantly to business perhaps, provide a gateway to a ready-made ecosystem that use the platform.
Expect Connected Platforms to emerge that act as a ‘hub' or focal point around which industry ecosystems evolve, and it is likely that every industry will come to be dominated by a few key platform providers.

Many organizations will therefore have little choice of which Connected Platform they use as they will be forced upon them by participants in their industry - either by the 400lb gorillas who already dominate their industry, or by the platforms to which their ecosystem and end customers have gravitated, forcing them to adopt.

As illustrated by figure 3, the challenge for each enterprise will be to determine,

  • what their role is in the ecosystem, as provider and /or consumer, or possibly platform operator
  • hence, which services they should be expected to provide, and which they should consume
  • what services the Connected Platform is or should be providing, and who should providing them
  • their willingness to depend on the Connected Platform and the extent to which they allow the platform to dominate
  • the extent to which architects design their service architecture around the Connected Platform, or to what extent they should design their own platform independent architecture, especially for large organizations who may participate in multiple overlapping ecosystems, with multiple Connected Platforms.

Figure 3 - The Connected Platform

The Architect's Challenge

The key challenge for architects is that they cannot treat the various elements of the Connected Architecture as they often do today - as architectural silos [3] in ivory towers. Instead, as discussed earlier the elements must work seamlessly together. But this isn't solved by Enterprise Architecture - which may contain elements of all these - at least not alone, as this is about working at the detailed level to deliver solutions, not just a high-level view of the enterprise.
Hence it is important that architects develop a consistent framework for collaboration within the Connected Architecture. This is an area in which Everware-CBDI is well placed to assist.

IASA UK Architecture Summit

My colleague David Sprott and I will be running a one day workshop on these and other related ideas at the IASA UK Architecture Summit.

References

[1] Architecture for the Smarter Planet. http://lwsoa.blogspot.co.uk/2009/10/architecture-for-smarter-planet.html [2] IDC Predictions 2013. November 2012, IDC #238044, Volume: 1 http://www.idc.com/research/Predictions13/index.jsp#.UR4HSmf-unI [3] Beware the new silos! http://everware-cbdi.com/index.php?cID=118&cType=document

Read the original blog entry...

More Stories By Lawrence Wilkes

Lawrence Wilkes is a consultant, author and researcher developing best practices in Service Oriented Architecture (SOA), Enterprise Architecture (EA), Application Modernization (AM), and Cloud Computing. As well as consulting to clients, Lawrence has developed education and certification programmes used by organizations and individuals the world over, as well as a knowledgebase of best practices licenced by major corporations. See the education and products pages on http://www.everware-cbdi.com

@MicroservicesExpo Stories
SYS-CON Events announced today that Ciqada will exhibit at SYS-CON's @ThingsExpo, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY. Ciqada™ makes it easy to connect your products to the Internet. By integrating key components - hardware, servers, dashboards, and mobile apps - into an easy-to-use, configurable system, your products can quickly and securely join the internet of things. With remote monitoring, control, and alert messaging capability, you will mee...
I woke up this morning to the devastating news about the earthquake in Nepal. Sitting here in California that destruction is literally on the other side of the world but my mind immediately went to thinking about my good friend Jeremy Geelan. See Jeremy and his family have been living in Kathmandu for a while now. His wife, in fact, is the Danish Ambassador to Nepal!
Public Cloud IaaS started it's life in the developer and startup communities and has grown rapidly to a $20B+ industry, but it still pales in comparison to how much is spent worldwide on IT: $3.6 trillion. In fact, there are 8.6 million data centers worldwide, the reality is many small and medium sized business have server closets and colocation footprints filled with servers and storage gear. While on-premise environment virtualization may have peaked at 75%, the Public Cloud has lagged in ado...
Dave will share his insights on how Internet of Things for Enterprises are transforming and making more productive and efficient operations and maintenance (O&M) procedures in the cleantech industry and beyond. Speaker Bio: Dave Landa is chief operating officer of Cybozu Corp (kintone US). Based in the San Francisco Bay Area, Dave has been on the forefront of the Cloud revolution driving strategic business development on the executive teams of multiple leading Software as a Services (SaaS) ap...
ProfitBricks, the provider of painless cloud infrastructure IaaS, today released its SDK for Ruby, written against the company's new RESTful API. The new SDK joins ProfitBricks' previously announced support for the popular multi-cloud open-source Fog project. This new Ruby SDK, which exposes advanced functionality to take advantage of ProfitBricks' simplicity and productivity, aligns with ProfitBricks' mission to provide a painless way to automate infrastructure in the cloud. Ruby is a genera...
This digest provides an overview of good resources that are well worth reading. We’ll be updating this page as new content becomes available, so I suggest you bookmark it. Also, expect more digests to come on different topics that make all of our IT-hearts go boom!
The 5th International DevOps Summit, co-located with 17th International Cloud Expo – being held November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the...
Microsoft is releasing in the near future Azure Service Fabric as a preview beta. Azure Service Fabric is built to run microservices - a complex application consisting of smaller, interlocked components that enables updating components without disrupting service. Microsoft has used this over the past few years internally for many of its own applications and the new release is for general use, a new product. OSIsoft is an early adopter of this system and run with it to expand into the explo...
79% of new products miss their launch date. That was the conclusion of a CGT/Sopheon Survey in which the impact of such market misses were also explored. What it didn't dig into was the reason why so many products and projects miss their launch date. When we start digging into the details with respect to applications, we can find at least one causal factor in the delivery process, specifically that portion which focuses on the actual move into production, from which consumers (internal and...
This is a no-hype, pragmatic post about why I think you should consider architecting your next project the way SOA and/or microservices suggest. No matter if it’s a greenfield approach or if you’re in dire need of refactoring. Please note: considering still keeps open the option of not taking that approach. After reading this, you will have a better idea about whether building multiple small components instead of a single, large component makes sense for your project. This post assumes that you...
DevOps tasked with driving success in the cloud need a solution to efficiently leverage multiple clouds while avoiding cloud lock-in. Flexiant today announces the commercial availability of Flexiant Concerto. With Flexiant Concerto, DevOps have cloud freedom to automate the build, deployment and operations of applications consistently across multiple clouds. Concerto is available through four disruptive pricing models aimed to deliver multi-cloud at a price point everyone can afford.
This is my first blog post at AppDynamics, and I have to say that it’s great to be aboard. It’s been a hectic first couple of weeks, but the energy, enthusiasm and friendliness of everyone I have met has made me very excited about 2015! AppDynamics has a market leading APM and analytics platform but it also takes great people to make a great company – and AppDynamics has a wealth of talent! So to start my blogging life at AppDynamics I want to focus on something that is a red-hot buzzword in IT...
There is no quick way to learn Jython API but to experiment with it. The easiest way is to start with Jytutor extension for XL Deploy. Now you can also use the code snippet for exposing jython/python context in XL Deploy environment by running it directly in Jytutor Here’s how you can go ahead with that Download the Jytutor extension referring to the Jytutor Blog or from the following link https://github.com/xebialabs-community/xld-jytutor-plugin/releases Shutdown your XL Deploy server...
ProfitBricks has launched its new DevOps Central and REST API, along with support for three multi-cloud libraries and a Python SDK. This, combined with its already existing SOAP API and its new RESTful API, moves ProfitBricks into a position to better serve the DevOps community and provide the ability to automate cloud infrastructure in a multi-cloud world. Following this momentum, ProfitBricks has also introduced several libraries that enable developers to use their favorite language to code ...
ProfitBricks, the provider of painless cloud infrastructure IaaS, announced the launch of its new DevOps Central and REST API, along with support for three multi-cloud libraries and a Python SDK. This, combined with its already existing SOAP API and its new RESTful API, moves ProfitBricks into a position to better serve the DevOps community and provide the ability to automate cloud infrastructure in a multi-cloud world. Following this momentum, ProfitBricks is also today introducing several l...
What exactly is a cognitive application? In her session at 16th Cloud Expo, Ashley Hathaway, Product Manager at IBM Watson, will look at the services being offered by the IBM Watson Developer Cloud and what that means for developers and Big Data. She'll explore how IBM Watson and its partnerships will continue to grow and help define what it means to be a cognitive service, as well as take a look at the offerings on Bluemix. She will also check out how Watson and the Alchemy API team up to off...
The 17th International Cloud Expo has announced that its Call for Papers is open. 17th International Cloud Expo, to be held November 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA, brings together Cloud Computing, APM, APIs, Microservices, Security, Big Data, Internet of Things, DevOps and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding bu...
Security is one the more prominent of the application service categories, likely due to its high profile impact. After all, if security fails, we all hear about it. The entire Internet. Forever. So when one conducts a survey on the state of application delivery (which is implemented using application services) you kinda have to include security. Which of course, we did.
One of the most frequently requested Rancher features, load balancers are used to distribute traffic between docker containers. Now Rancher users can configure, update and scale up an integrated load balancing service to meet their application needs, using either Rancher's UI or API. To implement our load balancing functionality we decided to use HAproxy, which is deployed as a contianer, and managed by the Rancher orchestration functionality. With Rancher's Load Balancing capability, users ...
Choosing between BIG-IP and LineRate isn't as difficult as it seems.... Our recent announcement of the availability of LineRate Point raised the same question over and over: isn't this just a software-version of BIG-IP? How do I know when to choose LineRate Point instead of BIG-IP VE (Virtual Edition)? Aren't they the same?? No, no they aren't. LineRate Point (and really Line Rate Precision, too) is more akin to an app proxy while BIG-IP VE remains, of course, an ADC (Application Delivery ...