Comment by TuringNYC

8 months ago

Not OP, but we originally migrated to Digital Ocean. But now, all complex stuff is on AWS and dual-stack stuff is on Replit.

4 comments

TuringNYC

Reply
gregsadetsky  8 months ago

and what did you use to manage git push deployments, setting env vars to replicate the heroku features?

also, you used replit for the frontend deployment? or frontend and some backend?

thanks - just super interesting as I'm in the space and feedback/real cases are really useful

  • TuringNYC  8 months ago

    >> and what did you use to manage git push deployments, setting env vars to replicate the heroku features?

    Yes Digital Ocean did all this, they were very feature-close to Heroku. We have over time migrated everything stable/prod to AWS just because AWS has more products and hence you have everything in one place inside a VPC (e.g. vector db)

    For Replit, i'd use it for anything I can in early-stages. It helps to prototype ideas you are testing. You can iterate rapidly. For PROD we'd centralize onto AWS given the ecosystem.

    • gregsadetsky  8 months ago

      cheers, I really appreciate your answers

      and last q :-) re AWS - once you moved there, did you use something like elasticbean or app runner? or did you roll your own CI/CD/logging/scaling...?

      1 reply →