Welcome!

Microservices Expo Authors: Yeshim Deniz, Pat Romanski, Todd Matters, Mark Leake, Stefana Muller

Related Topics: Microservices Expo

Microservices Expo: Article

Service-Oriented Architecture Best Practices

Meeting your goals takes a mixed effort

The concept of a service-oriented architecture is a powerful tool for simplifying enterprise integration. Following the three principles of modularity, encapsulation and loose coupling will achieve some amount of improvement for an individual service. It is insufficient to have a loose set of principles to guide enterprise architecture designs. It is also important to have "best practices" on how to build, run and manage enterprise systems. This document will cover the best practices that have been culled from Epiphany, a number of Epiphany's top customers and leading analyst firms.

Define the language of your enterprise. First and foremost, there must be a common language that your, enterprise must speak. This amounts to being able to define important entities as XML Schemas and transformations as XML style sheets. Enforcement is crucial, as well ensuring interoperability across an enterprise wide system. This is the single most important action an enterprise can take to smooth its transition to an SOA.

In one sense, this principle should not be necessary if industry standards groups could agree on basic XML document formats for simple things like names and addresses. Since this is unlikely to happen anytime soon, it is important that your organization set its own language policies now, and deal with transformation issues via XSLT later.

Establish a naming convention for your enterprise. In a SOA environment, having a document that formulates how to name Web services, service interfaces, legacy system endpoints, or any public component will help the enterprise architects, administrators, and developers provide consistent services.

Define service interfaces first, implement later. In a SOA, the interface for a Web service is more important than its actual implementation. When designing composite applications (i.e. applications composed from a cluster of web services), recognize that heterogeneity is the norm. One analyst study put the average number of hardware/software platforms in the Fortune 500 at 6. This underscores setting a baseline "language" for your organization, as heterogeneity is an unavoidable fact in any large enterprise.

In addition to having best practices around people, practices, and technology, it is also important to have "design patterns" that can be reused in order to make the design and construction of an SOA faster and easier. Just as there are design patterns for object-oriented programming, there is a group of experts who are looking at describing common enterprise workflows as a set of patterns. Led by BEA and the Middleware Company, initial work has been done to catalog a number of enterprise workflows captured as patterns for an SOA. While their efforts are in the early stage, the work appears promising.

Establish a service categorization. Services come in a number of flavors. An organization should decide on its services taxonomy. This definition will help to define development roles, as well as help to suggest a level or organizational structure. At a high level, there are only a few types of services. The Middleware Company group is attempting to pull together a set of best practices for building out a service-oriented architecture. The expert group has defined a taxonomy of services, which is a useful starting place:

  • Component services: Simple atomic services potentially acting on single enterprise resource (e.g., database, code, etc).
  • Data services: Service providing data querying, combination and transformation for multiple data sources.
  • Business services: Atomic services composed of combinations of component services and rules.
  • Workflow services: Long lived business processes coordinating other services with external interactions.
Separate rules. It is important to categorize business logic/rules, further, into "process" type business rules versus "UI" type business rules. Process-type business rules are good candidates to encompass within business services and UI-level business rules should be separated out.

Don't skimp on training. Start with a common skill set. Most organizations are new to the technologies behind SOA (like WS-I, WS-BPEL, etc.), so it is important for an IT staff to acquire the skills to understand and implement SOA on an enterprise-wide scale.

Architect a common management layer. A service-oriented architecture provides both additional opportunity and complexity for managing an operational system. Many of the infrastructure vendors like IBM and BEA provide the ability to monitor and manage Web services. It is important to implement a uniform management infrastructure for managing hardware, operating systems, applications, and Web services for maximum visibility.

Analyst firms have begun to discuss implementation issues around SOA as well. In a recent report, Forrester offers several suggestions for SOA best practices. The Forrester report offers several points for enterprises to consider:

Align services with business processes. This is important for a number of reasons. First, the service must be understood by the business users for it to be useful and successful. Second, the service should match the business process it is managing to mitigate the need to change management. Third, change management will be easier. As business processes change, determining which services need to change will be made easier.

Design decisions need to be made regarding integrating business rules within services. Consumer application-specific business rules may not have to be integrated within the producer services if there is no value in having these rules apply to other consumer applications. This also facilitates easy maintenance of services because there is less coordination with multiple consumer applications

Start with services, do Web services later. Moving to an SOA does not necessarily require Web services. Many companies have been successful building out an SOA message-oriented middleware (MOM). This includes JMS-based software as well as IBM WebSphere MQ (the former MQSeries). Applications rooted in MOM-based systems generally met the requirements of SOA: encapsulation, loose-coupling and modularity, but with the notion of messages on a queue rather than SOAP/XML messages.

Wrap packaged applications in service interfaces. This was mentioned above, but is important enough to restate. Enterprises should be wary of vendors claiming to provide a platform. Leveraging a single vendor's platform will unnecessarily tie an organization to one vendor. This is a risky strategy. It is better for enterprise information assets to speak a neutral, common language that will ensure interoperability.

Have a version resolution architecture. Web services present the ability to reuse software like never before. A Web service can be a public resource used by hundreds of applications. However, if the Web service changes the applications will have to change. This will create a maintenance nightmare. It is important to have an architecture where interfaces have a version associated with them, and a way of resolving a particular interface to a particular version. As Web service producers are changed, the consumers can be migrated slowly to the new service. This way disruption is minimized.

Conclusion
Successful enterprises know that achieving an organization's goals is a mix of best practices around people, policies, and technology. This article has attempted to illustrate that it is not sufficient to adopt SOA technologies. It is important to adopt best practices around how a group is organized and how it behaves. It is also important to adopt a set of policies that ensure smooth, visible operations and minimal effort in the face of change. This article has attempted show some of the current thinking around best practices from Epiphany, Epiphany's customers, and leading analyst firms. The nascent body of SOA best practices is still developing.

Resources

  • Some efforts in this area, like xNAL, are by no means universally accepted. See http://xml.coverpages.org/xnal.html for more details.
  • Gamma, E., et al. (1995). Design Patterns: Elements of Reusable Object-Oriented Softwar. Addison Wesley.
  • SOA Blueprints: www.middlewareresearch.com/soa-blueprints/
  • More Stories By Bill Roth

    Bill Roth is a Silicon Valley veteran with over 20 years in the industry. He has played numerous product marketing, product management and engineering roles at companies like BEA, Sun, Morgan Stanley, and EBay Enterprise. He was recently named one of the World's 30 Most Influential Cloud Bloggers.

    Comments (1) 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
    David Knox 02/10/05 11:05:08 AM EST

    This arcticle starts off right with the three bastions of SOA (standardized interfaces, separation of concerns, loose coupling), after that it falls off the edge. I was most alarmed by the notion that SOA requires 'common language'. The author's argument clearly implies that an enterprise architecture must mandate an all XML protocol. I find it difficult to believe that J2EE app servers shouldn't freely use RMI-IIOP between containers. If every application in the enterprise must have the same transport protocol it contradicts the edict of loose coupling. In the first paragraph the author states a working SOA definition, in the second the author contradicts a necessary aspect of SOA.

    @MicroservicesExpo Stories
    Cloud Expo, Inc. has announced today that Andi Mann and Aruna Ravichandran have been named Co-Chairs of @DevOpsSummit at Cloud Expo Silicon Valley which will take place Oct. 31-Nov. 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. "DevOps is at the intersection of technology and business-optimizing tools, organizations and processes to bring measurable improvements in productivity and profitability," said Aruna Ravichandran, vice president, DevOps product and solutions marketing...
    "When we talk about cloud without compromise what we're talking about is that when people think about 'I need the flexibility of the cloud' - it's the ability to create applications and run them in a cloud environment that's far more flexible,” explained Matthew Finnie, CTO of Interoute, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    For most organizations, the move to hybrid cloud is now a question of when, not if. Fully 82% of enterprises plan to have a hybrid cloud strategy this year, according to Infoholic Research. The worldwide hybrid cloud computing market is expected to grow about 34% annually over the next five years, reaching $241.13 billion by 2022. Companies are embracing hybrid cloud because of the many advantages it offers compared to relying on a single provider for all of their cloud needs. Hybrid offers bala...
    A common misconception about the cloud is that one size fits all. Companies expecting to run all of their operations using one cloud solution or service must realize that doing so is akin to forcing the totality of their business functionality into a straightjacket. Unlocking the full potential of the cloud means embracing the multi-cloud future where businesses use their own cloud, and/or clouds from different vendors, to support separate functions or product groups. There is no single cloud so...
    Containers, microservices and DevOps are all the rage lately. You can read about how great they are and how they’ll change your life and the industry everywhere. So naturally when we started a new company and were deciding how to architect our app, we went with microservices, containers and DevOps. About now you’re expecting a story of how everything went so smoothly, we’re now pushing out code ten times a day, but the reality is quite different.
    "We are a monitoring company. We work with Salesforce, BBC, and quite a few other big logos. We basically provide monitoring for them, structure for their cloud services and we fit into the DevOps world" explained David Gildeh, Co-founder and CEO of Outlyer, in this SYS-CON.tv interview at DevOps Summit at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    21st International Cloud Expo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Me...
    If you cannot explicitly articulate how investing in a new technology, changing the approach or re-engineering the business process will help you achieve your customer-centric vision of the future in direct and measurable ways, you probably shouldn’t be doing it. At Intellyx, we spend a lot of time talking to technology vendors. In our conversations, we explore emerging new technologies that are either disrupting the way enterprise organizations work or that help enable those organizations to ...
    In 2014, Amazon announced a new form of compute called Lambda. We didn't know it at the time, but this represented a fundamental shift in what we expect from cloud computing. Now, all of the major cloud computing vendors want to take part in this disruptive technology. In his session at 20th Cloud Expo, Doug Vanderweide, an instructor at Linux Academy, discussed why major players like AWS, Microsoft Azure, IBM Bluemix, and Google Cloud Platform are all trying to sidestep VMs and containers wit...
    The taxi industry never saw Uber coming. Startups are a threat to incumbents like never before, and a major enabler for startups is that they are instantly “cloud ready.” If innovation moves at the pace of IT, then your company is in trouble. Why? Because your data center will not keep up with frenetic pace AWS, Microsoft and Google are rolling out new capabilities. In his session at 20th Cloud Expo, Don Browning, VP of Cloud Architecture at Turner, posited that disruption is inevitable for comp...
    For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
    There's a lot to gain from cloud computing, but success requires a thoughtful and enterprise focused approach. Cloud computing decouples data and information from the infrastructure on which it lies. A process that is a LOT more involved than dragging some folders from your desktop to a shared drive. Cloud computing as a mission transformation activity, not a technological one. As an organization moves from local information hosting to the cloud, one of the most important challenges is addressi...
    What's the role of an IT self-service portal when you get to continuous delivery and Infrastructure as Code? This general session showed how to create the continuous delivery culture and eight accelerators for leading the change. Don Demcsak is a DevOps and Cloud Native Modernization Principal for Dell EMC based out of New Jersey. He is a former, long time, Microsoft Most Valuable Professional, specializing in building and architecting Application Delivery Pipelines for hybrid legacy, and cloud ...
    Companies have always been concerned that traditional enterprise software is slow and complex to install, often disrupting critical and time-sensitive operations during roll-out. With the growing need to integrate new digital technologies into the enterprise to transform business processes, this concern has become even more pressing. A 2016 Panorama Consulting Solutions study revealed that enterprise resource planning (ERP) projects took an average of 21 months to install, with 57 percent of t...
    Microservices are increasingly used in the development world as developers work to create larger, more complex applications that are better developed and managed as a combination of smaller services that work cohesively together for larger, application-wide functionality. Tools such as Service Fabric are rising to meet the need to think about and build apps using a piece-by-piece methodology that is, frankly, less mind-boggling than considering the whole of the application at once. Today, we'll ...
    In his session at Cloud Expo, Alan Winters, an entertainment executive/TV producer turned serial entrepreneur, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to ma...
    Hybrid IT is today’s reality, and while its implementation may seem daunting at times, more and more organizations are migrating to the cloud. In fact, according to SolarWinds 2017 IT Trends Index: Portrait of a Hybrid IT Organization 95 percent of organizations have migrated crucial applications to the cloud in the past year. As such, it’s in every IT professional’s best interest to know what to expect.
    Both SaaS vendors and SaaS buyers are going “all-in” to hyperscale IaaS platforms such as AWS, which is disrupting the SaaS value proposition. Why should the enterprise SaaS consumer pay for the SaaS service if their data is resident in adjacent AWS S3 buckets? If both SaaS sellers and buyers are using the same cloud tools, automation and pay-per-transaction model offered by IaaS platforms, then why not host the “shrink-wrapped” software in the customers’ cloud? Further, serverless computing, cl...
    In the decade following his article, cloud computing further cemented Carr’s perspective. Compute, storage, and network resources have become simple utilities, available at the proverbial turn of the faucet. The value they provide is immense, but the cloud playing field is amazingly level. Carr’s quote above presaged the cloud to a T. Today, however, we’re in the digital era. Mark Andreesen’s ‘software is eating the world’ prognostication is coming to pass, as enterprises realize they must be...
    Colocation is a central pillar of modern enterprise infrastructure planning because it provides greater control, insight, and performance than managed platforms. In spite of the inexorable rise of the cloud, most businesses with extensive IT hardware requirements choose to host their infrastructure in colocation data centers. According to a recent IDC survey, more than half of the businesses questioned use colocation services, and the number is even higher among established businesses and busin...