Ask HN: AWS lambda pricing/lock-in concerns
We are building a data analysis app, and AWS lambda seems to offer a scalable, secure, and easily administrable engine for the computationally-intensive parts of the app. The pricing structure is reasonable for now, but we are uneasy about becoming dependent and locked into lambda, should the pricing change dramatically in the future (this is Amazon, after all). Is this a valid concern? And, if so, how can it be mitigated? 1 comments on Hacker News.
We are building a data analysis app, and AWS lambda seems to offer a scalable, secure, and easily administrable engine for the computationally-intensive parts of the app. The pricing structure is reasonable for now, but we are uneasy about becoming dependent and locked into lambda, should the pricing change dramatically in the future (this is Amazon, after all). Is this a valid concern? And, if so, how can it be mitigated?
We are building a data analysis app, and AWS lambda seems to offer a scalable, secure, and easily administrable engine for the computationally-intensive parts of the app. The pricing structure is reasonable for now, but we are uneasy about becoming dependent and locked into lambda, should the pricing change dramatically in the future (this is Amazon, after all). Is this a valid concern? And, if so, how can it be mitigated? 1 comments on Hacker News.
We are building a data analysis app, and AWS lambda seems to offer a scalable, secure, and easily administrable engine for the computationally-intensive parts of the app. The pricing structure is reasonable for now, but we are uneasy about becoming dependent and locked into lambda, should the pricing change dramatically in the future (this is Amazon, after all). Is this a valid concern? And, if so, how can it be mitigated?
Hacker News story: Ask HN: AWS lambda pricing/lock-in concerns
![Hacker News story: Ask HN: AWS lambda pricing/lock-in concerns]()
Reviewed by Tha Kur
on
June 30, 2018
Rating:
No comments: