Cloud-native from ground up

CatalogONE was built from the ground up as a cloud-native application on a microservices and domain-driven-design architecture, with the goal of ensuring high availability, flexibility, scalability, and resiliency, together with an easy deployment that has global reach and can be achieved with a single click.

To build CatalogONE, we used Microservices360 (MS360), the Amdocs’ microservices orchestration and operations platform that is based on a “best-of breed” open source tool selection, including Kubernetes and Docker, and which is integrated into a full end-to-end automated DevOps environment.

The MS360 framework provides well-defined and tested business process flows, and enables the microservices to be run over any cloud infrastructure. It abstracts server management and low-level infrastructure decisions from developers, freeing them to focus on new functionality and innovation.

Furthermore, each CatalogONE microservice is designed according to domain-driven-design and is developed independently. This enables smaller teams to be even more agile in launching frequent catalog releases by using more efficient development methodologies.

CatalogONE & AWS: Leveraging the #1 public cloud infrastructure

“The carrier-grade, microservices design of CatalogONE is ideal for harnessing the deployment power of the AWS Cloud. This combination enables service providers to accelerate the journey to the cloud and digital and to bring to market more innovative offerings, faster and at a lower cost.”
Jean-philippe Poirault, VP and Global Head of Telecom, AWS

While CatalogONE is designed to be cloud-agnostic, we found that there is a great demand from service providers worldwide for optimizing the solution to run on AWS.

Accordingly, CatalogONE is built in accordance with the AWS Well-Architected Framework, which means that it is built according to AWS guidelines and leverages native AWS IaaS and PaaS services, such as AWS EKS, Kafka, elastic search, and more.

Furthermore, the application supports the Amazon API gateway, and geo-deployment for catalog services, as well as the ability to use Amazon Spot instances for deploying temporary workloads, like testing, at a lower cost, and elastic load balancing for greater levels of fault tolerance in applications, and for seamlessly providing the required amount of load balancing capacity needed to distribute application traffic.