The magic of cloud computing in which a solution creates problems for which solutions are provided. A forest of options that let's the non-technical indiehacker get lost before entering.
Working for ages in IT now, I once came to the realization that I get paid to know stuff that is important to know but nobody wants to know.
Anyway, thanks for the link. It makes totally sense to consider the RDS proxy for a Django Lambda scenario.
Decent guide. Great work with this one, Kostja 🤝
Thanks, Alexander! Positive feedback keeps me going :)
Thanks for adding the screenshots, they were helpful.
With the level of mess that AWS Panel is - screenshots are must :D
nice. I'm considering to deploy my next Django app as a Lambda function. That would solve the problem where to store the app database.
fyi, if you use Postgres + Lambda then you probably also want to use RDS Proxy https://aws.amazon.com/blogs/compute/using-amazon-rds-proxy-with-aws-lambda/ , otherwise you could hit a postgres limit with too many connections.
The magic of cloud computing in which a solution creates problems for which solutions are provided. A forest of options that let's the non-technical indiehacker get lost before entering.
Working for ages in IT now, I once came to the realization that I get paid to know stuff that is important to know but nobody wants to know.
Anyway, thanks for the link. It makes totally sense to consider the RDS proxy for a Django Lambda scenario.