2 cloud architecture problems are still unsolved

As 2021 begins to appear on the horizon, most people will be happy to see 2020 in the rearview mirror. Despite the pandemic and all its chaos and uncertainties, 2020 was the year of the cloud. Pandemic-weary enterprises rushed to the cloud for safety, scalability, and agility.

We still have some architectural obstacles to overcome. There’s no time like the present to review the two architectural problems on the top of my list.

First would be the edge data and knowledge tiering problem. When a tiered architecture includes an edge device, we need best practices and processes to figure out where to place data and knowledge bases and the back-end hyperscalers.

This seems like an easy problem to solve: Simply understand the workload requirements and then determine the proper tiering. Then the number of edge devices grows exponentially, the organic growth of data saturates the edge devices, and the requirements become quicksand.

We need a dynamic approach that uses automation to migrate the data and the knowledge bases as needed. But even that approach can be problematic through the negative effects of over-engineering. I’m working on this aspect of the solution right now.

The second problem is true federated multicloud security. You will probably point to IAM (identity and access management) solutions that span clouds, but I find that most are not yet ready for prime time.

Copyright © 2020 IDG Communications, Inc.

Source link