4 ms·

"Serverless" is a framework used by AWS: https://github.com/serverless/serverless https://github.com/serverless/serverless And it now supports Python. Would be

"Serverless" is a framework used by AWS: https://github.com/serverless/serverless https://github.com/serverless/serverless And it now supports Python. Would be interesting to see someone using AWS Serverless framework with Django Plugin support.

Mizza 11y ago
The point of this is that you don't need to learn any new frameworks - it works with your existing code. You can deploy your existing apps on Lambda without having to change anything, and you're not locked in to AWS if you want to go back.
- StavrosK 11y ago
  I rather doubt the "without changing anything" part. For example, I write static media to a subdirectory of my Django installation. Will that work without any changes? How about Django uploads? How about temporary files? Etc etc. I used to use Django-nonrel for GAE so I wouldn't be logged in, and guess what: By the time I wanted to move away, I had so much GAE-specific behaviour that I pretty much had to rewrite the app.
  - Mizza 11y ago
    Well you really shouldn't be serving static content through Django, you should be serving it through a CDN. If you use something like Django-Storages for uploads, it'll Just Work. I'm not guaranteeing that everything will work out of the box on the first try, but I bet you'll be very close. You will have to make a few design decisions, but if you're making the right ones it should just work. At the very least it should be far, far easier that GAE. (The one thing you'll have to watch out for are C-extensions, which, for now, require that you do your deployment from an x86_64 machine.)
    - StavrosK 11y ago
      > Well you really shouldn't be serving static content through Django, you should be serving it through a CDN The two aren't mutually exclusive. My CDN points to Django for retrieving the static media. > if you're making the right ones it should just work "If you're making the ones that Zappa requires", you mean. > The one thing you'll have to watch out for are C-extensions Eh, that's to be expected, though.

Mizza 11y ago

The point of this is that you don't need to learn any new frameworks - it works with your existing code. You can deploy your existing apps on Lambda without having to change anything, and you're not locked in to AWS if you want to go back.

StavrosK 11y ago
I rather doubt the "without changing anything" part. For example, I write static media to a subdirectory of my Django installation. Will that work without any changes? How about Django uploads? How about temporary files? Etc etc. I used to use Django-nonrel for GAE so I wouldn't be logged in, and guess what: By the time I wanted to move away, I had so much GAE-specific behaviour that I pretty much had to rewrite the app.
- Mizza 11y ago
  Well you really shouldn't be serving static content through Django, you should be serving it through a CDN. If you use something like Django-Storages for uploads, it'll Just Work. I'm not guaranteeing that everything will work out of the box on the first try, but I bet you'll be very close. You will have to make a few design decisions, but if you're making the right ones it should just work. At the very least it should be far, far easier that GAE. (The one thing you'll have to watch out for are C-extensions, which, for now, require that you do your deployment from an x86_64 machine.)
  - StavrosK 11y ago
    > Well you really shouldn't be serving static content through Django, you should be serving it through a CDN The two aren't mutually exclusive. My CDN points to Django for retrieving the static media. > if you're making the right ones it should just work "If you're making the ones that Zappa requires", you mean. > The one thing you'll have to watch out for are C-extensions Eh, that's to be expected, though.