When we analyze the history of the I.T and how it has evolved since its inception, a clear pattern draws itself and rules any transformation, let’s call it: the stacked abstractions.

So, everytime we have a new technology and the cloud is not an exception, it is most likely to be an abstraction of the previous inventions/technologies, here are just a few examples:

The operating system abstracts the HW.

The virtualization abstracts both the HW and the OS.

The containers abstract the operating system.

The orchestrators abstract the HW, the OS and the containers.

The cloud abstract all of them: HW, OS, containers, orchestrators and even applications.

Even the tools we use like Ansible, Terraform... are abstractions on the low level commands or API calls. This triggers an interesting question:

What will be the next step? Make the cloud and multi-cloud commodity as the HW has become and create another abstraction?

Or the history of the I.T will repeat it self: big corps, vendor lock-in, then open source...slowly...revolution-like...repeat?

https://www.brainboard.co made a bet on the following points:

Abstracting the cloud and multi-cloud will be a common practice.

Visualization has always been the starting point either on whiteboards or papers, so a visual graphical designer allows you to be fully productive by saving you a lot of time while respecting our native approach toward designing architectures.

Automation is already a common practice, so we take it to the next level by generating automatically and from the graphics the necessary code to deploy your cloud infrastructure.

We all know that DevOps is not a skill neither a technology but a culture that needs among a lot of things tools to unlock the creativity of the teams, we aim to be the bridge that connects people (engineers, developers, operators, administrators...) with the efficient use of technology.