|By Rickland Hollar||
|August 19, 2003 12:00 AM EDT||
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.
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.
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.
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.
|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.
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at 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. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
May. 3, 2016 10:00 AM EDT Reads: 1,326
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
May. 3, 2016 08:30 AM EDT Reads: 318
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
May. 3, 2016 06:45 AM EDT Reads: 828
With DevOps becoming more well-known and established practice in nearly every industry that delivers software, it is important to continually reassess its efficacy. This week’s top 10 includes a discussion on how the quick uptake of DevOps adoption in the enterprise has posed some serious challenges. Additionally, organizations who have taken the DevOps plunge must find ways to find, hire and keep their DevOps talent in order to keep the machine running smoothly.
May. 3, 2016 06:30 AM EDT Reads: 1,476
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
May. 3, 2016 06:15 AM EDT Reads: 852
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
May. 3, 2016 03:30 AM EDT Reads: 2,004
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
May. 3, 2016 03:00 AM EDT Reads: 1,437
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
May. 3, 2016 12:45 AM EDT Reads: 1,041
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
May. 2, 2016 08:30 PM EDT Reads: 1,548
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
May. 2, 2016 08:30 PM EDT Reads: 2,169
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
May. 2, 2016 07:45 PM EDT Reads: 1,899
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
May. 2, 2016 06:00 PM EDT Reads: 1,550
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.
May. 2, 2016 12:00 PM EDT Reads: 1,571
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
May. 2, 2016 10:15 AM EDT Reads: 1,109
SYS-CON Events announced today that DatacenterDynamics 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. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.
May. 2, 2016 06:30 AM EDT Reads: 2,561
Call it DevOps or not, if you are concerned about releasing more code faster and at a higher quality, the resulting software delivery chain and process will look and smell like DevOps. But for existing development teams, no matter what the velocity objective is, getting from here to there is not something that can be done without a plan. Moving your release cadence from months to weeks is not just about learning Agile practices and getting some automation tools. It involves people, tooling and ...
May. 2, 2016 04:30 AM EDT Reads: 1,540
Between the mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at 18th Cloud Expo, Charles Kendrick, CTO & Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how business and devel...
May. 2, 2016 04:30 AM EDT Reads: 1,792
SYS-CON Events announced today that Stratoscale, the software company developing the next generation data center operating system, will exhibit at 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. Stratoscale is revolutionizing the data center with a zero-to-cloud-in-minutes solution. With Stratoscale’s hardware-agnostic, Software Defined Data Center (SDDC) solution to store everything, run anything and scale everywhere...
May. 1, 2016 01:30 PM EDT Reads: 1,621
SYS-CON Events announced today that Men & Mice, the leading global provider of DNS, DHCP and IP address management overlay solutions, will exhibit at 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. The Men & Mice Suite overlay solution is already known for its powerful application in heterogeneous operating environments, enabling enterprises to scale without fuss. Building on a solid range of diverse platform support,...
May. 1, 2016 12:15 PM EDT Reads: 2,376
This is not a small hotel event. It is also not a big vendor party where politicians and entertainers are more important than real content. This is Cloud Expo, the world's longest-running conference and exhibition focused on Cloud Computing and all that it entails. If you want serious presentations and valuable insight about Cloud Computing for three straight days, then register now for Cloud Expo.
Apr. 30, 2016 02:30 PM EDT Reads: 1,785