Consultancy services in Cloud Computing and Systems Reliability Engineering (SRE).

Cloud Computing

Cloud Native Software Architecture

Cloud Native Software Architecture is a software engineering approach that focus on build applications to run on a cloud computing environment. These applications are designed to capitalize on the inherent characteristics of a cloud computing software delivery model. Cloud native refers to an approach to building applications or services for the cloud as well as the characteristics of those applications and services. Cloud-native applications are easier to update because they are made of microservices that run in containers, meaning the application is broken into pieces that can be individually updated. DevOps teams use continuous integration and continuous delivery (CI/CD) to keep their portion of an application up to date.

  • Software Architecture Assessment;

  • Strategy and Build of Modern and Cloud Native Applications;

  • Technical Team Structuring.

Cloud Capacity Planning

Capacity planning examines what systems are in place, measures their performance, and determines patterns in usage that enables the planner to predict demand. A system uses resources to satisfy cloud computing demands that include processor, memory, storage, and network capacity. Capacity planning is determining the ability of a production line, service department or function to meet a specified demand over a period of time. Inherent in this are actions required to adjust the capacity of the system to meet demand.

  • Capacity Planning Assessment;

  • Sizing Strategy and Modeling;

  • Architectural Classification, Sizing Equation Definition and Confidence Index Analysis.

Systems Reliability Engineering

Production-Ready Systems

A piece of software is considered production-ready if it is capable of meeting the demands of its users. This includes ease of usability, reliability, and availability. Various software teams assess these criteria in different ways, but Agile teams lean on acceptance of user stories in order to validate usability, and automated testing to validate reliability. The last piece, availability, means that the software must be available to use (e.g. it must be in production). Agile teams maximize availability by leveraging automated deployments and practicing continuous delivery.

  • Production-Ready Systems Assessment;

  • Gap Analysis and Diagnose;

  • Improvement Plan Definition and Technical Advisory.

SaaS Architecture

The software-as-a-service (SaaS) delivery model presents developers with a series of challenges, starting with the establishment of a new scenario of technical, operational and deployment considerations for these products. Adopting the SaaS profile often means rethinking the fundamentals of the entire business, not just from a technical perspective, but from an organizational perspective as well. To support associations in this service trajectory of adopting such a software model, the SaaS Enablement Framework is applied. The goal is to provide a roadmap for developing, operating and launching SaaS offerings in the cloud. By ranking SaaS best practices and design tradeoffs, you can enable catalysts for the SaaS community.

  • SaaS Enablement Framework Assessment;

  • Accessing, Building and Managing SaaS;

  • Profiling, Selling and Billing SaaS.


Customized workshops for corporate clients with a focus on the successful adoption of native and reliable architectures in the cloud.


Corporate talks on:

  • Science;

  • Innovation;

  • Entrepreneurship;

  • Cloud Computing;

  • Systems Reliability Engineering (SRE).

Contact us for more information on the lectures currently given in each of the related topics.