Skip to main content

Workspaces

Those who have dealt with a large microservice architecture know the difficulty in staying organized and managing permissions.

Easybase's workspace feature allows users to keep resources and Microstacks in their own isolated environments, similar to folders on a hard drive.

tip

Example: If you wanted to deploy two instances of the same Microstack, multiple workspaces would allow you to avoid resource conflicts. This is because Easybase uses a database-per-service pattern, so the tables would be completely isolated from one another and organized in their environments.

https://app.easybase.io

All content in the Tables, Functions, Schemas, and Monitor pages are scoped to the currently selected workspace. So, changing workspaces will change all the visible resources.

https://app.easybase.io
tip

Use the dots "···" to delete unneeded workspaces. The default workspace, My Workspace 1, cannot be deleted.

Schemas

A great way to see a high-level overview of the selected workspace is to use the Schemas page.

The Schemas page will display just the available API routes of the currently selected workspace, along with their associated schemas. It is these schemas [that you can see when expanding a row] that allow for yourself and others to know the input/output parameters involved with that API along with some documentation for the variables.

https://app.easybase.io
info

The Monitor page will show you all the tables and functions in the currently selected workspace with various analytics and logging views available.