Is it safe to cross the streams (er, cloud providers)?

Drew Schillinger - Dec 14 '21 - - Dev Community

Hello, fellow technophiles!

I'm tasked with rearchitecting an existing app for a start-up. There are 3 top priorities: speed to rebuild a crippled tech stack and created needed functionality, stability to said crippled stack as we are currently wooing investors and clients, and security: build the new stack right (and right now).

The former team mismanaged a DotNet stack on Azure (like, think diaper fire mishmash of misused VMs and outdated sdks/packages), and I have a ton of confidence and experience in AWS space.

If I were to say "let's take a 6-week hiautus), I and the other dev could rebuild what they have now with a pgsql, documentdb, and some lambdas in node or python or go. But the reality is we will be using the current dotnet stack until we've moved over to a new one (and likely using both as new features will be built in new Thing-X).

All that said, what is y'alls experience in coming in new and rebuilding better?

My concern in holding steady on Azure and building new on AWS mirror's Egon's warning about crossing the streams: "Try to image all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light."

Thank you for any advice, or for at least listening as I get my thoughts out on e-paper.

Excelsior!

DoctorEw

. . . .
Terabox Video Player