Recent discussions with government ICT leadership related to cloud computing strategies have all brought the concept of Enterprise Service Bus as a Service into the conversation.
Now ESBs are not entirely new, but in the context of governments they make a lot of sense. In the context of cloud computing strategies in governments they make a heck of a lot of sense.
Wikipedia defines an ESB as:
In computing, an enterprise service bus (ESB) is a software architecture construct which provides fundamental services for complex architectures via an event-driven and standards-based messaging engine (the bus). Developers typically implement an ESB using technologies found in a category of middleware infrastructure products, usually based on recognized standards.
Now if you actually understand that – then you are no doubt a software developer. For the rest of us, this means that with the ESB pattern, participants engaging in service interaction communicate through a services or application “bus.” This bus could be a database, virtual desktop environment, billing/payments system, email, or other services common to one or more agencies. The ESB is designed to handle relationships between users with a common services and standardized data format.
New services can be plugged into the bus and integrated with existing services without any changes to the core bus service. Cloud users and applications developers will simply add or modify the integration logic.
Participants in a cross-organizational service interaction are connected to the Cloud ESB, rather than directly to one another, including: government-to-government, citizen-to-government, and business-to-government. Rules-based administration support will make it easier to manage ESB deployments through a simplified template allowing a better user experience for solution administrators.
The Benefits to Government Clouds
In addition to fully supporting a logical service-oriented architecture (SOA), the ESBaaS will enhance or provide:
- Open and published solutions for managing Web services connectivity, interactions, services hosting, and services mediation environment
- From development and maintenance perspective, the Government Cloud ESB allows agencies and users to securely and reliably share information between applications in a logical, cost effective manner
- Government Cloud ESBs will simplify adding new services, or changing existing services, with minimal impact to the bus or other interfacing applications within the IT environment
- Improvements in system performance and availability by offloading message processing and isolating complex mediation tasks in a dedicated ESB integration server
Again, possibly a mouthful, but if you can grasp the idea of a common bus providing services to a lot of different applications or agencies, allowing sharing of data and and interfaces without complex relationships between each participating agency, then the value becomes much more clear.
Why the Government Cloud?
While there are many parallels to large companies, governments are unique in the number of separate ministries, agencies, departments, and organizations within the framework of government. Governments normally share a tremendous amount of in the past this data between each agency, and in the past this was extremely difficult due to organizational differences, lack of IT support, or individuals who simply did not want to share data with other agencies.
The result of course was many agencies built their own stand alone data systems, without central coordination, resulting in a lot of duplicate data items (such as an individual’s personal profile and information, business information, and land management information, and other similar data). Most often, there were small differences in the data elements each agency developed and maintained, resulting in either corrupt or conflicting data.
The ESB helps identify a method of connecting applications and users to common data elements, allowing the sharing of both application format and in many cases database data sets. This allows not only efficiency in software/applications development, but also a much higher level of standardization an common data sharing.
While this may be uncomfortable for some agencies, most likely those which do not want to share their data with the central government, or use applications that are standardized with the rest of government, this also does support a very high level of government transparency. A controversial, but essential goal of all developing (and developed) governments.
As governments continue to focus on data center consolidation and the great economical, environmental, and enabling qualities of virtualization and on-demand compute resources, integration of the ESBaaS makes a lot of sense.
There are some very nice articles related to ESBs on the net, including:
- Progress Software – ESB Architecture and Lifecycle Definition
- The Enterprise Service Bus- Making Web Services Safe for Application Integration
- Driving the Enterprise Service Bus
- Best of Breed ESBs
Which may help you better understand the concept, or give some additional ideas.
Let us know your opinion or ideas on ESBaaS
Organizations see the benefits of cloud computing, however many are simply mortified at the prospect of re-engineering their operations to fit into existing cloud service technology or architectures. So how can we make the first step?
We (at Pacific-Tier Communications) have conducted 103 surveys over the past few months in the US, Canada, Indonesia, and Moldova on the topic of cloud computing. The surveys targeted both IT managers in commercial companies, as well as within government organizations.
The survey results were really no different than most – IT managers in general find cloud computing and virtualization an exciting technology and service development, but they are reluctant to jump into cloud for a variety of reas0ns, including:
- Organization is not ready (including internal politics)
- No specific budget
- Applications not prepared for migration to cloud
- and lots of other reasons
The list and reasoning for not going into cloud will continue until organizations get to the point they cannot avoid the topic, probably around the time of a major technology refresh.
Disaster Recovery is Different
The surveys also indi9cated another consistent trend – most organizations still have no formal disasters recovery plan. This is particularly common within government agencies, including those state and local governments surveyed in the United States.
IT managers in many government agencies had critical data stored on laptop computers, desktops, or in most cases their organization operating data in a server closet with either no backup, or onsite backup to a tape system with no offsite storage.
In addition, the central or controlling government/commercial IT organization had either no specific policy for backing up data, or in a worst case had no means of backing up data (central or common storage system) available to individual branch or agency users.
When asked if cloud storage, or even dedicated storage became available with reasonable technical ease, and affordable cost, the IT managers agreed, most enthusiastically, that they would support development of automated backup and individual workstation backup to prevent data loss and reinforce availability of applications.
Private or Public – Does it Make a Difference?
While most IT managers are still worshiping at the shrine of IT Infrastructure Control, there are cracks appearing in the “Great Walls of IT Infrastructure.” With dwindling IT budgets, and
explosive user and organization IT utility demand, IT managers are slowly realizing the good old days of control are nearly gone.
And to add additional tarnish to pride, the IT managers are also being faced with the probability at least some of their infrastructure will find its way into public cloud services, completely out of their domain.
On the other hand, it is becoming more and more difficult to justify building internal infrastructure when the quality, security, and utility of public services often exceeds that which can be built internally. Of course there are exceptions to every rule, which in our discussion includes requirements for additional security for government sensitive or classified information.
That information could include military, citizen identification data, or other similar information that while securable through encryption and partition management, politically(particularly in cases where the data could possible leave the borders of a country) may not be possible to extend beyond the walls of an internal data center.
For most other information, it is quickly becoming a simple exercise in financial planning to determine whether or not a public storage service or internal storage service makes more sense.
The Intent is Disaster Recovery and Data Backup
Getting back to the point, with nearly all countries, and in particular central government properties, being on or near high capacity telecom carriers and networks, and the cost of bandwidth plummeting, the excuses for not using network-based off-site backups of individual and organization data are becoming rare.
In our surveys and interviews it was clear IT managers fully understood the issue, need, and risk of failure relative to disaster recovery and backup.
Cloud storage, when explained and understood, would help solve the problem. As a first step, and assuming a successful first step, pushing disaster recovery (at least on the level of backups) into cloud storage may be an important move ahead into a longer term move to cloud services.
All managers understood the potential benefits of virtual desktops, SaaS applications, and use of high performance virtualized infrastructure. They did not always like it, but they understood within the next refresh generation of hardware and software technology, cloud computing would have an impact on their organization’s future.
But in the short term, disaster recovery and systems backup into cloud storage is the least traumatic first step ahead.
How about your organization?
Equinix lowers guidance due to higher than expected churn in its data centers and price erosion on higher end customers. Microsoft continues to promote hosted solutions and cloud computing. Companies from Lee Technologies, CirraScale, Dell, HP, and SGI are producing containerized data centers to improve efficiency, cost, and manageability of high density server deployments.
The data center is facing a challenge. The idea of a raised floor, cabinet-based data center is rapidly giving way to virtualization and highly expandable, easy to maintain, container farms.
The impact of cloud computing will be felt across every part of life, not least the data center which faces a degree of automation not yet seen.”
Microsoft CEO Steve Ballmer believes “the transition to the cloud <is> fundamentally changing the nature of data center deployment.” (Data Center Dynamics)
As companies such as Allied Fiber continue to develop visions of high density utility fiber ringing North America, with the added potential of dropping containerized cloud computing infrastructure along fiber routes and power distribution centers, AND the final interconnection of 4G/LTE/XYZ towers and metro cable along the main routes,the potential of creating a true 4th public utility of broadband with processing/storage capacity becomes clear.
Clouds Come of Age
Data center operators such as Equinix have traditionally provided a great product and service for companies wishing to either outsource their web-facing products into a facility with a variety of internet Service Providers or internet Exchange Points providing high performance network access, or eliminate the need for internal data center deployments through outsourcing IT infrastructure into a well-managed, secure, and reliable site.
However the industry is changing. Companies, in particular startup companies. are finding there is no technical or business reason to manage their own servers or infrastructure, and that nearly all applications are becoming available on cloud-based SaaS (Software as a Service) hosted applications.
Whether you are developing your own virtual data center within a PaaS environment, or simply using Google Apps, Microsoft Hosted Office Applications, or other SaaS, the need to own and operate servers is beginning to make little sense. Cloud service providers offer higher performance, flexible on-demand capacity, security, user management, and all the other features we have come to appreciate in the rapidly maturing cloud environment.
With containers providing a flexible physical apparatus to easily expand and distribute cloud infrastructure, as a combined broadband/compute utility, even cloud service providers are finding this a strong alternative to placing their systems within a traditional data center.
With the model of “flowing” cloud infrastructure along the fiber route to meet proximity, disaster recovery, or archival requirements, the container model will become a major threat to the data center industry.
What is the Data Center to Do?
Ballmer:
“A data center should be like a container – that you can put under a roof or a cover to stop it getting wet. Put in a slab of concrete, plumb in a little garden hose to keep it cool, yes a garden hose – it is environmentally friendly, connect to the network and power it up. Think of all the time that takes out of the installation.”
Data center operators need to rethink their concept of the computer room. Building a 150 Megawatt, 2 million square foot facility may not be the best way to approach computing in the future.
Green, low powered, efficient, highly virtualized utility compute capacity makes sense, and will continue to make more sense as cloud computing and dedicated containers continue to evolve. Containers supporting virtualization and cloud computing can certainly be secured, hardened, moved, replaced, and refreshed with much less effort than the “uber-data center.”
It makes sense, will continue to make even more sense, and if I were to make a prediction, will dominate the data delivery industry within 5~10 years. If I were the CEO of a large data center company, I would be doing a lot of homework, with a very high sense of urgency, to get a complete understanding of cloud computing and industry dynamics.
Focus less on selling individual cabinets and electricity, and direct my attention to better understanding cloud computing and the 4th Utility of broadband/compute capacity. I wouldn’t turn out the lights in my carrier hotel or data center quite yet, but this industry will be different in 5 years than it is today.
Given the recent stock volatility in the data center industry, it appears investors are also becoming concerned.
2010 brings great opportunities and challenges to IT organizations in Indonesia. Technology refresh, aggressive development of telecom and Internet infrastructure, with aggressive deployment of “eEverything” is shaking the ICT industry. Even the most steadfast division-level IT managers are beginning to recognize the futility in trying to maintain their own closet “data
center” in a world of virtualization, cloud computing, and drive to increase both data center economics and data security.
Of course there are very good models on the street for data center consolidation, particularly on government levels. In the United States, the National Association of State Chief Information Officers (NASCIO) lists data center consolidation as the second highest priority, immediately after getting better control over managing budget and operational cost.
In March the Australian government announced a (AUD) $1 billion data center consolidation plan, with standardization, solution sharing, and developing opportunities to benefit from “new technology, processes or policy.”
Minister for Finance and Deregulation Lindsay Tanner noted Australia currently has many inefficient data centers, very suitable candidates for consolidation and refresh. The problem of scattered or unstructured data management is “spread across Australia, (with data) located in not just large enterprise data centres, but also in cupboards, converted offices, computer and server rooms, and in commercial and insourced data centers,” said Tanner.
“These are primarily older data centres that are reaching the limits of their electricity supply and floor space. With government demand for data center ICT equipment rising by more than 30 per cent each year, it was clear that we needed to reassess how the government handled its data center activities.”
The UK government also recently published ICT guidance related to data center consolidation, with a plan to cut government operated data center from 130 to around 10~12 facilities. The guidance includes the statement “Over the next three-to-five years, approximately 10-12 highly resilient strategic data centers for the public sector will be established to a high common standard. This will then enable the consolidation of existing public data centers into highly secure and resilient facilities, managed by expert suppliers.”
Indonesia Addresses Data Center Consolidation
Indonesia’s government is in a unique position to take advantage of both introducing new data center and virtualization technology, as well as deploying a consolidated, distributed data center infrastructure that would bring the additional benefit of strong disaster recovery capabilities.
Much like the problems identified by Minister Tanner in Australia, today many Indonesian government organizations – and commercial companies – operate ICT infrastructure without structure or standards. “We cannot add additional services in our data center,” mentioned one IT manager interviewed recently in a data center audit. “If our users need additional applications, we direct them to buy their own server and plug it in under their desk. We don’t have the electricity in our data center to drive new applications and hardware, so our IT organization will now focus only on LAN/WAN connectivity.”
While all IT managers understand disaster recovery planning and business continuity is essential, few have brought DR from PowerPoint to reality, putting much organization data on individual servers, laptops, and desktop computers. All at risk for theft or loss/failure of single disk systems.
That is all changing. Commercial data centers are being built around the country by companies such as PT Indosat, PT Telekom, and other private companies. With the Palapa national fiber ring nearing completion, all main islands within the Indonesian archipelago are connected with diverse fiber optic backbone capacity, and additional international submarine cables are either planned or in progress to Australia, Hong Kong, Singapore, and other communication hubs.
For organizations currently supporting closet data centers, or local servers facing the public Internet for eCommerce or eGovernment applications, data centers such as the Cyber Tower in Jakarta offer both commercial data center space, as well as supporting interconnections for carriers – including the Indonesia Internet Exchange (IIX), in a similar model as One Wilshire, The Westin Building, or 151 Front in Toronto. Ample space for outsourcing data center infrastructure (particularly for companies with Internet-facing applications), as well as power, cooling, and management for internal infrastructure outsourcing.
The challenge, as with most other countries, is to convince ICT managers that it is in their company or organization’s interest to give up the server. Rather than focus their energy on issues such as “control,” “independence (or autonomous operations),” and avoiding the pain of “workforce retraining and reorganization,” ICT managers should consider the benefits outsourcing their physical infrastructure into a data center, and further consider the additional benefits of virtualization and public/enterprise cloud computing.
Companies such as VMWare, AGIT, and Oracle are offering cloud computing consulting and development in Indonesia, and the topic is rapidly gaining momentum in publications and discussions within both the professional IT community, as well as with CFOs and government planning agencies.
It makes sense. As in cloud computing initiatives being driven by the US and other governments, not only consolidating data centers, but also consolidating IT compute resources and storage, makes a lot of sense. Particularly if the government has difficulty standardizing or writing web services to share data. Add a distributed cloud processing model, where two or more data centers with cloud infrastructure are interconnected, and we can now start to drive down recovery time and point objectives close to zero.
Not just for government users, but a company located in Jakarta is able to develop a disaster recovery plan, simply backing up critical data in a remote location, such as IDC Batam (part of the IDC Indonesia group). As an example, the IDC Indonesia group operates 4 data centers located in geographically separate parts of the country, and all are interconnected.
While this does not support all zero recovery time objectives, it does allow companies to lease a cabinet or suite in a commercial data center, and at a minimum install disk systems adequate to meet their critical data restoral needs. It also opens up decent data center collocation space for emerging cloud service and infrastructure providers, all without the burden of legacy systems to refresh.
In a land of volcanoes, typhoons, earthquakes, and man-made disasters Indonesia has a special need for good disaster recovery planning. Through an effort to consolidate organization data centers, the introduction of cloud services in commercial and government markets, and high capacity interconnections between carriers and data centers, the basic elements needed to move forward in Indonesia are now in place.
In the 1990s community of interest networks (COINs) emerged to take advantage of rapidly developing Internet protocol technologies. A small startup named BizNet on London’s Chiswell Street developed an idea to build a secure, closed network to support only companies operating within the securities and financial industries.
BizNet had some reasonable traction in London, with more than 100 individual companies connecting within the secure COIN. Somewhat revolutionary at the time, and it did serve the needs of their target market. Management was also simple, using software from a small company called IPSwitch and their soon to be globally popular “What’s Up” network management and monitoring utility.
However simplicity was the strength of BizNet. While other companies favored strong marketing campaigns and a lot of flash to attract companies to the Internet age, BizNet’s thought leaders (Jez Lloyd and Nick Holland) relied on a strong commitment to service delivery and excellence, and their success became viral within the financial community based on the confidence they built among COIN members.
As networks go, so did BizNet, which was purchased by Level 3 Communications in 1999 and subsequently the COIN network was dismantled in favor of integrating the individual customers into the Level 3 community.
Cloud Communities
Cloud computing supports the idea of a COIN, as companies can not only build their “virtual data center” within a Platform as a Service/PaaS model, but also develop secure virtual interconnections among companies within a business community – not only within the same cloud service provider (CSP), but also among cloud service providers.
In the “BizNet” version of a COIN, dedicated connections (circuits) were needed to connect routers and switches to a central exchange point run by BizNet. BizNet monitored all connections, reinforcing internal operations centers run by individual companies, and added an additional layer of confidence that helped a “viral” growth of their community.
Gerard Briscoe and Alexandros Marinos delivered a paper in 2009 entitled “Digital Ecosystems in the Clouds: Towards Community Cloud Computing.” In addition to discussing the idea of using cloud computing to support an outsourced model of the COIN, the paper also drills deeper into additional areas such as the environmental sustainability of a cloud community.
As each member of the cloud community COIN begins to outsource their virtual data center into the cloud, they are able to begin shutting down inefficient servers while migrating processing requirements into a managed virtual architecture. Even the requirement for managing high performance switching equipment supporting fiber channel and SAN systems is eliminated, with the overall result allowing a significant percentage of costs associated with equipment purchase, software licenses, and support agreements to be rechanneled to customer or business-facing activities.
Perhaps the most compelling potential feature of community clouds is the idea that we can bring processing between business or trading partners within the COIN to near zero, as the interaction between members is on the same system, and will not lose any velocity due to delays induced by going through switching, routing, or short/long distance transmission through the Internet or dedicated circuits.
Standards and a Community Applications Library
Most trading communities and supply chains have a common standard for data representation, process, and interconnection between systems. This may be a system such as RosettaNet for the manufacturing industry, or other similar industry specifications. Within the COIN there should also be a central function that provides the APIs, specifications, and other configurations such as security and web services/interconnection interface specs.
As a function of developing a virtual data center within the PaaS model, standard components supporting the COIN such as firewalls, APIs, and other common applications should be easily accessible for any member, ensuring from the point of implementation that joining the community is a painless experience, and a very rapid method of becoming a full member of the community.
A Marriage of Community GRIDs and Cloud Computing?
Many people are very familiar with project such as Seti At Home, and the World Community GRID. Your desktop computer, servers, or even storage equipment can contribute idle compute and storage capacity to batch jobs supporting everything from searching for extraterrestrial life to AIDS research. You simply register your computer with the target project, download a bit of client software, and the client communicates with a project site to coordinate batch processing of work units/packets.
Now we know our COIN is trying to relieve members from the burden of operating their own data centers – at least those portions of the data center focusing on support of a supply chain or trading community of interest. And some companies are more suited to outsourcing their data center requirements than others. So if we have a mix of companies still operating large data centers with potential sources of unused capacity, and other members in the community cloud with little or no onsite data center capacity, maybe there is a way the community can support itself further by developing the concept of processing capacity as a currency.
As all individual data centers and office LAN/MAN/WANs will have physical connections to the cloud service provider (IaaS provider) through an Internet service provider or dedicated metro Ethernet connection, the virtual data centers being produced within the PaaS portion of the CSP’s will be inherently connectable to any user, or any facility within the COIN. Of course that is accepting that security management will protect non-COIN connected portions of the community.
Virtually, those members of the community with excess capacity within their own networks could then easily further contribute their spare capacity to the community for use as non-time critical compute resource, or for supporting “batch” processing. Some CSPs may even consider buying that capacity to provide members either in the COIN, or outside of the COIN, and additional resource available to their virtual customers as low cost, low performance, batch capacity much like SETI at Home or the Protein Folding Project uses spare capacity on an as-available basis. Much like selling your locally produced energy back into a power GRID.
We Have a New, Blank Cloud White Board to Play With
The BizNet COIN was good. Eleven years after BizNet was dissolved, the concept remains valid, and we now have additional infrastructure that will support COINs through community clouds, with enabling features that extend far beyond the initial vision of BizNet. CSPs such as ScaleUp have built IaaS and PaaS empowerment for COINs within their data center.
Cloud computing is an infant. Well, maybe in Internet years it is rapidly heading to adolescence, but it is still pretty young. Like an adolescent, we know it is powerful, getting more powerful by the day, but few people have the vision to wrap their head around what broadband, cloud computing, diffusion of network-enabled knowledge into the basic education system, and the continuation of Moore’s, Metcalf’s, and other laws of industry and physics.
COINs and community clouds may not have been in the initial discussions of cloud computing, but they are here now. Watching a Slingbox feed in a Jakarta hotel room connected to a television in Burbank was probably not a vision shared by the early adopters of the Internet – and cloud computing will make similar un-thought of leaps in utility and capabilities over the next few years.
However, in the near term, do not be surprised if you see the entire membership of the New York Stock Exchange and NASDAQ operating from a shared cloud COIN. It will work.




