Guepard / Deploy & Use
Guepard Platform Terminology
Welcome to the comprehensive glossary for Guepard. This section combines both specific terminologies and broader concepts to provide a holistic understanding of the features and functionalities within the Guepard platform.
| TERM | DESCRIPTION |
|---|---|
| Guepard | The name of the platform, representing a versatile and efficient solution for database versioning, management, and deployment. |
| Database | A database instance deployed on Guepard, created by selecting "New Database" and configuring the required infrastructure settings. |
| Managed Database (F2) / Fire & Forget | A fully managed database model in Guepard that automates versioning and lifecycle management through a structured timeline of bookmarks. |
| Shadow Database | A cloned version of a database created from a specific bookmark, inheriting the configurations of the parent database while allowing independent modifications. |
| Branch | A lightweight, independent copy of a database that allows users to work on different versions without affecting the main instance. |
| Bookmark | A saved reference point of a specific database state, allowing users to quickly access or restore that version. |
| Compute | The virtualized processing unit assigned to handle database operations, running in isolated micro VMs. |
| Checkout | The process of switching a database branch to a specific state or snapshot for use. |
| Logs | The recorded events and queries executed within a database, useful for debugging and monitoring activity. |
| Monitoring | The system that tracks and visualizes CPU and RAM usage of a database instance in real-time, helping users optimize performance. |