Journey of an on-premise web application to cloud

This post is helpful to guide any person/ organization who have their web application hosted on-premise or on some vendor servers and have futuristic view that they see their user base to grow in coming future. It's understood that initially it would sound difficult to move an application to cloud because we do not know if our application is fit to run on cloud. 

The phases below show approach that a Cloud Architect would adopt to migrate a web application hosted on non-cloud environment to cloud.

Phase I 

[Initial adoption phase to understand if our application can run on cloud] 

Phase II 

[Now that application runs and we are happy, adopt the best practices of Cloud computing] 

Phase III 

[Try adopting to Cloud services] 

Phase IV 

[Cost cutting] 

* Lift and shift the application as is into Docker and push to cloud. 

* Backend database into separate EC2 instance. 

* Deployment pipeline. 

*Break big application into smaller chunks, Microservices to be introduced for most of the transaction to enhance performance.  

* Microservices wrapped in containers. 

* Introduce communication channel between components like RabbitMQ or SNS/SQS  

* ELK for storage of logs, analysis and visualization for application and infrastructure monitoring, faster  troubleshooting, security analytics, etc. 

* Check for Cloud services for Middleware, replacing your backend DB with RDS. 

* Make use of Adapters that connects to Cloud services, shielding our application from a Cloud specific API. 

* Define the minimum required instances [Dedicated/ Reserved capacity], based on this information connect with Cloud provider and have a contract defined. 

Comments

Post a Comment

Popular posts from this blog

Database Server administration concepts for Architects/ Tech Leads/ Database developers

Most of us must have heard of Database replication/ mirroring but few of us would have tried to explore the details. This article explains about these concepts which would give you an overall understanding of Database server concepts which are used for large applications. What is Database Mirroring? Database mirroring is a primarily software solution for increasing database availability. It maintains two copies of a single database that must reside on different server instances of SQL Server Database Engine. What is Database Replication? It is a set of technology for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency. Using replication, you can distribute data to different locations and to remote or mobile users over local and wide area networks, dial-up connections, wireless connections, and the Internet. Most of the development community think that above two mentioned questions
Read more

Shared Nothing Architecture (SN Architecture) and Sharding database

  SN Architecture : A shared  nothing architecture (SN) is a distributed computing approach in which each node is independent and self-sufficient, and there is no single point of contention required across the system.   This means no resources are shared between nodes (No shared memory, No shared file storage)   The nodes are able to work independently without depending on each other for any work.   Failure on one node affects only the users of that node, however other nodes continue to work without any disruption.   This approach is highly scalable since it  avoid  the existence of single bottleneck in the system. Shared nothing is recently become popular for web development due to its linear scalability. Google has been using it for long time.     In theory, A shared nothing system can scale almost infinitely simply by adding nodes in the form of inexpensive machines.   Sharding:   is  an  architectural approach that distributes a single logical database system into a cluster of mac
Read more

Log shipping vs Mirroring vs Replication for Data Architects/ DBAs

Log  Shipping:   It automatically sends transaction log backups from one database (Known as the primary database) to a database (Known as the Secondary database) on another server. An optional third server, known as the monitor server, records the history and status of backup and restore operations. The monitor server can raise alerts if these operations fail to occur as scheduled.     Mirroring:   Database mirroring is a primarily software solution for increasing database availability.   It maintains two copies of a single database that must reside on different server instances of SQL Server Database Engine.   Replication:   It is a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency. Using replication, you can distribute data to different locations and to remote or mobile users over local and wide area networks, dial-up connections, wireless connections, and the Intern
Read more