Welcome!

Microservices Expo Authors: Pat Romanski, Elizabeth White, Reinhard Brandstädter, Sujoy Sen, Liz McMillan

Related Topics: Microservices Expo

Microservices Expo: Article

Moving Toward the Zero Latency Enterprise

Moving Toward the Zero Latency Enterprise

The Internet makes it possible to deliver information almost instantaneously - anytime, anywhere - and is redefining the traditional boundaries around organizations and their IT systems. The Internet has turned buyers into sellers, sellers into buyers, and set new expectations for how services should be delivered. These expectations raise the bar for applications in terms of their need for interconnectivity and responsiveness. For businesses to remain competitive in this environment - or in the case of government agencies, responsive - they must embrace the idea that speed not only matters, but that it is now a key discriminator. Enterprises able to leverage the Internet's real-time nature and its technologies create competitive advantages that let them reap the benefits of greater efficiency, responsiveness, market share, and profitability. This promise has led businesses to look to interconnect their enterprise resource management (ERM), supply chain management (SCM), and customer relationship management (CRM) systems, both internally and externally; and government agencies to look for better ways to connect their systems with the public, their suppliers, and each other.

The Gartner Group coined the term "zero latency enterprise (ZLE)" to describe organizations that can exchange information with employees, trading partners and customers in near real time). The original focus was on internal systems, but much of what Gartner said applies equally to eliminating latency between internal and external systems. Figure 1 illustrates many of the concepts underpinning ZLE. In a ZLE organization, business events trigger system events that post actions and send responses throughout the enterprise. Bill Gates calls this level of interconnectivity a "digital nervous system." Like the human nervous system, the applications in a ZLE organization interconnect in such a way that they eliminate latency, which is the time gap between when the system receives information at one point and uses it, wherever needed, at others.

 

Becoming a ZLE
Transforming your organization into a ZLE is a three-phase process. You must understand where latency exists within your current processes and systems and your options for reducing or eliminating it. You must then create an architecture that focuses on minimizing latency along the critical path of as many business processes as possible. Finally, you must translate the architecture into an implementation plan that provides the roadmap for yours becoming a ZLE organization.

The first step in becoming a ZLE organization is identifying the major business processes within your organization that the ZLE architecture must support. One goal at this stage is to establish the architectural boundaries of the effort; will it deal with internal systems, external systems, or both? Another goal is to understand the dynamics of each business process: its tempo, meter, natural pauses and breaks. Understanding these dynamics is critical to recognizing latency and bounding the parameters for fixing it. It is important to remember that what constitutes latency in one process may be completely acceptable in another, even for the same application.

The next step is to decompose each business process into its applications and identify any latency points that exist. You should ask: What applications make up this process? Is latency a problem in either the overall process or one or more of its supporting applications? If so, how much of a problem? How much does its timing need to change? The result of asking and answering these questions is a list of business processes and applications that have latency problems.

Next you need to learn as much as possible about each latency point so that you can later devise techniques for removing, or at least minimizing, the latency. For internal systems, latency stems from several root causes (see Figure 2). Legacy systems are often stovepiped applications that were developed independently, over time, using different technologies. These applications create islands of information and functionality that are by their very nature difficult to integrate and share.

 

The same data belonging to different applications may be in different formats, follow different data validation and business rules, or be updated through completely different business processes. Interfaces within these older applications tend to be synchronous, tightly coupled, and driven more by the underlying technologies than the business needs they serve. Proprietary drivers, proprietary APIs, and proprietary formats represent only the tip of the iceberg when it comes to tying these systems together. One question you should ask is: What are each application's processing characteristics: batch, on-demand, or continuously running? Some may be batch oriented where you need them to be real time, others may have availability and reliability problems in cases where you need them to be 24x7. These issues frequently reflect age and technology differences that increase the difficulties in creating a coherent architecture.

Latency's causes multiply when you look at connecting internal and external systems. Each external system potentially represents a different set of technology, security, reliability, and manageability characteristics that your architecture must address.

The Architecture
At the end of the first phase, you should have a good understanding of your organization's internal and external business processes and the latency points you need to address within each. You're now ready to lay out the major business processes and applications and begin developing an overall ZLE architecture. It's important that your architecture address four key elements: business process management, data communications and routing, data transformation and formatting, and applications connectivity.

Business process management is, in my opinion, the most important part of the architecture; it's the glue that ties applications together. It should reflect the enterprise's business processes: assembling, sequencing, and orchestrating applications to align them with the business's natural processes and work flows. A workflow manager, a rules engine, and collaborative tools can be critical components at this level. Employees, business partners, and customers should find easy-to-use, intuitive interfaces supporting your core business processes.

Data communications and routing in conjunction with business process management create the central nervous system for the ZLE architecture. Two fundamental architectures, shown in Figure 3, have evolved in this area: hub-and-spoke; and data, or information, bus. The hub-and-spoke architecture uses a central integration engine and message queuing products, such as MQSeries and MSMQ, to integrate across applications. In this architecture, applications deal with one another through the central hub; this is responsible for extracting, transforming, and routing data and coordinating activities throughout the overall system.

 

The information bus architecture takes a decentralized approach. This architecture implements a common messaging framework, frequently using a publish and subscribe model, for intercommunication. Applications connect to this bus through application adapters and pass messages to one another by placing them onto the bus. The information bus may use either a messaging or workflow manager to assist in routing messages. You can use either architecture internally; the information bus is clearly superior when connecting between internal and external systems.

XML has become the lingua franca for solving the data transformation and formatting problem. It provides a flexible, extensible syntax for expressing both information and its structure in a meaningful format. Legacy applications can apply Extensible Stylesheet Language Transformations (XSLTs) to XML documents to convert information within those documents into whatever format they need. Data transfer and replication tools are also available for extracting, transforming, cleansing, and loading data for those wanting to make minimum modifications to existing applications.

Application integration can occur at many different levels (see Figure 4). A key question is whether there is overlap in the data the applications process or the business rules they enforce. User interface integration integrates applications at the presentation layer. This level of integration is valuable for connecting independent applications into common business processes. Data integration integrates applications at the database level by copying, transferring, or replicating information from one data source to another. This is a good strategy when transfers are timely and business rules are sufficiently compatible. Business logic integration integrates applications' middle tiers, allowing each application to retain its original business rules and logic. This level of integration works best for tying existing, interdependent applications together into more streamlined processes. Component integration integrates applications through their application programming interfaces (APIs), common components, or function calls. Integration at this level may require you to write proxy interfaces for some components; change call interfaces from direct to RPC for others; or adopt a distributed object model such as DCOM, CORBA, or Web services. This integration form is most useful for creating components several applications or processes can share.

 

A critical part of the application integration analysis is looking closely at each latency point to determine both the level of integration and corrections needed. The first step is to identify the appropriate integration level for each application: presentation, business logic, or data. Simply changing the application's invocation characteristics may be enough to also change its latency characteristics for some applications.

In situations where that is not the case, the next step is to drill down into the application and its interfaces with an eye towards improving the application's performance characteristics. The first, and simplest, corrective measure is to identify and remove any inefficiencies or chokepoints within the application. A second option is to look at overlapping the application's processing with that of others by making it an asynchronous process. Making an application asynchronous is straight-forward; you simply need to add a queue and alerting and rendezvous mechanisms. This can also be a good approach for dealing with reliability and availability problems caused by older systems. A third, and sometimes only, option is to redesign and rewrite the application.

You may need to make several passes through each of the four architectural elements to finalize the ZLE architecture. That isn't unusual. It's important that you come away with an overall architectural strategy, a list of integration points, and an idea of the integration strategies you'll need to address as part of the implementation process, which is the next step. Before proceeding to the implementation phase, it's a good idea to create a set of guiding principles to help in making architectural tradeoffs and selecting products. Questions you should answer include: Are the number or types of products you use of concern? How about the amount of code you write? Is it important to use the same solution for solving the latency problem between both internal and external applications? Is it important to use the same integration solution for integration points at the same level? Do you have large investments in ERM, SCM, or CRM solutions that will drive the implementation? With the answers to these questions in hand, you're now ready to look at options for implementing the architecture.

Implementation
Web services provides a lightweight, standards-based solution for implementing a ZLE architecture. Web services offers an integration model that brings applications together as loosely coupled components within a larger architectural framework. This standards-based framework closely aligns to the four elements in the ZLE architecture (see Figure 5). Business Process Execution Language for Web Services (BPEL4WS) and WS-Choreography are standards proposals for modeling, defining, orchestrating, and implementing business processes. WS-Transaction and WS-Security supply protocols for implementing atomic and business transactions, and security features such as authentication and encryption that are necessary for tying applications together into new business processes. The Simple Object Access Protocol (SOAP), HTTP, and TCP/IP create the backbone for data communications. WS-Routing, and WS-Referral address the data routing problem.

 

XML, which is the heart of Web services, provides a standard for data representation. XSLT adds a language for data transformation and formatting. SOAP-RPC contributes a lightweight, standards-based, platform-independent component model for implementing distributed components. In short, Web services provides all the elements necessary to implement whatever ZLE architecture you ultimately develop. With several of the standards still evolving, the issue is that products lag behind standards; that means you have to write more code.

If that is a concern, off-the-shelf enterprise application integration (EAI) products offer a good foundation for moving towards a ZLE organization. EAI products provide message broker and adapter technologies that quickly integrate applications to exchange and share information at the data, business logic, or presentation layers. Most EAI solutions implement either a message broker or bus concept corresponding to the hub-and-spoke and information bus architectures. If you decide this is the best approach for you, choose a product that fits into your overall integration strategy by providing the greatest number of integration adapters corresponding to the integration levels, points, and products you identified as part of your analysis.

EAI and Web services are extremely powerful together - EAI for fine-grained interfaces, Web services for coarse-grained interfaces. Many EAI vendors, such as SeeBeyond, TIBCO, webMethods, and IBM, recognize this synergy and offer products that are in fact a marriage between traditional EAI technologies and Web services. These products give you a best of both worlds option. Ultimately, the question boils down to which strategy works best with your architecture within your organization.

Summary
The costs of not becoming a ZLE organization are high; they translate to frustrated customers, disappointed partners, and missed opportunities. The challenges are in understanding critical business processes and developing an architecture that removes the problems creating latency both in the enterprise's internal systems and in their connections to systems be-longing to trading partners and customers. Web services standards, which EAI products are rapidly adapting, lay out the framework you need for implementing this architecture. As more companies adopt them, low cost, standards-based solutions for implementing ZLE applications may finally become a reality.

More Stories By Rickland Hollar

Rickland Hollar is a senior applications architect with the Central Intelligence Agency with over 30 years of experience in the industry. The views expressed in this article are his own and not necessarily those of the Agency. Prior to joining the CIA, he was president of a Virginia-based software development firm.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Wil Marshman 09/08/03 05:17:13 PM EDT

We [HP's NonStop Enterprise Division (NED), aka Tandem] picked up on ZLE several years ago and have produced a framework [as a product/solution] to facilitate customers doing what Holler describes. The Real Time Enterprise is an idea whose time has come [I assert that certain data needs to be accessible in real time for an enterprise to function effectively and many of our IT systems are not amenable to the changes required, mostly due to the silos that enterprises have built].

My point is that there are companies who can make the journey that Mr. Hollar describes easier. HP's ZLE implementation is ahead of the game.

Wil

@MicroservicesExpo Stories
SYS-CON Events announced today the How to Create Angular 2 Clients for the Cloud Workshop, being held June 7, 2016, in conjunction with 18th Cloud Expo | @ThingsExpo, at the Javits Center in New York, NY. Angular 2 is a complete re-write of the popular framework AngularJS. Programming in Angular 2 is greatly simplified. Now it’s a component-based well-performing framework. The immersive one-day workshop led by Yakov Fain, a Java Champion and a co-founder of the IT consultancy Farata Systems and...
IoT generates lots of temporal data. But how do you unlock its value? How do you coordinate the diverse moving parts that must come together when developing your IoT product? What are the key challenges addressed by Data as a Service? How does cloud computing underlie and connect the notions of Digital and DevOps What is the impact of the API economy? What is the business imperative for Cognitive Computing? Get all these questions and hundreds more like them answered at the 18th Cloud Expo...
Many banks and financial institutions are experimenting with containers in development environments, but when will they move into production? Containers are seen as the key to achieving the ultimate in information technology flexibility and agility. Containers work on both public and private clouds, and make it easy to build and deploy applications. The challenge for regulated industries is the cost and complexity of container security compliance. VM security compliance is already challenging, ...
@DevOpsSummit taking place June 7-9, 2016 at Javits Center, New York City, and Nov 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 18th International @CloudExpo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world.
Just last week a senior Hybris consultant shared the story of a customer engagement on which he was working. This customer had problems, serious problems. We’re talking about response times far beyond the most liberal acceptable standard. They were unable to solve the issue in their eCommerce platform – specifically Hybris. Although the eCommerce project was delivered by a system integrator / implementation partner, the vendor still gets involved when things go really wrong. After all, the vendo...
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
SYS-CON Events announced today the Docker Meets Kubernetes – Intro into the Kubernetes World, being held June 9, 2016, in conjunction with 18th Cloud Expo | @ThingsExpo, at the Javits Center in New York, NY. Register for 'Docker Meets Kubernetes Workshop' Here! This workshop led by Sebastian Scheele, co-founder of Loodse, introduces participants to Kubernetes (container orchestration). Through a combination of instructor-led presentations, demonstrations, and hands-on labs, participants learn ...
The initial debate is over: Any enterprise with a serious commitment to IT is migrating to the cloud. But things are not so simple. There is a complex mix of on-premises, colocated, and public-cloud deployments. In this power panel at 18th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists will look at the present state of cloud from the C-level view, and how great companies and rock star executives can use cloud computing to meet their most ambitious and disruptive business ...
The demand for organizations to expand their infrastructure to multiple IT environments like the cloud, on-premise, mobile, bring your own device (BYOD) and the Internet of Things (IoT) continues to grow. As this hybrid infrastructure increases, the challenge to monitor the security of these systems increases in volume and complexity. In his session at 18th Cloud Expo, Stephen Coty, Chief Security Evangelist at Alert Logic, will show how properly configured and managed security architecture can...
Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
Agile teams report the lowest rate of measuring non-functional requirements. What does this mean for the evolution of quality in this era of Continuous Everything? To explore how the rise of SDLC acceleration trends such as Agile, DevOps, and Continuous Delivery are impacting software quality, Parasoft conducted a survey about measuring and monitoring non-functional requirements (NFRs). Here's a glimpse at what we discovered and what it means for the evolution of quality in this era of Continuo...
You might already know them from theagileadmin.com, but let me introduce you to two of the leading minds in the Rugged DevOps movement: James Wickett and Ernest Mueller. Both James and Ernest are active leaders in the DevOps space, in addition to helping organize events such as DevOpsDays Austinand LASCON. Our conversation covered a lot of bases from the founding of Rugged DevOps to aligning organizational silos to lessons learned from W. Edwards Demings.
SYS-CON Events announced today BZ Media LLC has been named “Media Sponsor” of SYS-CON's 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. BZ Media LLC is a high-tech media company that produces technical conferences and expositions, and publishes a magazine, newsletters and websites in the software development, SharePoint, mobile development and Commercial Drone markets.
When I talk about driving innovation with self-organizing teams, I emphasize that such self-organization includes expecting the participants to organize their own teams, give themselves their own goals, and determine for themselves how to measure their success. In contrast, the definition of skunkworks points out that members of such teams are “usually specially selected.” Good thing he added the word usually – because specially selecting such teams throws a wrench in the entire works, limiting...
SYS-CON Events announced today TechTarget has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. TechTarget is the Web’s leading destination for serious technology buyers researching and making enterprise technology decisions. Its extensive global networ...
Application development and delivery methods have undergone radical changes in recent years to improve scalability and resiliency. Container images are the new build and deployment artifacts that are used to ship and run software. While startups have long been comfortable experimenting with and embracing new technologies, even large enterprises are now re-architecting their software systems so that they can benefit from container-enabled micro services architectures. With the launch of DC/OS, w...
Earlier this week, we hosted a Continuous Discussion (#c9d9) on Continuous Delivery (CD) automation and orchestration, featuring expert panelists Dondee Tan, Test Architect at Alaska Air, Taco Bakker, a LEAN Six Sigma black belt focusing on CD, and our own Sam Fell and Anders Wallgren. During this episode, we discussed the differences between CD automation and orchestration, their challenges with setting up CD pipelines and some of the common chokepoints, as well as some best practices and tips...
As AT&Ts VP of Domain 2.0 architecture writes one aspect of their Domain 2.0 strategy is a goal to embrace a Microservices Application Architecture. One page 9 they describe how these envisage them fitting into the ECOMP architecture: "The initial steps of the recipes include a homing and placement task using constraints specified in the requests. ‘Homing and Placement' are micro-services involving orchestration, inventory, and controllers responsible for infrastructure, network, and applicati...
Automation is a critical component of DevOps and Continuous Delivery. This morning on #c9d9 we discussed CD Automation and how you can apply Automation to accelerate release cycles, improve quality, safety and governance? What is the difference between Automation and Orchestration? Where should you begin your journey to introduce both?