|
|
|
|
|
by cogman10
247 days ago
|
|
Exactly. I've always found that how people want to use lambda is the exact opposite of how to use it cost effectively. I've seen a lot of people want to use lambdas as rest endpoints and effectively replace their entire API with a cluster of lambdas. But that's about the most expensive way to use a lambda! 1 request, one lambda. Where these things are useful is when you say "I have this daily data pull and ETL that I need to do." Then all the sudden the cost is pretty dang competitive. |
|
All the backend processing and just general 'glue' in your architectures