5 ms·
The question strikes me as odd. I can't imagine why one would split an API across separate isolated compute nodes. I've used isolated functions in the context o
by intrasight 3y ago
The question strikes me as odd. I can't imagine why one would split an API across separate isolated compute nodes. I've used isolated functions in the context of "message orchestration" scenarios, but I'd never do that for an API.
- anentropic 3y agoCan't help thinking that a lot of best practice advice from AWS coincidentally maximises your AWS lock-in and billing spend
- theshrike79 3y agoI've talked to actual AWS representatives face to face. Every time they tell us how we can spend less money. I've had one tell me that don't try to use this service, it won't work on your use case and if you try to force it, it'll cost you too much to be viable.
- mastazi 3y agoHere's an example: I have one workload that needs more RAM because it will parse some big CSV. So this is in its own lambda with different memory settings. Another example could be permissions granularity (each lambda can have its own IAM role). For example one of your lambdas could have access to something in Secrets Manager. There are also disadvantages to this approach, for example build times and deployment times.