I played with next/next-auth and what was appealing was how cheaply you could run an app.
one thing that i didn’t have time to look into is the latency profile when you manage sessions on your own with all the application logic on edge lambda functions and the database in one data center like us-east-1.
then i started experimenting with edge redis clusters that sit closer to the lambda functions, but that was a huge pain and still not as cheap as i wanted because the redis provider was charging per redis command.
i excited to play with aurora serverless v2 for postgres
True, this stack is very cost efficient for bootstrapping a project.
I'm sure you could optimize the latency with hosting yourself with aws lambda functions etc...
But the point is, if you're bootstraping a business, you should focus on what brings value to your customers :)
one thing that i didn’t have time to look into is the latency profile when you manage sessions on your own with all the application logic on edge lambda functions and the database in one data center like us-east-1.
then i started experimenting with edge redis clusters that sit closer to the lambda functions, but that was a huge pain and still not as cheap as i wanted because the redis provider was charging per redis command.
i excited to play with aurora serverless v2 for postgres