asked on

AWS (Amazon Web Services) Migration Reliability Engineering Help for Platform Engineering for AWS .NET Architecture

I need some key considerations regarding an application migration.

Current architecture: Application built on .NET framework deployed on Windows Servers in AWS.

Future architecture: Application built on .NET Core running on Linux Docker containers deployed using AWS Elastic Container Service.

The application is a mobile application (iOS and Android along with Web access) that allows customers to transfer money to other individuals.

Current flow:

Mobile App --> AWS API Gateway --> Load Balancer --> AWS ECS/Docker --> Rabbit MQ running on AWS EC2 Linux. There is also an API that feeds AWS Lambda as well as a mobile API that feeds into Rabbit MQ and the backend databases.

We have AWS Aurora and Redis running on the backend. I need to be able to migrate and deploy this future architecture into production with no platform downtime in a reliable fashion while minimizing any impact to customers that are using the platform.

ASKER CERTIFIED SOLUTION

Shalom Carmel

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dean Cantave

ASKER

Shalom, thank you kindly for chiming in with your expertise. Any differences or perhaps preferences in functionality, ease of use, etc. between using Cloudformation and Terraform? Obviously Cloudformation is native to the platform but I do think Terraform has it's pro's being an IaaC platform that can be used outside of AWS. Also, is there anything specific you can point to that needs to be considered once the environment is operational? Any particular DevOps considerations??