Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Kelly Burford, Karthick Viswanathan, Scott Davis

Related Topics: Microservices Expo, Java IoT, Industrial IoT

Microservices Expo: Article

Business Design for the Service-Oriented Enterprise

Design patterns for the smart, continuously evolving, virtual enterprise.

The way we design business is undergoing profound transformation. For the past 100 years business design has been directly influenced by Frederick Taylor, focused on how we do work and how we can make it more efficient. The LEAN and Six Sigma movements are the visible manifestation of that thinking. Together with BPM they have focused on incremental improvements of primarily internal processes and tasks encoded in process orchestration and workflows that control how the enterprise works.

But this is equivalent to looking in the rear view mirror to design tomorrows business. In this article we will look at three major trends that are going to break this conventional model.

  • Smart behaviors enabling cross ecosystem processes
  • Capability services (independent business components) enabling continuously evolving business models
  • The convergence of consumer and business IT enabling the real end user

Along the way we identify and list a number of primary patterns that describe this new world. Most of which by the way, are not new.

The original SOA vision of the enterprise as a network of services is now attainable by many enterprises. But the route to the Service Oriented Enterprise is not so direct; it must evolve and integrate with an ecosystem of services that reflects business reality.

Smart Behavior in the Ecosystem
Just over ten years ago when you walked into an airport you would stand in line for an agent and collect your boarding pass. When you wanted to purchase a book you visited a bookshop. In each of these use cases we transacted with human beings.

Today, in each of these use cases, we interact instead with an automated interface that actually does more than the human interface. In the case of Amazon of course they have moved far beyond the scope of a book shop, the interface is considerably improved because Amazon provides extensive customer reviews and a virtual market in which we can interact with vast numbers of specialist providers to acquire niche or second hand products. In the case of the boarding pass collection, not only has the airport check-in process been replaced with self-service, the physical pass itself is eliminated and we can have an image of the boarding pass sent to our smart phone which is scanned at the security checkpoint. At the same time the boarding pass frequently contains personalized advertising and vouchers for airport shops and behind the scenes the airline system may be checking with security agencies as well as perhaps establishing lounge access and in some territories checking with immigration and passport control as well.

What.s happening in these examples is that we have moved beyond automation of the basic process and integrated services from an ecosystem of providers that span numerous enterprises, to deliver an enhanced and more efficient service to the consumer, and in the process, eliminated unnecessary human intervention.

These examples have some very important lessons for us all. First, enterprise architecture must increasingly be scoped around an ecosystem that encompasses traditional and new participants in the process. Second intervention in the business process should be eliminated except where it is an intrinsic step in the process for a human or some form of node or agent to play a part. The real end user places an order. A toll barrier detects and reports a vehicle. A scanner detects and reports a piece of luggage has been received at an airport terminal. But be careful, because apart from customers and physical actions, most "human" interventions can and should be substituted by rules, and alerts used to bring humans into play only on an exceptional basis.

In recent years there has been a focus on autonomic or smart systems and there has been much attention on fully automating certain processes in verticals such as energy, climate change, transportation and healthcare. These processes are rather obvious candidates for rules based mediation and intervention, often using sensors to drive rules based processes, but we should look beyond this relatively narrow definition of smart systems and apply the same thinking across the entire enterprise architecture and business process design.

Continuously Evolving Business
As the enterprise becomes increasingly part of one or more ecosystems, (yes each enterprise will almost certainly be involved in more than one) there are further predictable changes to the business design. First, the enterprise inevitably becomes more focused on its core business because participation of partners naturally creates networks of specialists. Consider what is Amazon.s core business? They may have started out as a book seller in 1994, but today the core business today is clearly the platform, including all layers of the stack spanning Cloud technology to commercial storefront and business intelligence.

Second, the enterprise must become much more adaptive. Because the ecosystem is comprised of numerous specialist partners, each participant will be driving an independent business strategy that naturally serves their own objectives and goals. So each participant will need to be prepared to both lead and respond in equal measure, and this applies equally to a platform provider as an ecosystem participant.

In consequence each enterprise needs to manage its business as a set of highly independent capability services that can be upgraded, switched on and off with minimal impact on the rest of the ecosystem with upgrade lead times measured in weeks, not months and years.

Third, successful specialized capabilities may well exhibit exponential growth as the enterprise is so much more tightly focused.

Over the past decade the idea of business change has become almost a cliche. The business services and software marketing industries have pulled the change rabbit out of the proverbial hat so many times that we are all quite inured to the message. However the above discourse is quite serious, insofar as the supply and demand signals for change are clearly set to become even more acute. And the required response time will be similarly challenging.

The way to respond to this challenge is to reduce dependencies, to forge independent units of capability that offer software services that automate the interfaces with capability consumers and that are designed to be rapidly evolved without major impact on the consumers.

In the early stages of SOA, we and many other analysts articulated a clear vision for SOA . a network of standardized services that provided a stable and enduring set of interfaces for consumers to easily integrate core capability services into customized solutions, supported by highly independent implementation components with no implementation level dependencies. In other words architecture designed to support continuous evolution.

Since then a few organizations have achieved that vision, but it must be said, it is a minority of enterprises. We anticipate that given the radical transformation in prospect, most enterprises will redouble their efforts to reboot their SOA, to achieve the service architecture vision which is going to be a critical success factor for most enterprises.

Convergence of Consumer and Business IT
People are demanding to use their own gadgets and devices for business use. Attempting to prevent this is very short sighted.

Since its inception in the 80s the PC has dominated business computing. Over the past decade the rise of consumer technology has been spectacular but largely separate from enterprise computing. IT departments have frequently laid down rules for use of consumer technologies, in many cases using security as a primary reason why personal devices of all types should not be used in the business network. Of course Web services protocols have shown that message based security is perfectly adequate, and in many situations provides stronger risk prevention than transport based security.

CIOs that try to limit consumer technology run the risk of creating a grey zone, where employees bring their own technology to work in defiance of IT policy. This is not a new problem as it happened in the 80s when computer enthusiasts brought their PCs into the office to use VisiCalc, Excel and Word. But this time around it.s not only enthusiasts, it.s pretty much everyone!

While PCs are not going to disappear any time soon, it.s clear that there is a huge groundswell of demand for people to use their own devices in business, or at least to be provided with consumer grade technology. And this demand isn.t restricted to college graduates - the use of smartphones and tablets is now ubiquitous across society. So the challenge for IT departments is for consumer technologies to be integrated into the business process both internal to the enterprise and with external end users.

Consequently we are already seeing the reversal of the normal pattern where business leads technology adoption; today consumer technology, smart phones and tablets, are being brought into the enterprise computing network. At this juncture therefore, the term "consumer" technology is becoming redundant and might be superseded by "personal". And it really is personal - the reason people want to use their own device is because of the amazingly high ease of use in a single, integrated device that spans all requirements.

Yesterday's IT business was also all about the User Interface (UI). The UI was the way the business visualized and articulated its requirements, and was the foundation stone of countless methodologies and the basis for Agile methods and prototyping. For the past few years the emphasis has been on multi-channel UI, supporting conventional client/server, browsers, kiosks and devices. But this is all going to change.

WILLEM EELMAN, the chief information officer (CIO) of Unilever, an Anglo-Dutch consumer-goods giant, recounts the reaction of young employees when they first come across the complicated and often confusing ways in which many big corporate IT systems still present information to staff. ¡°They take a look at a business-application screen and they scream in horror,¡± he says. The youngsters are even more horrified when presented with tomes of instructions through which they must plough before getting down to work. Economist October 8th 2011

As discussed above, in tomorrow.s business our objective is to eliminate all unnecessary user interfaces in a business process. The UIs that remain should be genuine user interfaces that are connected to the genuine end user . not an internal proxy. This is illustrated by the Horse.s Mouth pattern. And the use of personal technology allows us to communicate effectively with the actual end user in real or near real time, with a user interface that is appropriate for the relationship between provider and consumer.

One of the most interesting developments in the consumer technology space has been the emergence of the "App" and App Store. This allows a customized interface with an appropriate amount of local processing, and customization. Enterprises are clearly using Apps today for consumer purposes and we should expect that enterprises will extend this model for business process integration both with consumers and other parties to the process to enable improved behaviors (quality, ease of use) as well as alternative communication mechanisms to respond to personal profiles. The airline boarding pass App has been a pathfinder, and many business processes will follow the example.

Beyond the "horses mouth" we expect most interfaces in a business process will be service interfaces with ecosystem partners. Most end user interfaces will be mobile .using heterogeneous, consumer devices. Regardless of whether the user is an employee, partner employee, agent or end consumer, there will be a multiplicity of devices that will be in the overwhelming majority of situations, the end users. personal property, and not under the control of any enterprise.

Finally we note the recent acquisition by Apple of Siri, a small start-up that created a voice activated personal assistant application. A Siri user can simply say, "Tell my wife I.ll be 20 minutes late," and Siri scours the user.s social networks, address books and other programs, finds the person tagged "wife" converts the message to text, and sends it directly to her phone. We expect voice recognition combined with smart Apps to considerably strengthen the convergence of consumer and business technologies and stimulate a whole raft of innovative UI patterns.

Patterns
The core pattern underlying the Service Oriented Enterprise (SOE) is illustrated in Figure 1: the Differentiated Response. An SOE is part of an ecosystem in which capabilities (potentially from many collaborating businesses) subscribe to events which are of common interest.

Figure 1: Differentiated Response Pattern

However in the SOE subscribing capabilities may have very different perspectives on the common event. For example:

  • A sensor at a toll barrier records a car license plate passing the barrier. The toll operator capability will typically make the immediate response of posting a charge to an account. But in parallel the police may also subscribe to the service and track movements of license plates of interest. Also in parallel a market research company may subscribe to the data for market analysis.

The differentiated response pattern encourages us to look for collaborations across unconventional partners that would not typically be part of a unified business process.

Conclusion and Remarks
In the CBDI SOA Maturity Model first published in 2004 we identified the Ecosystem maturity stage as "following" the Enterprise stage. For many years few were interested in what lay beyond the enterprise, for most organizations it was out of sight. However we always predicted that last stage implied big changes and today we see the SOE will have profound impacts on organizations. For example:

  • A reduction in enterprise scope to focus on core capabilities
  • Capability ownership drives organizational structure
  • Autonomics and direct connection with leaf nodes in the business process will lead to reduction in workforce.
  • Empowerment of the customer as the real ¡°end user¡±.
  • The demise of intermediaries
  • The demise of the call center as routine transactions and queries handled by smart autonomic systems; the rise of advisors . specialists who have skills and authority to sort out real exceptions

There are examples of the SOE in some successful corporations today. But you have to assess that they arrived at the strategy by a combination of lucky accident and individual genius. So what do architects and business managers do to make sure they have a strategy and are moving down the right path? Here are some recommended actions:

  1. Understand your capabilities, classify them as core and context and act accordingly
  2. Figure out your place in one or more ecosystems? Look at it from your customers., partners and suppliers perspective. Analyze the capability intersection
  3. Organize around core capabilities, encapsulate business processes, MI and BI inside the capabilities.
  4. Partner for context capabilities

Finally there is a table of relevant patterns appended to this article. Some of these are new and we will document these further.

References

More Stories By David Sprott

David Sprott is a consultant, researcher and educator specializing in service oriented architecture, application modernization and cloud computing. Since 1997 David founded and led the well known think tank CBDI Forum providing unique research and guidance around loose coupled architecture, technologies and practices to F5000 companies and governments worldwide. As CEO of Everware-CBDI International a UK based corporation, he directs the global research and international consulting operations of the leading independent advisors on Service Oriented Application Modernization.

@MicroservicesExpo Stories
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
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...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, 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.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, 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.
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...