profile

Lee Atchison

😅🥹👉Surviving the Riskiest Part of Your Cloud-Native Migration🫣

published3 months ago
1 min read

Surviving the Riskiest Part of Your Cloud-Native Migration

During any IT transformation project, the desired end goal is always the same: A more agile, scalable, supportable and cost-efficient application that better meets the needs of your customers. The journey through the transformation, however, is almost always a rocky one.

One of the trickiest transformations that many modern IT organizations are currently working on is cloud-native migration—moving an on-premises monolith application to a cloud-based, microservices-enabled, modern architecture application. The process of moving from an on-premises monolith to a modern cloud-native application is a key step that drives many current migration projects.


Cloud-Native Observability with Bruno Kurtic [podcast]

Welcome to the Modern Digital Business podcast!

Operating a modern digital business means building and operating large, highly-scaled applications that are more and more cloud-native in their architecture and implementation. Observability is critical in maintaining the highly scaled, highly available, highly adaptive nature of these modern cloud-native applications. You just can’t keep a large, complex, modern application operating without having a solid, modern observability platform as part of your system. And ideally, in today’s cloud-native market, you want an observability platform that is based on cloud-native technologies.

Bruno Kurtic, the founding Chief Strategy Officer for Sumo Logic is my guest on the Modern Digital Business.

To listen to the episode, click here:

If you'd like to here about new episodes as they become available, then subscribe to the podcast using your favorite podcast player, or click this link:


What You Need to Learn to Become a Cloud-Native Architect

Published on November 1, 2022

What is a cloud architect? What does a cloud architect do that’s different from a developer? What skills does someone need to move from a developer role to a cloud architect role—especially in the cloud-native world with microservices-based applications that run on platforms like Kubernetes? And how does architecting for cloud-native applications differ from other cloud architectures?

Becoming a cloud-native architect first involves, obviously, becoming a software architect. But, beyond that, a cloud architect generally has more responsibilities than just a standard software architect and requires more specialized knowledge and expertise. The modern cloud architect must understand how building and operating applications in the cloud differs from building and operating traditional applications. This isn’t a matter of understanding different programming concepts—this is about understanding the operational role of the modern application and the role that IT infrastructure plays in operating a modern digital application.