Gloop is Martini's graphical low code answer to application development. Using Martini and Gloop, you can map1 and manipulate data2 visually so that it can then easily be read and written to XML, JSON, YAML, SQL databases, flat files, JMS destinations, over HTTP, and anywhere else you can using the built-in functions.
Gloop works with all of the Martini endpoints, and is an excellent choice for consuming HTTP APIs 3, especially when consuming an API with a specification already available in widely used formats such as Swagger, OpenAPI, Postman collection WSDL, RAML, and WADL. Gloop also allows you to design and publish APIs in Swagger and OpenAPI formats, as a Postman collection, and in WSDL or SOAP format.
What's more, when Gloop itself doesn't have the ability to execute the logic you're after, you can write (or use existing) Groovy or Java code and drag and drop them into your Gloop services too. You can also write snippets of code that are embedded in Gloop to avoid writing new classes, or write new services written entirely in a supported language.
Gloop consists of two key components:
- Data models, which are the actual objects that store your data, and;
- services, which is where you write your code, manipulating the data in the Gloop objects.
or transform ↩
stored in Data models ↩
SOAP and REST ↩