We recently introduced “A Complete Guide to TIBCO: Microservices and DevOps (Part 1)” based on the recent heavy discussion around Microservices and the beginning of a new era. Read on for more insight on how TIBCO customers have been creating and managing Microservices for years.
TIBCO API Exchange for Exposing Your Microservice Via Open API
TIBCO API Exchange is used to expose Microservices via REST, SOAP or JMS including policy-based API management features such as security, throttling, routing, and caching. In the context of Microservices, API Exchange is used to enforce consumption contracts, ensure Y-scaling and reliability of Microservices, and to reuse Microservices in multiple contexts without change. Besides, a portal is available for easy self-service consumption of Microservices (see Figure 3). The third part of API Exchange is the analytics component, which enables both API providers and consumers to understand usage and performance through interactive reporting.
“A New Front for SOA – Open API and API Management” explains the term “Open API” in more detail and gives a technical overview about the components of an API Management solution: Gateway, Portal, and Analytics.
TIBCO Silver Fabric for Continuous Integration/Continuous Delivery (DevOps)
Automation is key for an agile, flexible, and productive Microservices development. Without continuous integration/continuous delivery (DevOps), you can realize the Microservices concept efficiently.
TIBCO Silver Fabric is used to continuously deploy, configure, and manage your applications and middleware, on-premises or in the cloud. It offers to end-to-end scripting, automation, and visibility via dashboards, and monitors the quality of deployed application, ports management, and elastic load balancing.
TIBCO Silver Fabric offers several out-of-the-box features to run a project in a DevOps style. Besides, it supports tools such as Chef, Puppet, and Docker. You can deploy Microservices everywhere including private data centers, virtual machines, and cloud environments—supporting environments such as Amazon Web Services, VMWare or OpenStack. It’s important to understand that every Microservice is built and deployed independently from each other in a flexible and scalable way.
Click here for the final installment of A Complete Guide to TIBCO: Microservices and DevOps.