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

Related Topics: Microservices Expo

Microservices Expo: Article

Learning from SOA Mistakes

A guide to SOA anti-patterns - how to benefit from known unworkable solutions

Capturing the Experience
So that all enterprises can benefit from the experience of early adopters of SOA, it's important that companies deploying SOA, companies providing SOA solutions, and companies providing tools communicate with each other. Participation in industry bodies and consortia can be an excellent way of doing that. Outside the commercial arena, free of the pressure to pick a product or make a sale, people can exchange ideas and discuss approaches to realizing SOA.

The Open Group is a vendor-neutral consortium whose vision is boundary-less information flow in and between organizations. It sees SOA as the prime architectural approach by which enterprises can realize that vision. Its SOA Working Group exists to develop and foster common understanding of SOA to facilitate alignment between the business and information technology communities. It does this by conducting a work program to produce definitions, analyses, recommendations, reference models, and standards to assist business and information technology professionals in and outside the Open Group to understand and adopt SOA. Participation in forums such as this helps people learn from others and capture common experience for the benefit of the wider community.

It's particularly important that anti-patterns are identified and described, and catalogued in a structured way. In the SOA Advanced Technology team at IBM, for example, an effort is under way to identify SOA anti-patterns from experiences with SOA customer engagements. The goals of this effort are, in addition to identifying the anti-patterns, to catalogue them for future reference, and to develop educational material on anti-patterns. And the practice of detecting anti-patterns at all stages of the SOA solution lifecycle is being enforced too.

SOA use is growing explosively. But when an enterprise uses any new approach, mistakes are likely, and SOA is no exception to this rule. For this reason, it's vital that the experience of the first adopters of SOA is captured for the benefit of all enterprises. Identification and documentation of anti-patterns - attractive apparent solutions that are known not to work - will help enterprises avoid mistakes and successfully implement SOA.

We hope that we have provided some useful thoughts on how to avoid known mistakes in a SOA project. Some of the most important lessons are:

  • Be sure to include skills development in your plan.
  • Plan for incremental releases, building on one another and testing as you go.
  • Web Services are an important technology but, by themselves, they aren't SOA. SOA is an architectural approach first and foremost!
  • Don't get trapped into thinking more services is a better solution. Having the right services is the better solution. Avoid anti-patterns like chatty services.
  • Adding point-to-point connections doesn't help; look to the Enterprise Service Bus pattern as way to simplify your architecture.
These aren't the only lessons. There are many anti-patterns to avoid. We are continuing to do research in this area and plan to publish further articles on the topic and encourage you, the practitioners, to join in this work, and get involved with other people and organizations working on SOA.

Where To Learn More
The Open Group SOA Working Group provides a very active forum for staying abreast of recent SOA developments. The group intends its work to be highly accessible to participants at all levels. You can find out more about the Open Group SOA Working group at www.opengroup.org/projects/soa/.

Besides the SOA Working Group, there are many sources for pattern and anti-pattern information. Below we list some we believe will be particularly useful.

1.  Jonathan Adams, Srinivas Koushik, Guru Vasudeva, and George Galambos. Patterns for e-Business: A Strategy for Reuse. MC Press. 2001.

2.  D. Alur, J. Crupi, and D. Malks. Core J2EE Patterns: Best Practices and Design Strategies. Prentice Hall/Sun Microsystems Press. ISBN: 0130648841.

3.  B. Dudney, S. Asbury, J. Krozak, and K. Wittkopf. J2EE Anti-Patterns. Wiley Publications. ISBN: 0471146153.

4.  E. Gamma, R. Helm, R. Johnson, and J. Vlissides. Design Patterns: Elements of Reusable Object-Oriented Software. Reading, Addison-Wesley. 1995.

5.  D. Hovemeyer and W. Pugh. "Finding Bugs is Easy."

6.  D. Reimer, E. Schonberg, K. Srinivas, H. Srinivasan, B. Alpern, R. D. Johnson, A. Kershenbaum, and L. Koved. SABER: Smart Analysis Based Error Reduction. In ISSTA. 2004.

7.  William J. Brown, Raphael C. Malveau, Hays W. "Skip" McCormick, and Thomas J. Mowbray. Anti-Patterns: Refactoring Software, Architectures, and Projects in Crisis. Paperback. March 20, 1998)

8.  Norbert Bieberstein, Sanjay Bose, Marc Fiammante, Keith Jones, and Rawn Shah. Service-Oriented Architecture (SOA) Compass: Business Value, Planning, and Enterprise Roadmap. Developerworks. Hardcover. IBM Press

9.  Olaf Zimmermann, Mark R. Tomlinson, and Stefan Peuser. Perspectives on Web Services: Applying SOAP, WSDL, and UDDI to Real-World Projects. Springer Professional Computing. Hardcover. ISBN: 3540009140.

10.  Steve Jones. "SOA Anti-Patterns." CGI: http://www.infoq.com/articles/SOA-anti-patterns. Also check out Steve's blog @ http://service-architecture.blogspot.com/ Search for "anti-patterns" or "patterns."

11.  Ali Asranjani, Service-oriented modeling and architecture, How to identify, specify, and realize services for your SOA. IBM Developerworks. November 2004.

12.  SOA Survey article, www.govtech.net/magazine/channel_story.php/100246

13.  "Growth in SOA and Web Services Implementation." SDA Asia. July 25, 2006.

14. Jenny Ang, Luba Cherbakov, and Dr. Mamdouh Ibrahim. “SOA Antipatterns - The obstacles to the adoption and successful realization of service-oriented architecture.” 18 Nov 2005. IBM Developerworks: http://www-128.ibm.com/developerworks/webservices/library/ws-antipatterns/

More Stories By Tony Carrato

Tony Carrato is the worldwide chief operations architect for the SOA Advanced Technology team in IBM's Software Group, focusing on SOA delivery. In this role, he is responsible for a team of IT architects who help IBM clients define and implement SOA projects around the world. Tony has over 30 years of IT experience, concentrating in financial services and telecommunications. He has held a variety of senior technical positions in Australia, Hong Kong, and the U.S.

More Stories By Harini Srinivasan

Dr. Harini Srinivasan is on the SOA design requirements team at IBM Software Group – a team that works with customers and IBM architects to capture SOA specific requirements and articulate them to relevant IBM SOA technology groups including the SOA product divisions. Before joining the SOA design requirements team, she spent 10 years at IBM Research as a Research Staff Member and has worked on customer-focused research topics such as performance analysis tools, JVM runtimes (including instrumentation) and C++ object models. . Her background is program analysis (static and dynamic analysis for performance and debugging), parallel and distributed systems including compiling explicitly parallel programs and runtimes for Java and C++.

More Stories By Chris Harding

Dr. Chris Harding leads the SOA Working Group at The Open Group - an open forum of customers and suppliers of IT products and services. In addition, he is a director of the UDEF Forum and manages The Open Group?s work on semantic interoperability. He has been with The Open Group for over 10 years. Dr. Harding began his career in communications software research and development. He then spent nine years as a consultant, specializing in voice and data communications, before moving to his current role. Recognizing the importance of giving enterprises quality information at the point of use, he sees information interoperability as the next major challenge, and frequently speaks or writes on this topic. Dr. Harding has a PhD in mathematical logic, and is a member of the British Computer Society (BCS) and of the Institute of Electrical and Electronics Engineers (IEEE).

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
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.