📄️ Namespace
Mager use namespacing concept to create isolation between application. Namespace can contain as many as service and capsule you want, it will connected to same network, so you can communicate between services in same namespace using internale network. One or multinode can contain many namespace but services between namespace cant comunicate via internal docker network. In most usecase you will only need 2 namespace local and your project namespace, you can also treat namespace as development environment if you want you can easily replicate service or capsule installed from another namespace with minimum effort.
📄️ Mager Definition
Mager definition are yaml file that contain information that required by Mager to build and deploy your services. Mager definition can only contain 1 image, those image can be used in multiple service in same definition.
📄️ Service
Service is your application that defined in your mager definition and Capsule that are already deployed is alsoe considered as service, so you can manage all of them using mager service:
📄️ Capsule
Capsule is third party outside your service scope that can installed in your namespace. For example database and application to support your service. Capsule that have installed in your namespace are categorized as service so you can manage them also.