Welcome!

Microservices Expo Authors: Pat Romanski, Gregor Petri, Elizabeth White, Liz McMillan, AppDynamics Blog

Related Topics: Microservices Expo, Java IoT, Agile Computing, @CloudExpo, @BigDataExpo, SDN Journal

Microservices Expo: 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
The many IoT deployments around the world are busy integrating smart devices and sensors into their enterprise IT infrastructures. Yet all of this technology – and there are an amazing number of choices – is of no use without the software to gather, communicate, and analyze the new data flows. Without software, there is no IT. In this power panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists will look at the protocols that communicate data and the emerging data analy...
DevOps at Cloud Expo – being held November 1-3, 2016, 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 world's largest enterprises – and delivering real results. Am...
About a year ago we tuned into “the need for speed” and how a concept like "serverless computing” was increasingly catering to this. We are now a year further and the term “serverless” is taking on unexpected proportions. With some even seeing it as the successor to cloud in general or at least as a successor to the clouds’ poorer cousin in terms of revenue, hype and adoption: PaaS. The question we need to ask is whether this constitutes an example of Hype Hopping: to effortlessly pivot to the ...
All clouds are not equal. To succeed in a DevOps context, organizations should plan to develop/deploy apps across a choice of on-premise and public clouds simultaneously depending on the business needs. This is where the concept of the Lean Cloud comes in - resting on the idea that you often need to relocate your app modules over their life cycles for both innovation and operational efficiency in the cloud. In his session at @DevOpsSummit at19th Cloud Expo, Valentin (Val) Bercovici, CTO of So...
Video experiences should be unique and exciting! But that doesn’t mean you need to patch all the pieces yourself. Users demand rich and engaging experiences and new ways to connect with you. But creating robust video applications at scale can be complicated, time-consuming and expensive. In his session at @ThingsExpo, Zohar Babin, Vice President of Platform, Ecosystem and Community at Kaltura, will discuss how VPaaS enables you to move fast, creating scalable video experiences that reach your...
If you’re responsible for an application that depends on the data or functionality of various IoT endpoints – either sensors or devices – your brand reputation depends on the security, reliability, and compliance of its many integrated parts. If your application fails to deliver the expected business results, your customers and partners won't care if that failure stems from the code you developed or from a component that you integrated. What can you do to ensure that the endpoints work as expect...
SYS-CON Events announced today the Enterprise IoT Bootcamp, being held November 1-2, 2016, in conjunction with 19th Cloud Expo | @ThingsExpo at the Santa Clara Convention Center in Santa Clara, CA. Combined with real-world scenarios and use cases, the Enterprise IoT Bootcamp is not just based on presentations but with hands-on demos and detailed walkthroughs. We will introduce you to a variety of real world use cases prototyped using Arduino, Raspberry Pi, BeagleBone, Spark, and Intel Edison. Y...
With the rise of Docker, Kubernetes, and other container technologies, the growth of microservices has skyrocketed among dev teams looking to innovate on a faster release cycle. This has enabled teams to finally realize their DevOps goals to ship and iterate quickly in a continuous delivery model. Why containers are growing in popularity is no surprise — they’re extremely easy to spin up or down, but come with an unforeseen issue. However, without the right foresight, DevOps and IT teams may lo...
As applications are promoted from the development environment to the CI or the QA environment and then into the production environment, it is very common for the configuration settings to be changed as the code is promoted. For example, the settings for the database connection pools are typically lower in development environment than the QA/Load Testing environment. The primary reason for the existence of the configuration setting differences is to enhance application performance. However, occas...
DevOps at Cloud Expo, taking place Nov 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 19th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long dev...
When scaling agile / Scrum, we invariable run into the alignment vs autonomy problem. In short: you cannot have autonomous self directing teams if they have no clue in what direction they should go, or even shorter: Alignment breeds autonomy. But how do we create alignment? and what tools can we use to quickly evaluate if what we want to do is part of the mission or better left out? Niel Nickolaisen created the Purpose Alignment model and I use it with innovation labs in large enterprises to de...
SYS-CON Events announced today that Numerex Corp, a leading provider of managed enterprise solutions enabling the Internet of Things (IoT), will exhibit at the 19th International Cloud Expo | @ThingsExpo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Numerex Corp. (NASDAQ:NMRX) is a leading provider of managed enterprise solutions enabling the Internet of Things (IoT). The Company's solutions produce new revenue streams or create operating...
Information technology is an industry that has always experienced change, and the dramatic change sweeping across the industry today could not be truthfully described as the first time we've seen such widespread change impacting customer investments. However, the rate of the change, and the potential outcomes from today's digital transformation has the distinct potential to separate the industry into two camps: Organizations that see the change coming, embrace it, and successful leverage it; and...
While DevOps promises a better and tighter integration among an organization’s development and operation teams and transforms an application life cycle into a continual deployment, Chef and Azure together provides a speedy, cost-effective and highly scalable vehicle for realizing the business values of this transformation. In his session at @DevOpsSummit at 19th Cloud Expo, Yung Chou, a Technology Evangelist at Microsoft, will present a unique opportunity to witness how Chef and Azure work tog...
Throughout history, various leaders have risen up and tried to unify the world by conquest. Fortunately, none of their plans have succeeded. The world goes on just fine with each country ruling itself; no single ruler is necessary. That’s how it is with the container platform ecosystem, as well. There’s no need for one all-powerful, all-encompassing container platform. Think about any other technology sector out there – there are always multiple solutions in every space. The same goes for conta...
Let's recap what we learned from the previous chapters in the series: episode 1 and episode 2. We learned that a good rollback mechanism cannot be designed without having an intimate knowledge of the application architecture, the nature of your components and their dependencies. Now that we know what we have to restore and in which order, the question is how?
Enterprise IT has been in the era of Hybrid Cloud for some time now. But it seems most conversations about Hybrid are focused on integrating AWS, Microsoft Azure, or Google ECM into existing on-premises systems. Where is all the Private Cloud? What do technology providers need to do to make their offerings more compelling? How should enterprise IT executives and buyers define their focus, needs, and roadmap, and communicate that clearly to the providers?
SYS-CON Events announced today the Kubernetes and Google Container Engine Workshop, being held November 3, 2016, in conjunction with @DevOpsSummit at 19th Cloud Expo at the Santa Clara Convention Center in Santa Clara, CA. This workshop led by Sebastian Scheele introduces participants to Kubernetes and Google Container Engine (GKE). Through a combination of instructor-led presentations, demonstrations, and hands-on labs, students learn the key concepts and practices for deploying and maintainin...
Analysis of 25,000 applications reveals 6.8% of packages/components used included known defects. Organizations standardizing on components between 2 - 3 years of age can decrease defect rates substantially. Open source and third-party packages/components live at the heart of high velocity software development organizations. Today, an average of 106 packages/components comprise 80 - 90% of a modern application, yet few organizations have visibility into what components are used where.
Keeping pace with advancements in software delivery processes and tooling is taxing even for the most proficient organizations. Point tools, platforms, open source and the increasing adoption of private and public cloud services requires strong engineering rigor - all in the face of developer demands to use the tools of choice. As Agile has settled in as a mainstream practice, now DevOps has emerged as the next wave to improve software delivery speed and output. To make DevOps work, organization...