Being a cloud technology is used a lot in the industry but now with many applications and services moved to the cloud in various ways from the on-premise model how can we differentiate those that were built for the cloud and those who have migrated to the cloud - and why should we even care? Cloud-Native is a label given to those technologies born and built in the cloud and are using cloud-based services and distributed computing to their full extent.

But what about ageing SaaS platforms that haven't kept in step with the innovations in cloud services and focused on features, or those that have wrapped themselves in API and automated CI/CD deployments where do they fit?

#CloudNative is a central tenant of MACH architecture but what doe it mean to be could native in this context and how can we navigate the complex technology cloudscape. That's what I tackle in this video the CloudNative in the context of MACH and Headless architectures as well as provide some clarity on how all the variations of could implementation fit.

Interested in more MACH architecture videos see:
Headless the last MACH Concept
[ Ссылка ]

Webhooks and why they are so critical for MACH architectures.
[ Ссылка ]

See more of my articles on linked in
[ Ссылка ]

Most of what I have learned in the MACH / Headless world has been while building Amplience headless CMS, DAM and dynamic media services take a look at the Amplience Website and see a MACH platform in action
[ Ссылка ]

00:00 Introduction
01:28 The Cloudscape Model
02:06 The Cloud Towers - Monolith in the cloud
03:07 The Iceberg - legacy / monolithic SaaS
04:28 The Factory - Packaged cloud instances
05:52 Native Cloud deep dive

свернуть