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
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.
Pipelines	CI/CD pipelines automate the processes of building, testing, and deploying code to ensure faster and reliable software delivery.
Workflow	A Workflow is a sequence of automated steps that developers and operations teams follow to build, test, deploy, and monitor software. It ensures continuous integration, delivery, and feedback for faster and reliable releases.
Event	An event is a record of a significant action or occurence in a system, showing what happened, why, where, and when.
Guardrail	Guardrails define scheduled rules for efficient environment management, automating scaling (up/down), environment and cluster deletions, and cluster nodegroup scaling ( up/down) based on predefined schedules or conditions to ensure best practice compliance.
Integrations	Integrations connect different tools and technologies to automate processes, streamline workflows, and enhance functionality across platforms.
Security	Security ensures compliance and protection through scans like CIS Level 1 & 2, PCI-DSS, SOC 2, and HIPAA to safeguard data and systems.
Cost Analysis	Cost analysis is the process of evaluating expenses to understand, manage, and optimize spending. You can check the total estimation cost for selective resources before creating any cluster.