Azure Billing Service

Background

This client has been experiencing a 30% per year growing over the past 04 years, and to maintain this success pathway, they are planning to expand their local country market to a global scenario. However, to achieve this objective they need to refactor the company’s main product.

These project was planned to be executed in several steps, since to build of new services to accommodate the new specifications; through to re-design the legacy LOB Software. The first step was to create a new Billing Service.

 

Problem

To build a Billing Service capable of to support the expectations to a new global market, in addition, to support the existing legacy systems.

 

Scope

This project was designed to be a Billing Service, excluding any accountancy objectives, which will still be supported by a SAP solution.

The solution must be Global, high-availability, scalable, estimating growing and prospecting new markets, with the lowest cost.

The client can access their finance statement; the partner’s developers can exchange information through an API, and the company can predict market behaviours.

 

Team

Three Software Architects designing this project, working together to solve the problem observing the scope requirements. Alexandre silva, Leonardo Machado, Euripedes Sobrinho.

 

The Design

Microsoft Azure was chosen to accommodate the solution. Azure Traffic Manager will be used to rout traffic between the datacentres involved, to provide a better latency and response time to customers.

To provide full access to entire service a WebAPI will be provided, in addition, to a WebApp Site, which will permit the client access to follow its financial statement. Both of them will be hosted in Azure Web Application, with auto scaling and Availability Sets, to ensure resiliency.

An Azure Service Bus will have to orchestrated the work Roles witch are responsible for the billing crude and consolidation, and also storage process. The messages will be stored in topic queues and then inserted into Azure DocumentDB. Another Azure Work role routine will consolidate data into Azure SQL Database.

Azure Search was chosen to find any data stored into the Azure DocumentDB, this provided a powerful search engine, providing easy developer scenarios through .NET SDK search API.

An Azure Virtual Machine hosting EMC Captiva Software will be responsible to do the CompTIA CDIA Standard Document processing pattern, changing images into valuable data using OCR technics.

The Azure Machine Learning will be used to predict new market scenarios, to prospect new markets niches, and provide information to a good company strategical decision.

 

Time

The project has been designed for 02 months, and the implementation phase planning had already begun.

 

Goals

After the full project implementation, the company expect consolidate its finance process into a solid and reliable platform, which is able to provide clients predictive and accurate behaviour perspectives.

 

Leave a Reply

Your email address will not be published. Required fields are marked *