5G

Small-scale enterprises and organizations have started evaluating and implementing edge architectures due to the need to support innovative use cases to increase efficiency and/or enhance their customer experience. But there is still a long way to go for enterprise edge deployments as there are more challenges in large-scale distributed computing

Those who pay attention and follow the 5G space have probably noticed the phenomenon of Operators moving their infrastructure over to the cloud providers.

At AWS, I lead the global container practice for two key verticals – Telcos and M&E (Media and Entertainment). My group spends a lot of our time being customer-focused and working with customers & partners on a daily basis to understand trends, use cases, and business goals.

As service providers begin to roll out 5G POCs and initial deployments, there is no question that these cloud native platforms will be huge Capex and Opex investments on their part. These platforms should be able to handle diverse workloads such as telco, edge and enterprise applications. They must be efficient as well as robust from an operational standpoint. They must also serve the operator well for years. While it is never my intention to be hyperbolic or combative, the question is if Openstack is a viable 5G platform – when compared with hyperscaler clouds.

Ericsson just released the twenty-second edition of their authoritative Mobility Report, in which they continue to follow the evolution of the telecom industry. Ericsson calls out 5G as scaling faster than any previous mobile generation. This blogpost summarizes the key findings of the report from a 5G subscriber growth & global distribution standpoint.

This post will consider the top four intertwined system architecture considerations in deploying edge applications successfully on a hardware platform.

This week’s blog is a joint post by Nati Shalom, CTO Cloudify and yours truly. We discuss the need for multiple K8s clusters along with Network orchestration.

We continue our discussion of the public reference architecture on the Dish 5G buildout on AWS with a detailed look at the deployment automation of the implementation.

This implementation uses O-RAN standards and consists of a Radio Unit(RU) deployed on cell towers and a Distributed Unit (DU) as well as a centralized unit (CU) which is deployed in an AWS local zone.

We continue our discussion of the public reference architecture on the Dish 5G buildout on AWS with a look at the physical network design and datacenter layout.