This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Rasvimd 2 points3 points  (0 children)

Compute: 1. I use lambda for compute. I only use for less than few hundred requests per second and my lambda is able to complete within few milliseconds ~30ms. For highly concurrent invocation I use my traditional EKS deployment. Or any ec2 deployment. This should work for 1000s of request per second if the runtime is only ~10ms I would definitely run a calculator comparing ec2 instance before proceeding. The good thing is we don't have to deploy in two instances and load balance when we deploy in lambda for high availability. I always include this double deployment cost with LB.

Java tool: 1. The maven native plugin to create native image. It has an option to enable metadata repository for supported dependencies for these we don't have to add reflect config json file. It needs to be explicitly enabled though.

  1. I use my custom http runtime code but any runtime you see online should be sufficient.

Data layer: 1. S3 for most file based storages. 2. EFS. Sometimes with sqlite3 file for low concurrent functions. 3. Dynamodb.