A Retrospective on Workload Identifiers: From Data Center to Cloud-Native Networks

Abstract

As applications move to multiple clouds, the network has become a reactive element to support cloud consumption and application needs. Through each generation of network architectures, identifiers and the use of dynamic locators evolved in different levels of the protocol stack. The identifiers and locators type is defined by the isolation boundary and how the architecture considers semantic overload in the IP address. Each solution is an outcome of incrementalism, resulting in application delivery outgrowing the underlying network. This paper contributes an industrial retrospective of how the schemes and mechanisms for identification and location of network entities have evolved in traditional data centers and how they match cloud-native application requirements. Specifically, there is an evaluation of each application artifact that forced necessary changes in the identifiers and locators. Finally, the common themes are highlighted from observations to determine the investigation areas that may play an essential role in the future of cloud-native networking.

Cloud-Native Service Mesh Readiness for 5G and Beyond

“…Due to 5GC's microservices-based design, the communication volume between NFs is anticipated to increase significantly compared to previous generations. Combined with millions of concurrent signaling messages, this architectural model is not conducive to large-scale real-time deployments, as the probability of partial failure grows exponentially with system size [2].…”

“…This entails customizing responses for reasons such as access control, policy, or to optimize the connection between the consumer and provider. A strategy involves enhancing queries with meta-information, enabling clients to exchange their details for more accurate service information [2]. The service discovery can then fine-tune its answers, offer improved estimations, or even decline connections, as illustrated.…”