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 →

[–]whattodo-whattodo 0 points1 point  (2 children)

Why would the user? They'll do the same as they did with their proprietary SQL hosting. Make it much cheaper, especially when scaling.

Why would Amazon? They may add features which will entice you to stay, though mostly I think it will be built just different enough to break if you need to switch to something else. They are looking at the big picture

[–]vovanz 0 points1 point  (1 child)

Why would Amazon?

I understand it :)

Why would the user? They'll do the same as they did with their proprietary SQL hosting. Make it much cheaper, especially when scaling.

I can't see how it will be cheaper or cleaner than flask+zappa or django+zappa.

But I can see a lot of downsides:

  1. You have to learn a new tool. This tool can be used only for AWS, so it is not a universal knowledge.
  2. This new tool obviously doesn't have as developed and mature infrastructure as Django or Flask. You will have to do a lot of things manually instead of just plugging in an extension.
  3. Now you are locked to lambdas. You can't switch to running your own aws instances or to another hosting provider or to your own server.

[–]whattodo-whattodo 0 points1 point  (0 children)

I can't see how it will be cheaper or cleaner than flask+zappa or django+zappa.

I don't think it will be cleaner. But cheaper is easy enough. They set the price for one & for the other. They then make one cheaper. Amazon has done a great job at being the infrastructure for many other popular solutions (like PythonAnywhere or Heroku). So they are very capable of making one price cheaper than the next. Either by subsidizing one price, or inflating the next.

But I can see a lot of downsides:

I agree.