Custom software

Docker in SIDECUBE digital projects

Docker is useful for applications and backends to be run predictably in development, staging and production.

Match

When we use Docker

The technology is chosen after we understand the objective, the rhythm of the team, the level of administration and how much the project needs to increase.

  • Custom applicationsWe start from the real process of the company and build the functions that standard solutions do not cover.
  • API backendsWe expose the server functions through documented endpoints with consistently treated access and errors.
  • Staging environmentWe check changes in a separate environment before applying them to the version used by customers.
  • Deploy predictableWe shall establish the publication steps, the checks and the return to the previous version if necessary.

Uses

What can we build with Docker

We only use technology where it helps the project to be faster, easier to manage or safer to expand.

Deliverables

What goes into implementation

Accurate delivery depends on the project, but we keep every documented, tested and prepared implementation for maintenance.

  • Dockerfile
  • Composites for services
  • Environmental variables
  • Deploy documentation
  • Building checks

Frequently Asked Questions

Before you choose technology

Uses, integration and costs for Docker.

01 / Match

When that choice makes sense

What projects do you consider Docker for?

Suitable situations: Custom applications; API backends; Staging environment; Predictable Deploy. The choice shall be confirmed after analysis of existing requirements, team and solutions.

What uses do you propose for Docker?

Relevant examples are: Application Containerisation; Local Environment; Backend Services; Controlled Deploy. We determine what serves your objective and what would add complexity without a clear benefit.

02 / Implementation

Integration and deliverables

Can the solution be integrated into an existing project?

We inventory available applications, data and interfaces. We check compatibility, permissions and consequences for existing processes before changing an operational flow.

What could include implementation?

For Docker, we can define in the offer: Dockerfile; Composes for services; Environmental Variables; Documentation deploy; Buildings checks. We confirm the deliverables after verification of compatibility and available access.

03 / Operation

Verification and costs

How do you check that implementation works?

We use scenarios with representative data to check the rules, data integrity and errors. To connect systems we also check access, synchronisation and possibility of recovery.

What costs should be foreseen in the long term?

We separate the analysis and development of infrastructure, licenses and use. Data volume, number of users and availability requirements influence the long-term cost.