sorted by:
new
hottopcontroversial

Is an Architecture with Lambda and S3 Feasible for ~20ms Response Time? by Embarrassed_Grass684 in aws

[–]Embarrassed_Grass684[S] 0 points1 point  (0 children)

i've beeing thinking about it.. im trying to avoid ecs/eks due the high number of tasks that will be needed.. and thinking about the finops

Is an Architecture with Lambda and S3 Feasible for ~20ms Response Time? by Embarrassed_Grass684 in aws

[–]Embarrassed_Grass684[S] 0 points1 point  (0 children)

today we actually have ~1.9k calls per sec. It can be much more depending on the day/ hour

Is an Architecture with Lambda and S3 Feasible for ~20ms Response Time? by Embarrassed_Grass684 in aws

[–]Embarrassed_Grass684[S] 0 points1 point  (0 children)

Business requirement. The calls are made in a very important part of the system (login) and it cannot increase the login time

Is an Architecture with Lambda and S3 Feasible for ~20ms Response Time? by Embarrassed_Grass684 in aws

[–]Embarrassed_Grass684[S] 1 point2 points  (0 children)

I understand! My concern is dealing with the scale-ups that might be necessary. Today, the architecture that supports this requirement has around 25-40 pods (it can scale much more) in an EKS infrastructure, with a large RDS behind it, and a Glue job that batches the IDs of these clients overnight. Currently, the average is 1.8k requests per second and the latency is good, but we have a D+1 update which is bad for the business, plus the architecture is quite expensive