BCWeb was originally developed as a Sharepoint application, highlighting another decision possibility for migrating legacy apps to the Cloud, in that a ‘lift and shift’ option is possible, through migrating on-premise Sharepoint to Azure-based Sharepoint hosting ((https://social.technet.microsoft.com/Forums/en-US/bad2acb2-0eda-4947-86f8-9325e7f21a0c/move-sharepoint-onpremise-to-azure?forum=sharepointgeneral)), or even to Office 365.
In the case of this project they moved away from Sharepoint and re-built a new application based on PaaS, describing the mapping of Sharepoint functions to their modernized equivalent on Azure:
- Web-based user interfaces mapped directly to Azure web roles.
- WCF (Windows Communication Foundation) Services and background processes were split into two worker roles (Web and worker roles explained by TechTarget).
- SQL Server database mapped to Azure SQL Database.
This approach delivered business benefits including:
- Increased performance and stability – Traffic loads for the prior Sharepoint-based system had exceeded what the infrastructure could handle, and it became unstable and went offline during peak usage times at month ends, and attempts to alleviate the issue such as load balancers and architecture improvements failed to remedy the situation. Moving to Azure applied Cloud-scale capacities that eliminated the issue.
- Cost savings / avoidance – Eliminated the requirement to procure and maintain servers.
- Best practices and reusable components – The team developed practices and components to support the migration that other Azure projects could benefit from.
An example of the benefits of growing best practices is the second of the application case studies.
The ‘Connect’ application was used for employee performance reviews and ran on a large web cluster that sat idle for much of the year, because of the infrequent schedule of conducting the reviews. Not only were they able to also migrate this app to an elastic Cloud supply that easily scales to service more than 120,000 employees and eliminate the servers, but the new app was built from scratch in only four months.
Secure, Real-time Architecture
The third case study for the ‘Paystub’ application highlights the serious issues that some poorly architected legacy applications can cause. In this case it pulled and maintained a local copy of personal data, presenting privacy and security risks and requiring batch job synchronization, causing data latency problems.
Furthermore the business logic was programmed directly into the user interface, so even the smallest of business workflow-level changes required source code reengineering and distribution. The application also required a dedicated server cluster.
So again migrating to Azure eliminated these hardware costs, but more importantly enabled architecture modernization that also eliminated the more severe issues caused by the poor design model, making possible a single data source, real-time approach.
Delivering Business Value
The ‘Returns Service’ was how Microsoft customers would arrange for the return of products via the online and retail stores. It was painful for customers because it was manual, slow and sometimes introduced errors such as assigning refund credit incorrectly. Customers had to wait 24 hours to receive a shipping label.
Therefore in this case migrating the app to Azure delivered customer value. Integrating with the online store it enabled self-service submitting of return requests, eliminating the delays and errors and greatly improving the customer experience.
- Microservices on AWS - April 28, 2018
- AWS re:Invent 2017 Keynote – Werner Vogels - April 9, 2018
- Sharepoint to Azure Transformation - April 6, 2018
- Cloud Transformation: Migration and Modernization - April 6, 2018
- Cloud Native at AWS – Adrian Cockcroft, Amazon Web Services - January 21, 2018
- Mark Russinovich – Azure Container Service - January 21, 2018
- AWS Digital Government – Innovation and Transformation - January 18, 2018
- Tasktop – Value Stream Architecture - November 27, 2017
- Accenture – Open Source DevOps - November 27, 2017
- AWS – Enterprise Cloud Adoption Maturity - November 27, 2017