* an OIDC identity provider so you don't have to make your own password system
* Redis for caching
* S3-compatible object storage (so you don't have to reinvent file uploads)
* The app itself
What would you rather them do? Waste time reinventing the wheel for no reason? If you have the IDP and object storage setup already figured out you can get away with just the app, postgres, and redis.
That's a typical tech answer. Do you really want to spin up 10 images for note taking for yourself? From a product standpoint that's not sensible and wastes way to much resources.
Are you sure? It’s a collaborative note taking application which is designed to support large groups.
A similar project we collaborate on has Helm charts as an option. “Are you mad? You run an online archive with how many pods, come again?” You may say.
“When said archive can handle a continent’s load and scale almost indefinitely, you engineer things differently”, I’ll answer.
Also, nobody will probably make this comment, if the said application was built by a private company and was not open source.
* Postgres for permanent storage
* an OIDC identity provider so you don't have to make your own password system
* Redis for caching
* S3-compatible object storage (so you don't have to reinvent file uploads)
* The app itself
What would you rather them do? Waste time reinventing the wheel for no reason? If you have the IDP and object storage setup already figured out you can get away with just the app, postgres, and redis.