GLU.RESOURCES

Integration Platform as a Service (iPaaS) is a suite of cloud services enabling development, execution and governance of integration flows connecting any combination of on premises and cloud-based processes, services, applications and data within individual or across multiple organisations.

No Code is a software development approach that requires few, if any, programming skills to quickly build an application. This allows line of business (LOB) employees who have the necessary institutional knowledge and understand the business requirements for an app, but lack knowledge of programming languages, to create software applications such as a form or website, or add functionality to an existing site or app. No Code decouples programming languages and syntax from logic, and instead takes a visual approach to software development to enable rapid delivery. In this sense, no-code is similar to low-code development.

The key difference is that Low Code platforms use less abstraction -- that is, they incorporate some coding and require some knowledge of programming languages -- and are often used by professional developers within an enterprise IT department.

Yes, GLU.Ware requires no programming knowledge whatsoever ... so GLU.Ware is truly No Code.

We have decoupled the NO CODE GLU.Console configuration environment from the runtime Integration components - the GLU.Engines. This segregation puts the control of all data being processed by the GLU.Engines completely in the Clients control.

EAI is the process of connecting disparate systems to allow for “communication” and data sharing between them.

EIPs define a series of steps that provide the framework for enterprise integration solutions. EIPs are not tied to specific implementations but provide a method of “communication” between systems. The concept of an EIP was made popular by Gregor Hohpe and Bobby Woolf in their book ‘Enterprise Integration Patterns’. Together they created a catalogue in which they explain 65 patterns that fall under what they call the messaging integration style. They define this type of integration as using “messaging to transfer packets of data frequently, immediately, reliably, and asynchronously, using customisable formats.”

Enterprise integration is the process of configuring various systems to work together in order to increase efficiency and interoperability. The goal is to use all the systems together like a well-oiled machine towards the realisation of the mission of the organisation.

You have a patchwork of systems and databases developed without architecture or planning. Data is fragmented and silo'ed. Legacy systems are holding your business back. Launching new systems is materially a function of the integration complexity. Integrating systems is too slow and expensive.

Metcalfe's law characterises many of the network effects of communication technologies and networks and integrated ecosystems. Metcalfe's Law is related to the fact that the number of unique possible connections in a network of 'n' nodes can be expressed mathematically as: n*(n-1)/2 ... which is asymptotically proportional to nxn. Integrated Ecosystems with a point-to-point integration architecture suffer the implications of this mathematical fact. By adopting an Enterprise Integration architecture, the number of connections = n.