Microservices architectures needn't be overly burdensome. You just need the right recipe for success.

Microservices visualized Microservices - decoupling your service architecture

Microservices success can be broken down into 5 key capabilities that enable this strategy.

  1. Componentization: The run-time architecture must support componentization of services at a granular level. Flexibility to connect these components together in different ways is needed for different use cases. (e.g. exposing a microservice easily via EDA/Messaging, REST/JSON/OAuth, or SOAP/WS-Security, etc.) This will vary, whether the use case is Cloud, Mobile, IoT, etc. How do we support this? We have built-in a common run-time across our suite, based on OSGi. We also have a componentized Deployer that enables configurable runtimes, so you just deploy what you need to specific nodes. In addition, we provide suite-wide governance and visibility of components, services, runtimes, and clusters.
  2. Automated, templatized deployment: De-centralized, decoupled, and elastic architectures must be automatically deployed, but through central management. We have built-in "elastic" deployment capabilities into our webMethods ESB. Our elastic ESB and Messaging enable dynamic scalability of components, with centralized management, governance and monitoring of services, APIs, and other runtime components. The management of this is fully automated through our Command Central and Deployer components.
  3. Virtualization capabilities: Enable greater flexibility in decoupling of services from their consumers. Allow applying different end-point protocols and policies, and allowing routing logic that supports multiple versions of microservices at run-time. Our runtime architecture is fully compatible with Virtualization and Cloud architectures from VM Ware, Amazon, Microsoft, IBM, HP, Red Hat, and others. It's also fully compatible with newer standards such as Docker.
  4. Extensible security and governance: Decentralized components need flexibility in deployment and enforcement of security policies and other governance. This allows flexibility in policy enforcement based on use-case specific risks and requirements. But this must be centrally managed to keep operational costs low. We provide our CentraSite platform for suite-wide management of services, APIs and other assets, components, and runtimes. We also provide suite-wide capabilities for dynamic security policy enforcement based on standards such as OAuth, WS-Security, X.509, NTLM, Kerberos, HTTPS, and others.
  5. Visibility and management: Microservices architectures are typically more complex. Thus they require greater visibility of errors, root-cause analysis, transactional assurance, etc. Without end-to-end visibility, supporting a Microservices architecture can quickly become an operational nightmare. We provide Insight and Optimize to monitor the flow of transactions across runtimes for end-to-end transactional visibility and assurance. This enables instantaneous root-cause identification of problems, latency issues, errors, and allows you to catch problems before they result in outages.

Where have we done this? What types of customers are using our platform in highly distributed architectures?

Customer across a wide range of industries are doing Microservices-style deployment architectures with webMethods. We have retailers running a "micro-version" of our ESB embedded into their Point-of-Sale systems in every retail store, in many cases over 1000 locations running microservices on webMethods. We have multiple customers in the cruise line industry running our ESB on every one of their cruise ships. We have numerous customers in manufacturing and banking who have our software running in hundreds or even thousands of separate VMs. There are even customers leveraging our integration technology across IoT and Mobile and even from Kiosks, where thousands or tens of thousands of clients are communicating with globally distributed clusters of our messaging products and feeding this data to clusters focused on a wide range of components hosting services, analytics, and other capabilities. And we have OEM customers hosting hundreds or thousands of distributed componentized services on webMethods for their own Cloud and Service Bureau offerings.

Feel free to reach out to me directly or to your local account executive, presales, and consulting teams to find out more about how we can support you in adopting a more flexibile, scalable and decentralized Microservices strategy, enabling greater Agility and Scalability to drive further growth in your business. We can also share more about what other customers are doing and how we've made them successful.

Learning more:

Elastic ESB - webMethods Integration Server and Command Central:



Management and Monitoring of Highly-Distributed Services and APIs with the CentraSite suite and Insight.


Continuous Integration with webMethods:


Leave a comment

Search B2B

Most Popular Blog Posts


Connect with us!