Reliability for Netcracker active resource inventory on AWS - Netcracker Active Resource Inventory on AWS

Reliability for Netcracker active resource inventory on AWS

Netcracker active resource inventory on AWS is built with the ability to perform its intended function correctly and consistently when it’s expected to. Below a small overview of how Netcracker active resource inventory on AWS uses the five design principles for reliability in the cloud:

  1. Automatically recover from failure – As illustrated in above, Netcracker leverage Elastic Load Balancing to distribute load to an Amazon EKS Cluster in an Auto Scaling Group spawning multiple Availability Zones. Netcracker leverage Amazon CloudWatch and EKS inherent capabilities to automatically recover from pods failures.

  2. Test Recovery procedures – With AWS, Netcracker has the ability to use automation to simulate different failures and validate the recovery procedures. Netcracker uses automation and the AWS cloud capabilities to test and fix before a real failure scenario occurs, thus reducing risk.

  3. Scale horizontally to increase aggregate workload availability – Netcracker active resource inventory on AWS allows for using multiple small resources to reduce the impact of a single failure on the overall workload. As shown above, distributing requests across multiple, smaller resources to ensure that they don’t share a common point of failure.

  4. Stop Guessing Capacity – Netcracker active resource inventory on AWS allows for a solution that grows with the network demand and growth. AWS allows Netcracker to grow with the Network, where additional resources are spinned-off as the amount of inventory data flow into Netcracker active resource inventory. Similarly, it allows Netcracker to adapt its CPU and memory to the amount of inventory required at a given time. This is a complete opposite to on-premises workloads that often reach resource saturation.

  5. Manage change in automation – Changes to Netcracker active resource inventory is made through automation using AWS CloudFormation.

You can find prescriptive guidance on Implementation in the Reliability Pillar whitepaper.