Before you begin
You will hear a few terms here and there throughout the documentation, so let’s get some terminologies cleared -
| Concept | Description |
|---|---|
| AWS | Amazon Web Services |
| Azure | Microsoft cloud services |
| GCP | Google Cloud Provider |
| Cluster | Across Atmosly, Cluster refers to a Kubernetes Cluster. A Kubernetes Cluster is a collection of node machines that allows you to run containerized applications. |
| Addons | An "addon" refers to additional software components or extensions that enhance the functionality of your Kubernetes Cluster. These addons can provide a wide range of features, from monitoring and logging to networking and security enhancements. |
| Project | The project is an application blueprint. Allows you to group a set of services interacting with each other to serve a common purpose. The project also allows you to declare Environment variables that would allow an application to successfully connect with another service. |
| Service | Service is the basic unit that you can add to an Environment. Each service has an associated git repository (or registry) that will be used to deploy the service on the Cluster. Two types of services exist within Atmosly: ➤ Application: Application services are modular components or microservices that encapsulate specific business logic, rules, or processes, making them reusable and scalable across different parts of an application or even across different applications. For example, backend, frontend etc are application services. ➤ Datasource: it allows you to deploy a database for the application you want to run. Atmosly currently supports the following four types of databases: → Postgres → MySQL → Redis → Mongo |
| Environment | An Environment allows you to group a set of services having a specific version, usually based on a branch of your repository. For example, you can have one Production environment (all the services pointing to the main branch), one Staging environment (all services pointing to the staging branch), etc. You run your application on an environment. |
| Deployment | A "deployment" refers to the process of delivering a software application to a runtime environment where it can be executed and accessed by users. In Atmosly, we use this term literally. You make deployments of an application to the Environment. |
| Event | An "event" refers to the guardrail which was created to run on schedule. |
| Guardrail | Guardrails are the policies you can implement on Atmosly. |