GLU.Ware Architecture

GLU.Ware is a suite of cloud services that enables the configuration, build, test, governance, monitoring and management of one or more integration flows that connect any combination of on premises and cloud-based processes, services, applications and data within individual, or across multiple, organisations, across any channel.

GLU.Ware™ comprises two essential constructs as illustrated below.


The GLU.Console™ is the ‘brain’ of GLU.Ware™. It provides the ability for a Systems Analyst to rapidly define / configure integrations via a GUI. Tight version control of configurations and builds is built into the SDLC Process Management capabilities of the GLU.Console. APIs and Connectors (connections to various end systems) are configured as re-usable ‘building blocks’. These are SDLC Environment context aware. The GLU.Console™ offers an expanding library of supported API protocols and Connectors, scaling GLU.Ware’s ability to drive agility for our customers. It has configurable user management and SDLC Process Management and provides built-in monitoring of the deployed GLU.Engines™. The GLU.Console™ offers seamless access to a number of supplementary ‘Value added Services or Products’ (VAS) such as Consumer Channel Server, Channel Configuration Tool, Fraud Detection, Big Data, BI and Consumer Experience Monitoring amongst others.


The GLU.Engine™ produced by the GLU.Console is lightweight and fit for purpose. It only contains the libraries, protocols and code necessary for its targeted purpose. It is deployed behind the Customer’s firewall and within the Customer’s security policies and controls. The Customer’s team manage it and GLU.Console™ only has visibility of the system and environmental ‘health’ status. The handling of the GLU.Engine™ as the integration component in the Customer’s ecosystem is entirely the responsibility of the Customer. This implies that GLU does not have responsibility for how the GLU.Engine™ is deployed or run within the Customer domain. This segregation of duties between GLU and the Customer is implemented by design. GLU.Engines are Stateless in that each session is carried out as a unique event and responses are handled independently of data from any previous session.


GLU.Engines as Microservice Orchestrators Configuration of GLU.Engines in the GLU.Console allows for multiple GLU.Engines to be built. This may be for different end Clients or within an integration layer where one implements a ‘micro-service’ based integration architecture. Using a series of micro-service specific GLU.Engines with REST connectors interlinking them to each other and to the micro-services they service makes it easy to maintain, manage and roll-forward / back your evolving Micro-service based Applications.


The level of separation is as follows: at the Application Level, GLU.Engines are completely separate from each other but at the Connector level, it’s possible that one Connector can be used by multiple Applications, so the selection of which Connectors are available to be used by which Applications is dealt with within the Connector configuration space. Similarly Environments per Application are managed within the ‘Manage Application Environment’ tool. Further it is possible to also restrict users to only specific Applications.

Was this article helpful?

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Need Support?

Can't find the answer you're looking for?
Contact Support
Fill the form and we’ll contact you shortly

    I agree with

    cookies
    We uses cookies to make your experience on this website better. Learn more
    Accept cookies