Whose Problem Is Your Cloud Architecture Solving?

English summary of Marcello Meneghel’s article published on LinkedIn on September 21, 2026. The complete original article is linked below.

Cloud brought faster provisioning, automation and access to advanced services. The question is how to use those capabilities to meet business needs without allowing a provider’s service catalog to determine the architecture.

An available capability is not a requirement

Containers, Kubernetes, managed databases and AI services can all be useful. Every decision must still respond to the application’s context, the operating model and the value it is expected to create. A reference architecture should support requirements rather than manufacture them.

Portability requires a view of dependencies

A common platform can reduce differences between environments. The application still relies on data, identity, networks, integrations and specific services. Understanding those relationships helps identify where standardization creates value and where a dependency is justified by its benefits.

Read the complete original article on LinkedIn ↗