That doesn't really narrow it down very much. How many different entities, how complex are the filters, how frequent are the reads and writes?
When I was around 14 or something I started teaching myself relational databases with something called Paradox for DOS. For at least 15 years I went along with the assumption that real programmers use a relational database for just about everything.
When the NoSQL trend appeared and became wildly popular, it made me reconsider.
These days, if I can get away with using JSON files, then I just do that.
As far as the stack I usually use Node.js and JavaScript just because I have been doing it that way for so long. Recently some people specifically ask for Python.
Obviously, whether that will work depends on the project.
You often don't have a choice because the database is already built.
For many projects, there are multiple different approaches that would work fine.
I think for the future you will start to see languages that target web assembly becoming more and more popular for portability. Such as Rust and maybe some Rust competitor that has yet to become popular.
There will probably be some kind of popular web assembly runtime soon bundled with Postgres or something.
Or maybe someone will just build a Postgres extension that serves web pages running web assembly that can query Postgres.
When I was around 14 or something I started teaching myself relational databases with something called Paradox for DOS. For at least 15 years I went along with the assumption that real programmers use a relational database for just about everything.
When the NoSQL trend appeared and became wildly popular, it made me reconsider.
These days, if I can get away with using JSON files, then I just do that.
As far as the stack I usually use Node.js and JavaScript just because I have been doing it that way for so long. Recently some people specifically ask for Python.
Obviously, whether that will work depends on the project.
You often don't have a choice because the database is already built.
For many projects, there are multiple different approaches that would work fine.
I think for the future you will start to see languages that target web assembly becoming more and more popular for portability. Such as Rust and maybe some Rust competitor that has yet to become popular.
There will probably be some kind of popular web assembly runtime soon bundled with Postgres or something.
Or maybe someone will just build a Postgres extension that serves web pages running web assembly that can query Postgres.