Microservices Expo Authors: Pat Romanski, Zakia Bouachraoui, Elizabeth White, Liz McMillan, Yeshim Deniz

Related Topics: Microservices Expo

Microservices Expo: Article

The Keys to Successful SOAs

Aligning business and technology to achieve enterprise goals

Today most of the conversations surrounding service-oriented architectures (SOAs) focus on flexibility and breaking down applications into services: modular, reusable, componentized, with increased availability to the services as well as increased management of them. However, with these conversations comes the risk of getting sucked into a technology-centric vacuum in which consideration for the real business problems that customers need to solve might be neglected.

Undoubtedly there is a huge demand for the development and implementation of SOAs. Gartner predicts that by 2008 more than 60 percent of organizations will use SOA as a "guiding principal" when creating essential applications and processes. With this in mind, and as the spotlight on SOA grows ever brighter throughout the industry, companies in all sectors are posing the question, "What are the key things we need for successful SOAs?"

Before embarking on building an SOA, business and IT executives need to sit down and determine what business problems need to be solved. These are clearly going to vary by industry. For example, Telco and wireless service providers worry about customer turnover. Pharmaceuticals stay up at night trying to get new, life-saving drugs to market faster. Hospitals want to ensure that up-to-date patient records are available to doctors when needed during emergencies.

Solving real business problems using the flexibility afforded by an SOA is critical to helping customers transform to on-demand businesses that can quickly respond to rapidly changing market environments. An SOA can help companies do this by providing an industry-standard framework that is interchangeable, adaptive, and flexible, but most important, is closely linked to the business goals.

Business leaders who are not aware of the benefits an SOA can provide will likely lose a competitive edge in the marketplace as more nimble competitors take advantage of this new enabling technology. The business value that SOAs provide is so great that organizations are set to spend billions of dollars annually in just a couple of years on software and services to achieve these benefits.

Working through the steps of identifying a specific business problem, determining an approach to solve it, realizing ROI, and then moving on to the next business problem is a method that customers understand and prefer when purchasing technology and services. This approach is forcing the strategy to shift away from the practice of customers simply purchasing middleware, a database, management tools, or even general services from a single vendor, to customers demanding solutions based on IT components with the right combination of technology and services to solve specific business problems. Vendors that can't adapt to this new culture will have problems. They must improve themselves to sell large quantities of components and assets that fit into a defined ecosystem - based on industry standards - and scale these components to address additional business problems.

Customers need to approach building an SOA based on the needs of the business. A company, or more specifically an IT department, can't guess what new technology (such as Web services) will add the greatest value, so a detailed identification and prioritization of the services a business needs to develop or expose in order to support improved business processes must be developed. Once a business has determined its priorities and those priorities are understood and shared by the company's business and IT leaders, the next step is to agree upon a systematic approach that will help them build a roadmap for implementing an SOA. In order to migrate to an SOA that will generate the greatest results in the most efficient manner, there are certain questions that must be addressed. In a recent paper, Ali Arsanjani, PhD and IBM's chief architect for IBM's SOA and Web Services Center of Excellence, outlined the following points for best practices in migrating to SOA.

  • Adoption and maturity models. Where is your company at in the relative scale of maturity in the adoption of SOA and Web services? Every different level of adoption has unique needs.
  • Assessments. Have pilots been conducted? Have you dabbled into Web services? How good is the resulting architecture? Should you keep going in the same direction? Will this scale to an enterprise SOA? Have you considered everything you need to consider?
  • Strategy and planning activities. How do you plan to migrate to an SOA? What are the steps, tools, methods, technologies, standards, and training needed? What is the roadmap and vision, and how do you get there? What's the plan?
  • Governance. Should existing API or capability become a service? If not, which ones are eligible? Every service should be created with the intent to bring value to the business in some way. How is this process managed without obstructing business goals?
  • Implementation of best practices. What are some tried and tested ways of implementing security, ensuring performance, complying with standards for interoperability, and designing for change?
Once these questions have been addressed, the first phase of the SOA roadmap should be materializing. However, this is also the time when the architecture itself will need to be mapped out and a template for the architecture will need to be created, and design and architecture decisions will need to be determined for each of the following seven layers.

Layer 1: Operational systems layer. This consists of existing custom-built applications, otherwise called legacy systems, including existing CRM and ERP packaged applications, and older object-oriented system implementations, as well as business intelligence applications. The composite layered architecture of an SOA can reuse existing systems and integrate them using service-oriented integration techniques.

Layer 2: Enterprise components layer. This is the layer of enterprise components that is responsible for realizing functionality and maintaining the quality of service of the exposed services. These special components are a managed, governed set of enterprise assets that are funded at the organization or the business unit level. As enterprise-scale assets, they are responsible for ensuring conformance to SLAs through the application of architectural best practices. This layer typically uses container-based technologies such as application servers to implement the components, workload management, high-availability, and load balancing.

Layer 3: Services layer. The services the business chooses to fund and expose reside in this layer. They can be discovered or they can be statically bound and then invoked, or possibly, choreographed into a composite service. This service exposure layer also provides for the mechanism to take enterprise scale components, business unit specific components, and in some cases, project-specific components, and externalizes a subset of their interfaces in the form of service descriptions. Thus, the enterprise components provide service realization at runtime using the functionality provided by their interfaces. The interfaces get exported out as service descriptions in this layer, where they are exposed for use. They can exist in isolation or as a composite service.

Level 4: Business process composition or choreography layer. Compositions and choreographies of services exposed in Layer 3 are defined in this layer. Services are bundled into a flow through orchestration or choreography, and thus act together as a single application. These applications support specific use cases and business processes. Here, visual flow composition tools can be used for the design of application flow.

Layer 5: Access or presentation layer. Although this layer is usually out of scope for discussions around an SOA, it is gradually becoming more relevant. I depict it here because there is an increasing convergence of standards, such as Web services, for Remote Portlets Version 2.0 and other technologies, that seek to use Web services at the application interface or presentation level. You can think of it as a future layer that you need to take into account for future solutions. It is also important to note that SOA decouples the user interface from the components, and that you ultimately need to provide a complete solution from an access channel to a service or composition of services.

Level 6: Integration (ESB). This layer enables the integration of services through the introduction of a reliable set of capabilities, such as intelligent routing, protocol mediation, and other transformation mechanisms, and is often described as the ESB. Web Services Description Language (WSDL) specifies a binding, which implies a location where the service is provided. On the other hand, an ESB provides a location-independent mechanism for integration.

More Stories By Michael Liebow

Michael Liebow is a seasoned leader who brings more than 25 years of sales, marketing and management experience to Dexterra. Most recently, he served as a vice president in IBM Global Business Services, a $20 billion division, where he was responsible for creating a new portfolio of composite business solutions. In addition to his career at IBM, Michael has held a variety of senior management positions across a diverse range of industries, including high-technology, consumer package goods, communications, media and entertainment. With a strong entrepreneurial focus and technical vision, Michael has a proven success record in building organizations that uniquely address the needs of global markets and industries.

Comments (0)

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.

Microservices Articles
Lori MacVittie is a subject matter expert on emerging technology responsible for outbound evangelism across F5's entire product suite. MacVittie has extensive development and technical architecture experience in both high-tech and enterprise organizations, in addition to network and systems administration expertise. Prior to joining F5, MacVittie was an award-winning technology editor at Network Computing Magazine where she evaluated and tested application-focused technologies including app secu...
When building large, cloud-based applications that operate at a high scale, it’s important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. “Fly two mistakes high” is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee A...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Using new techniques of information modeling, indexing, and processing, new cloud-based systems can support cloud-based workloads previously not possible for high-throughput insurance, banking, and case-based applications. In his session at 18th Cloud Expo, John Newton, CTO, Founder and Chairman of Alfresco, described how to scale cloud-based content management repositories to store, manage, and retrieve billions of documents and related information with fast and linear scalability. He addresse...
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
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.
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...