Sponsored By: Wind River
Service Portability is a major concern with new edge-centric architectures. This isn’t a surprise as operators need the flexibility to apply cloud native principles to shift services between a device, local cluster, or the cloud as they scale services at the edge.
Cloud-native methodologies have been discussed extensively when it comes to building cloud-native applications. In contrast, cloud native services have
been written about much less frequently, which is why this article is necessary to clarify what they are, how they differ from cloud-native apps, and why they’re important. It comes down to what is on the other end of cloud-native technology.
If it’s the user, such as in the chat use case, then it’s an application. But if it’s another program, like when that chat app interacts with an online database such as Amazon’s DynamoDB or Azure SQL to store messages and chat logs, then it’s a cloud native service.
In any event, there are common best practices for both use cases. But what’s most important is how a cloud-native mindset contributes to developing services in an edge-centric architecture. That’s because the definition of cloud-native services continues to evolve, which means there must be continuing evolution of service integration and delivery.