How Trillo Workbench Works
Frequently Asked Questions
Some application types are better served by using cloud-native tools. For example:
Yes! Workbench runs on a Kubernetes cluster that is configured and runs in your VPC environment. All network communication between Workbench and your backend GCP infrastructure services (databases, file storage, functions, etc.) stays within your environment.
Behind the scenes, Workbench uses native cloud services. It follows the best practice recommended for each service. The end result is the same as if you built it from the ground up yourself, except that you save up to 90% of the cost and time.
Absolutely! Workbench is built on Kubernetes using microservices. It can automatically scale up (or down) as needed to handle large loads while still maintaining excellent performance.
We have helped many enterprise-level customers build real-world applications that consistently experience heavy usage loads.
Metadata Service – application metadata such as database schemas, configuration files, SQL query templates, schedules, and workflow definitions.
Data Service – creates, alters, and operates on the database tables based on meta properties specified for each table and its columns. Using meta properties, it imposes access control rules (for example, a certain role can access a certain column). It provides CRUD, batch operations, and query APIs.
Storage Service – manages files using Google Cloud Storage, including uploading, downloading, sharing, and supporting folder/file operations such as mode, delete, and copy.
Function Service – Function Service dynamically compiles and executes plug-in code. In the production environment, it can use dynamic compilation with a jar file.
Workflow Service – executes functions in the background as tasks or workflows consisting of multiple steps. Developers can define workflows graphically. Alternatively, a function can implement a workflow by controlling the execution of multiple steps. Each step, in turn, is a function.
Scheduling Service – schedules a function or workflow for the periodic execution.
Firebase Notification – Workbench provides out-of-the-box integration with Firebase Notification for applications requiring a real-time push to a UI.
Audit Logging – Audit Logging is a powerful feature of Trillo Workbench. It tracks workbench activities performed by a client program or backend tasks. Standardizing audit log records provides easy search and filtering of a particular activity. It serves multiple purposes – troubleshooting, operations management, and compliance.
User Management – user management and authentication using a database or Google Cloud identity platform. Using SAML and OIDC, it can integrate with external authentication systems.
API Gateway – A client can access Trillo Workbench services using an in-built API gateway. The API gateway is oauth2 compliant.
Git Integration – Trillo Workbench uses a database for storing metadata. It retains multiple versions of metadata. It also integrates with a git repository so an admin can push metadata and plug-in code to a git-repo. A workbench instance running in a different environment can pull code from Git. Thus a typical Trillo Workbench deployment uses Git for managing development to QA to production code deployment processes.
No. Trillo Workbench is not a UI-building tool. We suggest you build your UI using other open-source technologies and use Trillo Workbench as a server using APIs.