serverless-dotenv-plugin
serverless-wsgi
serverless-dotenv-plugin | serverless-wsgi | |
---|---|---|
1 | 3 | |
344 | 487 | |
- | - | |
2.4 | 4.8 | |
4 days ago | 2 months ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
serverless-dotenv-plugin
-
Major changes to serverless-dotenv-plugin
The biggest impact with these changes is that plugins will not get initialized until after env variables are resolved. This meansserverless-dotenv-plugin is no longer able to load environment variables in time for them to be used in your service file (i.e. serverless.yml). However, the plugin will continue to load environment variables into all your functions using dotenv.
serverless-wsgi
-
Serverless Templates for AWS and Python
I hope your head is not spinning. Now you might think, Wait, I have a Flask or my Django app where the framework is taking care of the endpoints in my python code. Do I need to recreate several lambdas? A valid question. Luckily, there is also an awesome Plugin for that.
-
AWS is playing chess, Cloudflare is playing Go
> But two years from now CloudFlare could be doing the exact same stuff Amazon is doing now, and customers are locked in again, because no source code.
I hear this argument often but it always rings hollow.
A friend had a first gen iPod – when he wanted to switch, he discovered that the music he bought on iTunes couldn't be moved anywhere else because of DRM. That's lock in.
But this morning I was looking at the source code of an app built against the Serverless framework[1] and what I'm seeing is a bog standard WSGI application that uses a library to transform the inbound AWS "proprietary bits" into WSGI[2]. I'm not worried about lock-in there because all API Gateway + Lambda do is "translate an HTTP request into a JSON object and toss it to an app"[3] – what source code am I missing? The underlying Lambda/APIGW code? OK, but do I need it to run it myself? Not really.
Many – most? – AWS products tend towards this analysis. S3 is so locked in that, what, we now have multiple very high quality alternatives that are API compatible?
The real risk of cloud vendor lock in, from where I sit, comes from egregious pricing models that make it cheap to get data in & expensive to push data out. But I'm not sure Cloudflare has the juice to make this play work: egress pricing is essentially free money for AWS, so they've got lots of room to cut costs there – from what I've heard from people who negotiate real bills with AWS, they're very happy to give you discounts there.
[1]: https://github.com/serverless/examples/tree/master/aws-pytho...
[2]: https://github.com/logandk/serverless-wsgi
[3]: https://docs.aws.amazon.com/apigateway/latest/developerguide...
-
Does API Gateway replace web frameworks?
using https://github.com/logandk/serverless-wsgi
What are some alternatives?
serverless-python-requirements - ⚡️🐍📦 Serverless plugin to bundle Python packages
examples - Serverless Examples – A collection of boilerplates and examples of serverless architectures built with the Serverless Framework on AWS Lambda, Microsoft Azure, Google Cloud Functions, and more.