|
|
|
|
|
by jronald
3405 days ago
|
|
Your making value decisions based on expertise in your existing delivery methods and trying to map them 1-1 to aws features, that may or may not map 1-1. You keep disparaging aws' pricing (stupidly expensive, serious premium), without providing an alternative/baseline. Again, if you have numbers and not broad statements we'd appreciate them. |
|
eh, no. You have no idea about my areas of expertise, what features I require, or how I map them, or what I map them to, so you cannot make this kind of statement (well, you can, and you did, but it is a fallacy).
you have numbers and not broad statements we'd appreciate them.
I'm sure you do. Doing what I do today in terms of functional parity, but doing it on AWS, will work out roughly 2.5 times more expensive, and will not gain me any additional features or functionality, and will leave me with about two-thirds of reduction in overall performance against metrics that are of interest to me. Also "we"? You speak for others? Who are the "we" that have appointed you as their speaker?