Welcome!

Microservices Expo Authors: Stackify Blog, Automic Blog, Simon Hill, Pat Romanski, Liz McMillan

Related Topics: Microservices Expo

Microservices Expo: Article

SOA Adoption Models

Ad hoc versus program-based

SOA Adoption Models
We have encountered various approaches that enterprises are taking for migrating to and adopting SOA for their enterprises. We list the following models in this article that we have come across consistently: ad hoc and program-based (organic and strategic) models.

The Ad Hoc SOA Adoption Model
Ad hoc SOA adoption is the project-level adoption of service-oriented technologies on a specific need or tactical basis. There is no central coordination or plan. The results of this adoption model are:
• Each project or initiative benefits the technical advantages of new services at an individual level.
• The technologies are applied inconsistently, which allows for proliferation of bad SOA practices, such as the development of non-standard Web Services, hidden pockets of cost in one-off maintenance, low-level of service reuse, increase in point-to-point Web Services connectivity, etc
• Enterprise reuse can't be achieved and can therefore yield redundant development efforts.
• Increased IT complexity, resulting in reduced agility for responding to business demands
• Potentially resulting in worse condition than the previous status quo.

It's clear that businesses need to invest in a strategy for SOA adoption that will address business drivers, improve existing IT challenges, and avoid the negative impact of unplanned ad hoc SOA adoption. Depending on the organization's goals and level of investment, SOA adoption can be planned in accordance with an overall program.

The Program-based SOA Adoption Model
Program-based SOA adoption allows SOA evolution to be controlled according to an overarching enterprise strategy and goals. This model provides a holistic view and addresses the enterprise from organizational, process, and technology dimensions over time. A planned and directed SOA adoption strategy eliminates the risk of propagating SOA bad practices that will worsen the IT situation. Some key characteristics of a program-based approach are:
• Creates processes and guidelines that support desirable, consistent, predictable, and measurable outcomes for SOA adoption.
• Provides active service portfolio management, including ongoing SOA opportunity identification.
• Promotes SOA best practices and enhances one's ability to adopt new technology paradigm consistently across the enterprise as well as increase SOA ROI
• Provides an opportunity for changes to the organization and processes as learning can be applied to further strengthen the SOA ROI.

We'll consider two program-based SOA adoption models: organic and strategic. Both provide planned and controlled adoption behaviors. The difference in these models is how they are initiated and the pace of adoption. (See Sidebar)

The Program-based Organic SOA Adoption Model
Organic SOA adoption model requires low investment. It allows:
• Quick understanding and alignment of key business drivers with SOA objectives
• Execution of a prioritized project using SOA principles
• Development of core (base line) processes
• Building foundation technologies that can be used for successive SOA projects.

In an organic adoption model of SOA, one builds a business case from the findings of the initial project. Base line standards, best practices, processes, and organization structure are created and then evolved. The initial project rarely provides a positive ROI due to the cost associated with additional planning and the SOA infrastructure build-out. However, the organic model shows that incremental benefits will be achieved through SOA on successive projects. SOA does not require a full enterprise implementation to begin to realize value. Investments in the infrastructure can be aligned on a project basis to reduce risk. The value can be realized earlier without a comprehensive SOA strategy.

Figure 1 shows the typical progression of the organic SOA adoption model. The initial project is chosen opportunistically from existing planned projects according to agreed upon criteria. The project is executed with the original scope in mind and a specific business problem is solved. SOA artifacts and processes used on the project are then harvested. Incremental SOA costs are absorbed by the initial project and are recouped by the business in subsequent SOA projects.

The Program-based Strategic SOA Adoption Model
As an alternative to the organic approach, the strategic SOA adoption model is characterized by an initial strategy project to build an enterprise business case for SOA, define a future state, and plan a roadmap for implementation. The future state incorporates not only the technology transformation required to move towards SOA, but also the organizational and process changes as well. (Figure 2)

Organizations adopting SOA through a strategic model build out a supporting infrastructure for enterprise SOA with a reference implementation that demonstrates the recommended use of standards and best practices.

The roadmap of strategic SOA is based on a comprehensive assessment of the enterprise and defines SOA projects over a three- to five-year timeframe. It takes into account all the dimensions of an enterprise: people, processes, and technology (see Figure 3). NOTE: We need to redraw this visual differently. It was done for PMUSA with ToPCoder).

SOA Adoption Recommendations
While there are clear tradeoffs between the organic and strategic SOA adoption models, there are four key adoption recommendations for any successful program-based SOA. They are:
• Align SOA objectives with business drivers
• Selectively determine SOA adopters
• Identify and address organizational barriers to adoption
• Define and measure success

Align SOA objectives with business drivers
Since SOA is a set of best practices and related standards that can be applied uniquely on each implementation, implementation can produce a variety of benefits. There's a risk of misfiring or misinterpretation when SOA objectives aren't clearly aligned with business drivers. To be effective, SOA implementation objectives have to be in alignment with the enterprise imperatives for both organic and strategic adoption. In both organic and strategic SOA adoption, SOA objectives need to be documented that can:
• Support the business case for SOA
• Align the architecture with the needs of the business
• Act as a reference for developing a future-state reference architecture
• Prioritize the approach for potential projects and a SOA roadmap

SOA strategy should begin by understanding the enterprise imperatives - a successful business plan takes the external environment, business and IT strategy, and current and planned projects into account. SOA objectives are best identified collaboratively in a workshop environment with key SOA stakeholders from business and IT leaders along with user communities. With enterprise imperatives identified, SOA objectives can be well articulated and prioritized across functional units of the value chain.

Earlier we showed you typical business drivers for SOA (Table 1). SOA objectives for the enterprise can be an extension of these kinds of drivers prioritized and aligned with the enterprise imperatives. For example, the first business driver - lower cost of IT - simplify the IT infrastructure - can be the basis of a SOA objective and can be extended to state - lower cost of IT - simplify the IT infrastructure by reducing the data redundancies across customer-oriented systems. An SOA objective should relate to a particular business strategy, but not prescribe an implementation approach.


More Stories By Alkesh Shah

Alkesh Shah is a director at Keane Architecture Services.

More Stories By Paul Kalin

Paul Kalin is senior principal enterprise architect at Keane Architecture Services.

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.


@MicroservicesExpo Stories
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
Digital transformation has changed the way users interact with the world, and the traditional healthcare experience no longer meets rising consumer expectations. Enterprise Health Clouds (EHCs) are designed to easily and securely deliver the smart and engaging digital health experience that patients expect today, while ensuring the compliance and data integration that care providers require. Jikku Venkat
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
DevOps promotes continuous improvement through a culture of collaboration. But in real terms, how do you: Integrate activities across diverse teams and services? Make objective decisions with system-wide visibility? Use feedback loops to enable learning and improvement? With technology insights and real-world examples, in his general session at @DevOpsSummit, at 21st Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, explored how leading organizations use data-driven DevOps to close th...
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
"We are an integrator of carrier ethernet and bandwidth to get people to connect to the cloud, to the SaaS providers, and the IaaS providers all on ethernet," explained Paul Mako, CEO & CTO of Massive Networks, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
From our perspective as consumers, perhaps the best thing about digital transformation is how consumerization is making technology so much easier to use. Sure, our television remote controls still have too many buttons, and I have yet to figure out the digital display in my Honda, but all in all, tech is getting easier for everybody. Within companies – even very large ones – the consumerization of technology is gradually taking hold as well. There are now simple mobile apps for a wide range of ...