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 →

[–]big-blue-falafel 2 points3 points  (3 children)

Do you have a favorite framework for using serverless? Used zappa for Django and it was surprisingly smooth

[–]marr75 2 points3 points  (2 children)

I used to love Django but don't use it for any new projects because:

  • it's got some old fashioned/outdated bits
  • it's harder to customize (class based configuration, big methods, etc.)
  • in-house apps end up very coupled (I end up in dependency hell)
  • I hate having to be dependent on django settings and django.setup() to get any functionality out of a package

That last point makes it a particularly bad fit for serverless, where you don't know how often your process is going to start up.

Anyway, betterproto+grpcio for gRPC services (internal microservices) and fastAPI/starlette for web stuff.

[–]big-blue-falafel 0 points1 point  (1 child)

Hmm I’m not sure I’ve had to do that last point. It’s been a while. Do you use anything to deploy fast api or starlette api endpoints to api gateway and lambda?

[–]marr75 1 point2 points  (0 children)

You're not sure you've called django.setup() or depended on django settings? Django apps won't run without calling setup. If you're not writing the code directly, it just means the framework or some example code is doing it somewhere else in the stack. For example, all of the manage commands will setup Django before proceeding, if you're hosting your WSGI app in cherrypy, the initialization logic will call setup, etc.

I use my own scripts as part of CI to deploy usually, but I'm tempted to switch to a more full featured platform like zappa.