TIBCO Mashery Local Overview

TIBCO Mashery® Local is a cloud-native API gateway that can be deployed within a customer's datacenter or on cloud platforms.

TIBCO Mashery Local supports two deployment options: Untethered, without any external dependencies, or in a hybrid manner working with TIBCO Cloud™ Mashery. When operating in an untethered mode, the Configuration Manager tool can be used to configure API policies, packages and plans, and manage API keys. Logs from TIBCO Mashery Local can be collected and forwarded for downstream reporting and analytics via other externally-available tools. When operating in a hybrid mode, TIBCO Cloud Mashery includes the cloud-hosted Developer Portal, Administration Dashboard, and API Reporting and Analytics.

TIBCO Mashery Local includes commercial support for Project Flogo microgateway. For more information about Project Flogo microgateway, see https://github.com/project- flogo/microgateway.

TIBCO Mashery Local is available to customers for installation in container-based environments.

TIBCO Mashery Local Components include:

  • NoSQL

    Each NoSQL component is a Cassandra Node. Multiple nodes can be deployed as a ring in a Data Center that maps to a TIBCO Mashery Local Zone and Kubernetes Zone. TIBCO Mashery Local relies on Cassandra for data availability across Zones in a TIBCO Mashery Local Cluster.

  • Registry

    The Registry component is responsible for storing the topology of a TIBCO Mashery Local cluster. Every TIBCO Mashery Local component communicates with the registry so it knows about each components's physical information (host, IP, Container Agent URL), its state, and bindings to resources.

  • Log

    The Log service component provides the data collection services for all TIBCO Mashery Local components. It also provides Log Consumer services to be able to send the logs to various destinations for processing and analytics.

  • SQL

    The SQL component runs a MySQL Database and stores the configuration data related to services, packages, keys, applications and related information.

  • Cache

    The Cache component runs memcaches pools and provides in-memory cache for fast access to configuration and OAuth data.

  • Traffic Manager

    The Traffic Manager component provides the traffic management and OAuth capabilities.

TIBCO Mashery Local components can be deployed in a single zone or multiple zones to form a cluster of components to address scalability, reliability, and high availability requirements. TIBCO Mashery Local relies on Cassandra for data availability within and across Zones.

Definition of a Cluster

"Cluster" means a TIBCO Mashery Local installation with all the necessary Mashery Local components located at the same physical address (for example, 3307 Hillview Avenue) if being deployed within a customer's premises; or one region, if being deployed in the cloud. Each TIBCO Mashery Local cluster includes support for up to 10 Flogo app instances with microgateways.

Any installation spanning across multiple regions in the cloud (or multiple physical addresses if within customer's premises) are counted as separate Clusters.