Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Microservices Expo

Microservices Expo: Article

Best Practices for Transition Planning

Taking control of SOA

Despite the magnitude of a migration to a service-oriented platform, the continuing uncertainty of critical WS-* standards, and the often thundering impact of large-scale SOA deployments, now is the time to start considering the move. The key to a successful transition is to find a spot of calm amidst the storm of activity surrounding SOA, and develop an intuitive plan that will guide your organization through a path of technical obstacles, organizational resistance, and ever-shifting industry trends.

Count yourself lucky if you've had the foresight to coordinate your migration efforts around this type of plan. Many organizations stumble their way into the world of Web services and what they perceive to be SOA. This "inadvertent migration" is often the result of blindly adopting updates to established development tools and following the vendor's lead with regards to how the next generation of applications should be built this time around. The danger of allowing architecture to evolve in this manner is that you never attain a sufficient level of control over the underlying technology. Little or none of your environments become standardized, and new product platforms further entrench layers of proprietary technology.

One of the core benefits of SOA is its ability to unify previously disparate environments. In planning a migration to a standardized adoption of SOA you therefore have an opportunity to erase some of the neglect from the past. Web services and the vendor-neutral communications framework they establish can bridge disparity and unify interoperability on both data representation and messaging levels. SOA fully leverages this framework by introducing standard service design characteristics that foster interoperability between services, solutions, and organizations.

The potential upside is obviously significant, and well worth the battle that lies ahead in achieving this transition. Your best defense against the potential disruptions, costs, and risks that can follow SOA into an organization is the creation of an SOA Transition Plan. This article provides a set of best practices that will assist you in preparing for and developing such a plan.

Define SOA Within Your Own Organization
Surprisingly, one of the greatest obstacles to adopting SOA is a lack of understanding of what actually constitutes a service-oriented architecture. If you were handed a blank piece of paper and asked to write a generic definition of SOA in the next 10 minutes, what would it be? You (and any other decision makers who are part of a migration project) need to be able to clearly describe concepts such as service autonomy, process encapsulation, and service composition, while distinguishing the differences between SOA and traditional distributed architectures. You'll also need to understand how SOA affects business process modeling and introduces a new integration model.

Without a clear vision of what SOA is in the abstract, you will be in no position to contribute to or even assess the merits of a transition plan. This is because the core of the plan will need to consist of a high-level design in which you define how and to what extent SOA will become part of your organization. This definition will then become the ultimate goal of your migration effort, followed by detailed technical designs, organization processes, and strategic decisions that will be determined in support of this goal.

Invest in an Impact Analysis Before Developing the Transition Plan
In order to assess the feasibility of a transition to SOA, you first need to estimate the real-world impact such a migration will have. Therefore, you should consider holding off any sort of planning until an initial impact analysis is complete.

SOA's reach is broad. Hence the scope of this report may exceed what you are accustomed to associating with a traditional impact analysis. Specifically, this type of research effort tends to include in-depth assessments of current and upcoming development tools, infrastructure requirements, skill-set and training requirements, proposed new middleware, changes to organizational processes, changes to security models and policies, and a list of recommendations associated with architecture, custom standards, and project management approaches.

Keep in mind that if you decide to postpone your transition, much of this analysis work may lose its value. While SOA design principles will remain relatively static, a great deal of the underlying technology will continue to evolve and change. Even a delay of one year will require a significant re-analysis. On the other hand, if you do decide to proceed with a transition now, this upfront analysis effort will have already laid the groundwork for your project. (However, if you are planning a long-term migration, re-analysis may still be required, and should be a task scheduled as part of the plan.)

Set the Scope of the Transition
Using the impact analysis results as your primary guide, and factoring in budget constraints, related project requirements, and other external drivers (such as strategic business goals), you should be able to determine the scope of your planned transition. It is not uncommon for an SOA transition plan to apply only to a subset of an organization's technical environment. For instance, there may be several legacy areas of an enterprise that do not warrant any intrusion by service encapsulation. Perhaps your goal is to build a dedicated hosting environment intended only to support new service-oriented applications. More often than not, however, integration requirements drive SOA transitions, in which case the scope of your project could easily see the introduction of SOA affect a majority of your IT enterprise.

Setting the scope of your migration pretty much determines the structure and size of your plan. The scope also dictates a great many parts of your plan's deliverables, including the amount of new technology introduced, the extent to which existing organizational processes are modified, the number of new or revised standards required, and the migration model that is chosen. The use of a migration model, such as the Layered Scope Model, is highly advisable, as it provides you with a customizable template for building project phases around specific migration milestones.

Change the Project Team's Mindset
Service-oriented principles themselves are not complex, however, the application of these principles can result in relatively complex automation solutions. This is especially the case when services from different solutions are shared and composed to support new or modified business processes. If you're going to live in a service-oriented world, your project team will need to change the way it thinks about fundamental aspects of common architecture, such as componentization, integration, and process automation.

One of the more significant revelations team members will be faced with is how much SOA differs from an architecture that uses Web services only peripherally. Even a large-scale deployment of Web services does not necessarily constitute an SOA. This new design paradigm brings with it a set of distinct principles that need to be applied in order for an architecture to be considered truly service-oriented.

There also needs to be a common acceptance of the fact that service-oriented theory is not solely related to the eventual implementation of technology. Concepts, such as process encapsulation and service composition, extend beyond technical environments, and can change the manner in which business processes are structured and modeled. This has significant implications, as the introduction of SOAs can force change beyond the realm of technology, affecting business analysts and existing modeling standards.

Without a sound understanding of these and other changes to how distributed solutions are traditionally designed, you will introduce risks to your project. Foremost of these is the danger of laying a weak foundation built around the use of Web services, but omitting the unique characteristics that define SOA.

Expect Evolution to be Part of the Migration
It may read like a tired line, but investing in SOAs is "building for the future." Whether you need it or not, you will be creating an environment in which interapplication (and even intra-application) communication becomes nonproprietary, and therefore provides the constant potential of open interoperability. You will also be designing solutions consisting of autonomous units of application logic (services) that can be efficiently composed and recomposed to accommodate changes in the business processes they automate.

These, and other SOA characteristics, can lead to significant benefits and an overall superior enterprise. Achieving all of this, however, comes at the price of serious commitment and investment. It also requires that you stay open to the sometimes unpredictable evolutionary nature of SOA. In larger scale transition projects, it is not uncommon for the environment you end up migrating toward to be very different from what you originally defined in your transition plan. Further, it will likely continue to change soon after the migration project finishes. This is the nature of SOA.

And, while WS-* standards continue on their volatile path, products that implement these standards will undergo continuous refinements. This can turn a physical target architecture into a moving target. It is easier to simply accept this ahead of time than to get frustrated at having to continually adapt. The bottom line is that when you document the environment you want to establish upon completion of your migration, realize that what actually gets implemented will likely differ. Then, compensate for this by incorporating a means of facilitating regular change (through iterative design cycles, for example, into your plan.

Use Speculative Analysis to Build Toward a Future State
In order to best leverage the potential of Web services within SOAs, it is often advisable to build an environment capable of providing more than what your immediate requirements ask for. A speculative analysis entails a realistic prediction of how your technical environment will change over the immediate future following the completion of your transition. This analysis is based on current corporate goals and anticipated changes to an organization's business areas. Typically, you won't want to venture out more than 6?12 months with these predictions. What often results is a set of new requirements (commonly integration-related) that can be greatly facilitated by introducing design changes ahead of time.

With this approach you obviously run the danger of wasting time and money on features that end up not getting used. Of course, anything can change and no speculation can be guaranteed. However, if a little more up-front design and development effort can spare the significantly larger amount of effort required to redesign and redevelop solutions (which incurs associated testing and deployment overhead), then it's worth the gamble.

For example, imagine that the results of your analysis indicate a strong likelihood of two systems having to communicate with each other within a year after you introduce SOA to your organization. In this case you are better off taking that potential requirement into account ahead of time. It may not even necessarily require that you build new functionality into your current system; you can often accommodate future state architectures simply by designing increasingly autonomous services with highly generic interfaces, and by positioning these services as future application endpoints.

Prepare for Post-Migration Growth
A common mistake is to limit the scope of a transition plan to the cycle of the migration process. Even if the ultimate goal of your plan is to establish Web services based on service-oriented principles as the primary computing platform within your organization, you still need to take the post-migration growth of this new environment into account ahead of time.

Many organizations focus almost exclusively on the introductory phase of the migration, ignoring what it will take to maintain and expand these environments. This oversight can be costly. For example, IT managers are often shocked when they realize how little of their existing infrastructure can be used to manage large-scale Web services deployments (the second shock generally occurs when the cost of upgrading the administration infrastructure is presented).

The best way to avoid this situation is to speculate on the growth rate of Web services and SOAs within your organization, and to then dedicate part of the up-front analysis to an evaluation of current administration tools. Match up licenses with expected administration requirements, add a contingency for changes in the marketplace and growth variance, and put this figure in your initial budget. Finally, even if the anticipated usage of SOAs is minimal upon completion of the transition, ensure that an extensible support infrastructure is delivered as part of the migration project.

Plan Transition Phases Around the Introduction of Custom Standards
Nothing is more important to realizing the benefits of SOA than creating and enforcing custom standards. SOA promises to establish an environment that is open, adaptive, and fosters interoperability through a common, globally accepted communications platform. A primary benefit of this architecture is its ability to bridge platform and data disparity. Without standardizing this effort, however, the benefits actually realized will be superficial. Nonstandardized SOAs will, in fact, end up contributing to existing disparity.

"Phasing in SOA means phasing in standards." Base your approach on a motto similar to this, and you should see the delivery of standards documents take a prominent place in your migration project. Planning the delivery of standards, however, is only the first step. The enforcement of a standardized SOA will not only introduce changes to technology and the organization as a whole, it will also impose new constraints and limitations. It should therefore be recognized that phasing in SOA and associated custom standards in a controlled manner requires the support and cooperation of the entire IT department.

Though an entirely separate topic, also worth noting is the creation of standards for distributed applications that will not be immediately migrated to SOA. There are a number of steps you can take to build service-oriented characteristics into a solution in preparation for a future migration. Not only will this ease an eventual transition to the Web services platform, it will greatly facilitate any integration with service-oriented applications in the interim.

Other Best Practices
These best practices have focused almost exclusively on the groundwork of your transition plan. Unfortunately that is all I've been able to provide here. Once you actually start authoring the details of your plan, more best practices come into play, such as:

  • Assigning new roles and responsibilities
  • Creating subprojects based on project phases
  • Defining transition architectures
  • Incorporating a service-oriented security model
  • Periodically revisiting original impact analysis results
  • Planning around application endpoints
  • Structuring plans in support of ROIs
Summary
A good transition plan must coordinate the strategic positioning of new concepts and technologies within an organization. With SOA, the execution of the plan achieves an alignment of proprietary technology and open industry standards with an organization's business goals. In other words, you need to seize ownership over how SOA is phased in on corporate, organizational, and technical levels. Approaching migration in this manner minimizes dependencies on external drivers, and places the evolution of this architectural platform in your hands.

More Stories By Thomas Erl

Thomas Erl is a best-selling IT author and founder of Arcitura Education Inc., a global provider of vendor-neutral educational services and certification that encompasses the Cloud Certified Professional (CCP) and SOA Certified Professional (SOACP) programs from CloudSchool.com™ and SOASchool.com® respectively. Thomas has been the world's top-selling service technology author for nearly a decade and is the series editor of the Prentice Hall Service Technology Series from Thomas Erl, as well as the editor of the Service Technology Magazine. With over 175,000 copies in print world-wide, his eight published books have become international bestsellers and have been formally endorsed by senior members of many major IT organizations and academic institutions. To learn more, visit: www.thomaserl.com

Comments (2) View Comments

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.


Most Recent Comments
Simon Li 10/29/04 02:32:33 PM EDT

This is a pretty aggressive approach to migration, but I in today's shifting technology climate it is the only way to go. Traditional migration approaches will fail when applied to such a big technology overhaul. I would like to know more about the other practices he mentiones, especially the one about defining transition architectures. Everything service-oriented right now seems to be hybrid to an extent.

Jeff Windham 10/29/04 02:46:28 AM EDT

Interesting idea to do an impact analysis BEFORE starting the actual transition planning. Using the analysis results as an input to the plan and as a guage of the plan's suitability makes sense especially for larger migrations. The point about the expiry of these documents is also valid and a pretty important consideration considering how much could be invested in platforms that are changing so rapidly.

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
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...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up 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.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, 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.