Migrating an on-premise, RMS application to Azure Cloud

One of the largest, not for profit charities in the US successfully deploys its RMS application to Azure Cloud.

By: Nitin Kulkarni
Architect, ennVee


Business Use Case – Migrating RMS application to Windows Azure

One of the largest Jewish, not for profit charities in the United States utilizes a Result Management System (RMS), web-based application deployed on-premise. In this white paper, we discuss migrating to Azure using this RMS as an example for both Windows Azure through Cloud services implementation models.

Download the full white paper here.

Current Architecture and Deployment Setup

  • Built with ASP.Net 4.5
  • Hosted on-premise in a data center on a single instance server.
  • Can be accessed from the internet.
  • Relies on Windows authentication to authenticate users.
  • Uses a standard Microsoft SQL Server 2008 database for storing application data.
  • Connects to the production databases using a service account.

Challenges

  • Highly manual maintenance due to the application residing on-premise and the database in a different server.
  • No automated system to show exceptions of the applications without looking into logs.
  • Deployment of new enhancements or issues is manual and requires third party config tools.
  • The existing application lacks a centralized navigation to browse different pages.
  • The existing application is not prepared to be scalable or integrate with any new systems in the future.
  • High risk of exposure of all user data due to a lack of role-based access.

Advantages

  • Moving to cloud provides greater ease and control in application maintenance through an intuitive dashboard.
  • Introducing an interactive maintenance dashboard makes both the application and database available in the same place.
  • All application and database exceptions can be tracked though Azure to reduce the amount of time spent identifying them.
  • The deployment of new enhancements or issues can be handled through IDEs like Visual Studio and requires significantly less configuration.
  • A completely centralized navigation is provided as part of the enhancement and upgrade, which delivers greater flexibility to move around the application.
  • The centralized navigation and role-based accessed enhancement provides more control on data exposure.

Download the full white paper here.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s