Microservices and agile development
We like to align ourselves with our clients and the value of the business provided to their clients. To this end, we use the best practices of Agile, QA and DevOps methodologies to ensure reliable and on-time delivery.
Why choose us for your microservices development
Our first objective is to understand the needs, priorities and way of working of the business. This helps us to determine the methodology and best technical solution for each case
Our group of professionals is able to transform the business requirements into technical requirements and implement them with clean coding and industry best practices.
To have highly qualified professionals it is essential to have a continuous training plan to stay up to date with the latest technology and methods.
Our strategic partners in terms of Microservices and DevOps are: CloudBees (Jenkins) RedHat (OpenShift, Ansible, etc.), MongoDB (NoSQL)
Quality – QA
In critical environments reliability is essential. This is where we begin working from gathering requirements to define how the environments will be tested (three amigos) and defining the appropriate metrics to obtain ROI.
Technically speaking, we consider the testing team to be part of the Scrum team, where the appropriate level
of testing per layer is determined based on the complexity and speed of the tests.
Técnicamente hablando para nosotros el equipo de pruebas es parte del equipo de Scrum donde se define el nivel
adecuado de pruebas por capa basado en la complejidad y la velocidad de las pruebas.l
Depending on the environment (from pure development to pure support), we use one of the following methodologies: Scrum, ScrumBan or Kanban.
As an example, our engineers are certified in Agility (Scrum Manager Certified).
Our solutions guarantee:
Reliability of all the components that make up the designed solution (QA). Agility in changing requirements (agile methodologies). The use of appropriate technologies (microservices best practices).
Using short iterations to achieve functionality and allow for changes based on new business requirements is part of the success.
Deciding whether tasks are done in Development or in Operations is the first step for automation from development to production, including QA testing.
We like to define the deliverables according to the tests that should be done and to structure the appropriate level of testing based on the importance of the deliverables and align them with the test pyramid.
When we talk about Microservices development, a number of technologies come into play: Cloud/OnPremise, container platforms, Pipeline, DevOps, programming languages, frameworks, patterns and UX.