| Status | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|
What is a Namespace?
...
Inside each PIPEFORCE namespace multiple services are hosted to run your solutions. Depending on your setup, the number and type of these services could differ. Each service is encapsulated inside a (“Docker”) container and can “talk” to each other:
...
| Info |
|---|
We use the term “Docker” container for any type of container, for simplicity. Although in the backend different container types are supported like: containerd, Docker, CRI-O, and Mirantis. |
Public Service
Usually these services are by default available within your namespace and can be accessed from the public internet. They are therefore called "public" services:
...
Beside the default services provided by PIPEFORCE as mentioned above, there could be additional, custom services depending on your license / setup. PIPEFORCE allows to deploy a container easily as an additional custom service into your namespace. This can be a container provided by the Docker Hub or developed and built by yourself.
...
In case you have questions about how to develop resilient and scalable microservices in PIPEFORCE, feel free to ask our Support team.
...
Typically, the staging process is seperated separated into at least three tiers: DEV, QA, PROD.
...