(Phase Two – Application Arch) Strategy to migrate Software Applications to Cloud

Series:

·        (Prologue) Strategy to migrate Software Applications to Cloud

·        (Phase One – Strategy) Strategy to migrate Software Applications to Cloud

·        (Phase One - Architecture) Strategy to migrate Software Applications to Cloud

·        (Phase One – Monitoring) Strategy to migrate Software Applications to Cloud

·        (Phase One – DevOps) Strategy to migrate Software Applications to Cloud

·        (Phase One – Security) Strategy to migrate Software Applications to Cloud

·        (Phase One – Performance) Strategy to migrate Software Applications to Cloud

·        (Phase One – Testing) Strategy to migrate Software Applications to Cloud

·        (Phase One – Plan) Strategy to migrate Software Applications to Cloud

·        (Phase Two – Strategy) Strategy to migrate Software Applications to Cloud

·        (Phase Two – EA Integration) Strategy to migrate Software Applications to Cloud

·        (Phase Two – Application Architecture) Strategy to migrate Software Applications to Cloud

·        (Phase Two – DevOps) Strategy to migrate Software Applications to Cloud

·        (Phase Two – Testing) Strategy to migrate Software Applications to Cloud

·        (Phase Three) Strategy to migrate Software Applications to Cloud

 (Disclaimer: The manuscript is my personal view and is not affiliated to any groups or organizations)

In phase II application architecture needs to contemplate about consuming more PaaS services and or moving towards PaaS based infrastructure deployment services. Both Azure and AWS provides numerous PaaS services, consuming the appropriate ones should be the center piece of this phase. Each layers of the applications along with the software stacks should be evaluated and replaced. Don’t forget to evaluate ancillary platforms such as DW or BI.

Continue the same level of vigor that commenced in the first phase of eager to learn and apply the technologies. Emphasize that collaboration is crucial to successful of an efficient Cloud deployment.

Azure Redis Cache or AWS Elastic Cache should replace memcached in IaaS VMs. Azure Search (or AWS CloudSearch) should replace custom text based searches. Azure DocumentDB or Azure Table(or AWS SimpleDB) should replace NoSQL based DBs. Azure SQL DB or ClearDBs MySQL DB (or AWS RDS) should take place of IaaS MySQL DB. For Oracle (or any other DBs for which there is no PaaS), Azure Oracle image should be used to setup Oracle RAC in IaaS VMs. Use Azure Service Bus or Azure Queue (or AWS SQS) instead of own Queue infrastructure in VMs. Use Azure HDInsight (or AWS Redshift) instead of custom Hadoop cluster in IaaS VMs. Caution try not to change the processes. Try not to introduce additional services which directly doesn’t address current infrastructure or software stacks (application and DW).

 

Azure has two different flavors of PaaS based infrastructure deployment services. Please note AWS has very limited capability (AWS Beanstalk) in this arena. Azure Cloud Service and Azure Website are two different flavors. Azure Website is the ultimate form of PaaS. Evaluate the application if it use Website or CloudService in that order.

Goal is to move to PaaS infrastructure (in case of Azure) and consume PaaS services instead of own managed services.