Question about this Quickstart compared to quickstart-microsoft-sql

[sql-sith]

Did this replace quickstart-microsoft-sql? I don't see that one anymore. We customized that one to deploy availability groups into EC2 instances in multiple regions, which we turned into read replicas of our on-premise availability groups.

Is this architecture capable of supporting enterprise-critical, high traffic OLTP workloads (averaging around 20k/second)? And can it serve as a read replica in AWS until we flip the table copy into AWS?

I'm asking because this looks easier to maintain, and possibly cheaper, even though storage has less redundancy.

I'm not looking for a full-on consult here. I'm just curious if this is worth bringing up with our TAMs as a possibly better/cheaper architecture than the full EC2-based solution we have more, and that friends on its scalability, reliability, and ability to participate in availability groups.

If there's somewhere I can read up on all of this, is appreciate that in addition to your feedback.

Thanks!

Thanks!