Microservices
Microservices is the first architecture emerged after the DevOps revolution. It matches perfectly with Cloud adoption and Continuous Delivery practices.
The pillars are resiliency, scalabilily and real-time monitoring. Microservices is an architectural paradigm to obtain high availability through small autonomous monitored services.

.

Greenfield project

Microservices approach is focused on the analysis of the goal to identify the various indipendent components that will be leveraged to achieve the objective.
This is our current approach at new projects and allows us to deliver reusable applications, capillarly scalable where needed and easy to monitor accurately.
This enables us to re-employ every component already developed for our infrastructure (mail sender, third-party integration…) handling versions and releases of the component itself.

Should I create a new project to move to µs? No!

We favour microservices even when we are facing existing applications that need refactoring or performance improvements. Identifying indipendent and critic components is the first step before detaching them and thus reaching chrurgical scalability with resilient and automatic means.

Scalability

As a rule of thumb is easier and cheaper to scale a microservice rather than a monolithic application. This approach enables a dynamic, resilient, intelligent and cheaper provisioning.
The catch is that to manage and develop a microservice there is a lesser need of hardware resources and effort.


Scalabilità microservizi

Containers, orchestrators and Cloud: manage and monitor applications.

To fully enjoy the microservices approach we need to use containers (and orchestrators).
Among the orchestrators the best current option is Red Hat Openshift and we have (other than a long lasting partnership with Red Hat) a very through knowledge and enterprise experiences either for user load or number of unique services.
Through this approach and keeping the infrastructure in Cloud you can manage the resiliency of the applications consuming resources as configured for the handled load. Every major public cloud provider support such approach (ex. Amazon ECS).

Another option is using frameworks that don’t enforce a provided infrastructure (a lighter approach, provider-agnostic) such as Spring Netflix.


          Docker

DevOps: no-downtime automation

The microservices style architectural resiliency toghether with DevOps best practices are the means that ensure a secure and automated management. In particular these practices allow secure and accurate releases excluding downtime or slowness usually crippling monolithic applications releases.

 

 

Contact our Team! If you're interested or want more information on our services, please fill out the form below and we'll get back to you as quickly as possible.
 The information provided here will only be used for contact purposes and will remain completely confidential. It will not be distributed to third parties.
Message sent.