Introduction¶
Service is an application deployed in D2C.
D2C executes your services/applications inside containers. We use Docker as our containerization platform. Each app is a separate container: web-app, database, load-balancer, etc. Docker is installed and configured on the hosts that are managed by D2C automatically. When you deploy your service, all the necessary files are delivered to the host, and container images are built locally on the host and then run by Docker daemon. D2C configures the environment automatically, so we do not recommend to add your current development boxes as managed hosts, to prevent any configuration conflicts.
Once you can deploy up to 50 containers (except services, which have their limitations).
Naming¶
Each service has its unique name. Services can communicate with each other by container names (e.g. servicename-1 or alias-names (e.g. servicename or servicename-master). It doesn’t matter on which host a service is running – all private network intercommunication is transparent for services. Moreover, we use them to create public domains like: [servicename]-[www].[accountID].[at].d2c.io for your services which are served by NGINX or HAProxy.
The name should start with a letter and contain up to 16 characters (Latin letters, numbers, hyphen).
Native support¶
Data services¶
| Name | Configuration | Scalable | Supported versions |
|---|---|---|---|
| MongoDB | StandAlone or ReplicaSet | Yes | 3.6, 4.2, 4.4 |
| MySQL | StandAlone or MasterSlave | Yes | 5.5, 5.6, 5.7, 8.0 |
| MariaDB | StandAlone or MasterSlave | Yes | 5.5, 10.4 |
| Percona | StandAlone or MasterSlave | Yes | 5.5, 5.6, 5.7, 8.0 |
| PostgreSQL | StandAlone or MasterSlave | Yes | 9.6, 10.5, 11.7, 12.0 |
| Redis | Yes | 3.2, 4.0, 5.0, 6.0 | |
| Memcached | Yes | 1.4, 1.5, 1.6 | |
| ElasticSearch | StandAlone | No | 5.6, 7.7.0 |
Application services (Runtimes)¶
| Name | Scalable | Supported versions |
|---|---|---|
| Node.js | Yes | 8, 10, 12, latest(13) |
| Python | Yes | 2.7, 3.7, 3.8 |
| Go | Yes | 1.13, 1.14, 1.15 |
| Ruby | Yes | 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 |
| PHP+NGINX | Yes | 7.2, 7.3, 7.4 |
| PHP+APACHE | Yes | 7.2, 7.3, 7.4 |
Other services¶
| Name | Scalable | Supported versions | Comments |
|---|---|---|---|
| NGINX | No | 1.16, 1.17, 1.18, 1.19 | NGINX is an edge service for serving on top of stack. It can generate free TSL certificates (by Let’s Encrypt). |
| NGINX-Static | Yes | 1.16, 1.17, 1.18, 1.19 | NGINX-Static returns static files (HTML, JS, CSS, images, etc.). It cannot serve other services. |
| HAProxy | No | latest | HAProxy is a load balancer. May be used as edge service. It can generate free TSL certificates (by Let’s Encrypt). |
| Docker (Services based on Docker Images) | Yes |
Actions¶
Basic actions¶
- Edit
- Update version
- Restart
- Stop/Start
- Change projects
- Clone
- Scale (except some services e.g. NGINX)
- Destroy (+force destroy)
- Deploy from scratch. For cases when you want to start deploying service from scratch
Actions with application services¶
Smart update feature which you can choose separately or combine with each other:
- Update version (data and other services have only this one)
- Update global dependencies
- Update local dependencies
- Update sources
- Include .git folder
Actions with containers¶
- Service Scaling (except some services e.g. NGINX)
- Add load-balancer
- Log redirection
- Execute command
Additional action with databases:¶
For MongoDB, MySQL, MariaDB, Percona, PostgreSQL services:
- Reset password
- Migrate (configuration) from StandAlone to MasterSlave/ReplicaSet
Services data¶
All data of services are stored in: /ebs/containers/serviceName
For example, you can find sources in: /ebs/containers/serviceName/sources
Backups: /ebs/containers/serviceName/backup
Persistent data¶
D2C separates the application itself from its data. Docker volumes are used to store persistent data. Data is stored locally on the hosts. Any data which is generated by an application should be added to Persistent data volumes. All modifications outside of these directories will be deleted after restart/rebuild/redeploy of a container/service (Docker restores the original state of a container).
You can create new volumes using Add volume button. The host path by default is created automatically. You can change it but be careful. It can break the whole host.
Synchronizing¶
We recommend storing user generated content in cloud storage like Amazon S3 or CDN. Sometimes there is a need to support old technologies when data stores at hosts. For such cases you can use synchronization volumes between all containers. Simply check the volumes which you want to sync when creating or editing service. D2C uses Lsync for synchronization.
System Logs¶
Each service has system logs (deploy logs).
The line which has ellipsis marks, in the end, can be opened with a mouse click.
Cron tasks¶
You can create and manage Cron tasks at the service page.
Read more about how to create a cron job
How the service page look like¶
