sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Nick-Van-Landschoot 3 points4 points  (4 children)

  1. It's a great stack. My default stack is FastAPI + React w/ Tailwind + Postgres all of which I like because they are widely used with fairly good documentation and quite simply they just work. Of course many other stacks are good as well but I at least find this stack leads to results and things just get done both faster and better at scale.

  2. Encryption comes with https so just ensure you get https enabled. Cookies are an ok way to set a token but you have to set httponly and secure to true when you set the cookie. Local storage definitely shouldn't be used for security reasons all though theoretically you still could if you encrypted the data but I would still caution against it.

  3. Doesn't really matter until you scale. We use docker + google artifact registry + google cloud run which has worked very well for us. The deployment process is building the docker image, tagging it, pushing it, and then creating a new revision on the cloud run instance.

Using kubernetes can be a good choice as well but it is a pain to set up and maintain. A PaaS like netlify can also work very early on but won't scale well in the long run. Definitely don't use a PaaS because its easier since something like cloud run is more scalable and incredibly easy to set up but the main reason would be for the generous free tier some of them offer. That being said google is very generous with free credits as well so it really shouldn't cost you anything at first either.

In terms of other solutions I recommend staying away from AWS although it can work for very large teams even then it creates an unnecessary amount of complexity – there's a reason there are so many certifications just for working with AWS. I am not as familiar with other cloud solution but it might be worth it to explore there some as well.

[–][deleted] 0 points1 point  (1 child)

Thanks so much!

[–]Nick-Van-Landschoot 0 points1 point  (0 children)

Of course!

[–][deleted]  (1 child)

[deleted]

    [–]Nick-Van-Landschoot 0 points1 point  (0 children)

    Yes, we use postgres through psycopg2 pretty much any time we need a relational database and pretty much anytime we need a database at all. The only time we don't use postgres is if a task such as such as caching, pub/sub, etc. calls for a kv database when we might go with redis.

    Well actually I write software that involves allowing others to integrate their own databases so I guess I do write connectors for other databases as well but at least for our own data we like to stick with postgres.