- What does DevOps consulting involve?
- It reduces the time and risk between a code change and its arrival in production. At QMates that means working alongside your team on CI/CD pipelines, trunk-based development, infrastructure as code, observability and, where there is more than one team, platform engineering. The result you should expect is a team that releases often and can maintain what was built without us.
- What is the difference between continuous delivery and continuous deployment?
- With continuous delivery, every change that passes the pipeline is ready for production, and the release starts when someone decides it should. With continuous deployment it starts by itself, with no human step. Teams usually reach the second by way of the first, once tests and observability give them enough confidence.
- Does trunk-based development work with large teams?
- Yes, and with large teams long-lived branches cost even more, because conflicts grow with the number of people working on the same code. You need small changes, a fast pipeline, reliable tests and feature flags for unfinished work. The move is made in stages, shortening the life of branches before eliminating them.
- Do we need Kubernetes?
- It depends on how many services you run and who can operate them. For many organisations a managed cloud service is enough and demands less attention from the team. Kubernetes pays off when services are numerous and an internal platform hides it from the development teams. We assess it against your situation, and if the bottleneck is somewhere else, we advise putting the decision off.
- Do you build the internal platform yourselves?
- We guide and support your platform team as it designs and builds the platform, working at its side. The platform stays yours and your people will maintain it, so it is best that they understand every choice behind it. Our job is to help them start from the needs of the development teams and keep the golden path simple.
- Do you work with our cloud and our tools?
- Yes, we adopt the stack you have, including the cloud provider and CI/CD tools already in use. If a tool is what holds releases back, we say so with the measurements in hand and replace it in stages, with the old and the new running together for as long as needed.