We are planning to migrating the DB from ON prem to AWS . But I know that the connections gonna throttle when my app connections crossed beyond 200/sec. We do use in our application mysql connection pool manager. But I really don’t want to restrict the connections for 200. cuz currently our app is opening 1000+ connections(doesn’t mean they all are getting used up). As far as my understanding based upon my previous implementation, IAM authentication is only for small applications but not for real big prod work load. I want to re confirm my understanding/conclusion is right .

We are planning to migrating the DB from ON prem to AWS . But I know that the connections gonna throttle when my app connections crossed beyond 200/sec. We do use in our application mysql connection pool manager. But I really don’t want to restrict the connections for 200. cuz currently our app is opening 1000+ connections(doesn’t mean they all are getting used up). As far as my understanding based upon my previous implementation, IAM authentication is only for small applications but not for real big prod work load. I want to re confirm my understanding/conclusion is right .

We are planning to migrating the DB from ON prem to AWS . But I know that the connections gonna throttle when my app connections crossed beyond 200/sec. We do use in our application mysql connection pool manager. But I really don’t want to restrict the connections for 200. cuz currently our app is opening 1000+ connections(doesn’t mean they all are getting used up). As far as my understanding based upon my previous implementation, IAM authentication is only for small applications but not for real big prod work load. I want to re confirm my understanding/conclusion is right .

We are planning to migrating the DB from ON prem to AWS . But I know that the connections gonna throttle when my app connections crossed beyond 200/sec. We do use in our application mysql connection pool manager. But I really don’t want to restrict the connections for 200. cuz currently our app is opening 1000+ connections(doesn’t mean they all are getting used up). As far as my understanding based upon my previous implementation, IAM authentication is only for small applications but not for real big prod work load. I want to re confirm my understanding/conclusion is right .

We are planning to migrating the DB from ON prem to AWS . But I know that the connections gonna throttle when my app connections crossed beyond 200/sec. We do use in our application mysql connection pool manager. But I really don’t want to restrict the connections for 200. cuz currently our app is opening 1000+ connections(doesn’t mean they all are getting used up). As far as my understanding based upon my previous implementation, IAM authentication is only for small applications but not for real big prod work load. I want to re confirm my understanding/conclusion is right .

We are planning to migrating the DB from ON prem to AWS . But I know that the connections gonna throttle when my app connections crossed beyond 200/sec. We do use in our application mysql connection pool manager. But I really don’t want to restrict the connections for 200. cuz currently our app is opening 1000+ connections(doesn’t mean they all are getting used up). As far as my understanding based upon my previous implementation, IAM authentication is only for small applications but not for real big prod work load. I want to re confirm my understanding/conclusion is right .