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.

Mashery Local supports two deployment modes: Untethered, without any external dependencies, or hybrid in conjunction with TIBCO Cloud Mashery. These two deployment modes are mutually exclusive. In hybrid mode, TIBCO Cloud Mashery includes the cloud-hosted Developer Portal, Administration Dashboard, and API Reporting and Analytics. In untethered mode, Mashery Local includes a local Developer Portal and Configuration Manager. It also includes the ability to update policies using the Mashery Local API. Mashery Local Configuration Manager and Mashery Local API are no longer mutually incompatible like in previous 5.x versions. In untethered mode, logs from Mashery Local can be collected and forwarded for downstream reporting and analytics via other externally-available tools. Mashery Local is available to customers for installation in container-based environments.

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 Mashery Local Zone and Kubernetes Zone. Mashery Local relies on Cassandra for data availability across Zones in a Mashery Local Cluster.

  • Registry

    The Registry component is responsible for storing the topology of a Mashery Local cluster. Every 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 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.

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. Mashery Local relies on Cassandra for data availability within and across Zones.

Definition of a Cluster

"Cluster" means a 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 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.