|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.
Cloud Expo, Inc. has announced today that Andi Mann returns to 'DevOps at Cloud Expo 2016' as Conference Chair The @DevOpsSummit at Cloud Expo will take place on November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. "DevOps is set to be one of the most profound disruptions to hit IT in decades," said Andi Mann. "It is a natural extension of cloud computing, and I have seen both firsthand and in independent research the fantastic results DevOps delivers. So I am excited t...
Jun. 29, 2016 03:15 PM EDT Reads: 219
When people aren’t talking about VMs and containers, they’re talking about serverless architecture. Serverless is about no maintenance. It means you are not worried about low-level infrastructural and operational details. An event-driven serverless platform is a great use case for IoT. In his session at @ThingsExpo, Animesh Singh, an STSM and Lead for IBM Cloud Platform and Infrastructure, will detail how to build a distributed serverless, polyglot, microservices framework using open source tec...
Jun. 29, 2016 12:30 PM EDT Reads: 533
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes ho...
Jun. 29, 2016 08:45 AM EDT Reads: 1,107
Gartner is now treating algorithms like they are some kind of innovative addition to the modern digital discussion. Presumably the brilliant minds there have some novel insight into algorithms and, yes, the Algorithm Economy that CIOs should sit up and take notice of. Not only are algorithms nothing new, but much of what Gartner is saying about them is obvious. The bigger picture here is that software continues to improve, and enterprises are becoming increasingly software-driven, in part bec...
Jun. 17, 2016 04:07 PM EDT Reads: 841
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound...
Jun. 12, 2016 09:00 PM EDT Reads: 5,230
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data...
Jun. 12, 2016 02:45 AM EDT Reads: 3,785
NHK, Japan Broadcasting, will feature the upcoming @ThingsExpo Silicon Valley in a special 'Internet of Things' and smart technology documentary that will be filmed on the expo floor between November 3 to 5, 2015, in Santa Clara. NHK is the sole public TV network in Japan equivalent to the BBC in the UK and the largest in Asia with many award-winning science and technology programs. Japanese TV is producing a documentary about IoT and Smart technology and will be covering @ThingsExpo Silicon Val...
Jun. 8, 2016 10:30 PM EDT Reads: 4,657
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,...
Jun. 8, 2016 06:45 PM EDT Reads: 4,188
Internet of @ThingsExpo, 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 and ThingsExpo New York Call for Papers is now open.
Jun. 8, 2016 03:45 PM EDT Reads: 3,322
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed...
Jun. 8, 2016 03:00 PM EDT Reads: 3,305
@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.
Jun. 8, 2016 01:00 PM EDT Reads: 4,479
Cloud Expo, Inc. has announced today that Andi Mann returns to 'DevOps at Cloud Expo 2016' as Conference Chair The @DevOpsSummit at Cloud Expo will take place on June 7-9, 2016, at the Javits Center in New York City, New York. "DevOps is set to be one of the most profound disruptions to hit IT in decades," said Andi Mann. "It is a natural extension of cloud computing, and I have seen both firsthand and in independent research the fantastic results DevOps delivers. So I am excited to help the g...
Jun. 8, 2016 11:00 AM EDT Reads: 3,756
Korean Broadcasting System (KBS) will feature the upcoming 18th Cloud Expo | @ThingsExpo in a New York news documentary about the "New IT for the Future." The documentary will cover how big companies are transmitting or adopting the new IT for the future and will be filmed on the expo floor between June 7-June 9, 2016, at the Javits Center in New York City, New York. KBS has long been a leader in the development of the broadcasting culture of Korea. As the key public service broadcaster of Korea...
Jun. 8, 2016 10:00 AM EDT Reads: 2,647
SYS-CON Events announced today that Addteq will exhibit at SYS-CON's @DevOpsSummit at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Addteq is one of the top 10 Platinum Atlassian Experts who specialize in DevOps, custom and continuous integration, automation, plugin development, and consulting for midsize and global firms. Addteq firmly believes that automation is essential for successful software releases. Addteq centers its products a...
Jun. 8, 2016 09:45 AM EDT Reads: 2,614
In the rush to compete in the digital age, a successful digital transformation is essential, but many organizations are setting themselves up for failure. There’s a common misconception that the process is just about technology, but it’s not. It’s about your business. It shouldn’t be treated as an isolated IT project; it should be driven by business needs with the committed involvement of a range of stakeholders.
Jun. 8, 2016 02:15 AM EDT Reads: 3,682
SYS-CON Events announced today that FalconStor Software® Inc., a 15-year innovator of software-defined storage 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. FalconStor Software®, Inc. (NASDAQ: FALC) is a leading software-defined storage company offering a converged, hardware-agnostic, software-defined storage and data services platform. Its flagship solution FreeStor®, utilizes a horizonta...
Jun. 7, 2016 07:00 PM EDT Reads: 4,295
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York and Silicon Valley. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place Nov 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 17th Cloud Expo and will feature technical sessions from a rock star conference faculty ...
Jun. 7, 2016 04:30 PM EDT Reads: 6,022
SYS-CON Events announced today that Column Technologies will exhibit at SYS-CON's @DevOpsSummit at Cloud Expo, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Established in 1998, Column Technologies is a global technology solutions provider with over 400 employees, headquartered in the United States with offices in Canada, India, and the United Kingdom. Column Technologies provides “Best of Breed” technology solutions that automate the key DevOps principal...
Jun. 7, 2016 04:15 PM EDT Reads: 3,429
SYS-CON Events announced today that SoftLayer, an IBM Company, has been named “Gold Sponsor” of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2016, at the Javits Center in New York, New York. SoftLayer, an IBM Company, provides cloud infrastructure as a service from a growing number of data centers and network points of presence around the world. SoftLayer’s customers range from Web startups to global enterprises.
Jun. 7, 2016 01:00 PM EDT Reads: 2,848
SYS-CON Events announced today that IBM Cloud Data Services has been named “Bronze Sponsor” of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. IBM Cloud Data Services offers a portfolio of integrated, best-of-breed cloud data services for developers focused on mobile computing and analytics use cases.
Jun. 7, 2016 12:30 PM EDT Reads: 2,851