Ajay Budhraja Cloud Big Data

cloudbigdataajaybudhraja

Subscribe to cloudbigdataajaybudhraja: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get cloudbigdataajaybudhraja: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Ajay Budhraja Cloud Big Data Authors: Greg Schulz, William Schmarzo, Paresh Sagar, Jason Bloomberg, AppDynamics Blog

Related Topics: Microservices Journal, cloudbigdataajaybudhraja

Article

NFV Microservices | @CloudExpo #DevOps #SDN #Docker #Microservices

Embrace a Microservices Application Architecture

As AT&Ts VP of Domain 2.0 architecture writes one aspect of their Domain 2.0 strategy is a goal to embrace a Microservices Application Architecture.

One page 9 they describe how these envisage them fitting into the ECOMP architecture:

"The initial steps of the recipes include a homing and placement task using constraints specified in the requests. ‘Homing and Placement' are micro-services involving orchestration, inventory, and controllers responsible for infrastructure, network, and application. The goal is to allow algorithms to use real-time network data and determine the most efficient use of available infrastructure capacity."

This was a scenario industry expert Tom Nolle envisaged, and vendors like Ciena have re-engineered their telco platform offering accordingly.

This last point highlights how they will interface with the DCAE big data smart management framework.

"Analytic applications are developed by various organizations, however, they all run in the DCAE framework and are managed by the DCAE controller. These applications are micro-services developed by a broad community and adhere to ECOMP Framework standards."

Cloud Transformation - From Monolith to Microservices
These goals highlight how they face the same challenges that every organization faces who want to embrace Microservices: Creating new apps is relatively easy, factoring in your existing legacy applications is an entirely different, very difficult challenge - A shift from ‘Monolith to Microservices‘.

As AT&T describes:

"The BSS transformation to support the dynamic D2 environment is based on the following: Building blocks - BSS migration from monolithic systems to a platform building block architecture that can enable upstream User Experience (UX) changes in how products are sold, ordered, and billed."

These service elements lead us into the final aspect of the AT&T program, their anticipated Business Transformation.

Page 24 provides a complete overview of the departmental functions they expect to require some form of modernization to reflect this new platform capability, such as Sales, Marketing and Billing capabilities.

"D2-based Offer/Products will be designed, created, deployed and managed in near real-time, rather than requiring software development cycles. ECOMP is the framework that provides service creation and operational management of D2 which enables significant reductions in the time and cost required to develop, deploy, operate and retire AT&Ts products, services and networks.

The Business Support Systems which care for such capabilities as sales, ordering, and billing will interact with ECOMP in the D2 architecture, and those systems will need to pivot to this new paradigm."

The post Business transformation for NFV Microservices appeared first on Cloud Best Practices.

More Stories By Cloud Best Practices Network

The Cloud Best Practices Network is an expert community of leading Cloud pioneers. Follow our best practice blogs at http://CloudBestPractices.net