`pglite` is a WASM version of postgres. I use it in one of my side projects for providing a postgres DB running in the user's browser.
For most purposes, it works perfectly fine, but with two main caveats:
1. It is single user, single connection (i.e. no MVCC)
2. It doesn't support all postgres extensions (particularly postGIS), though it does support pgvector
I agree with you that this question is unanswerable verbatim. It sorta reminds me of how Agile came up the "Definition of Done"
System maintainers / stakeholders themselves need to come up with a "Definition of Working"
Since distributed systems are basically in some state of failure/degradation almost all of the time, it is useless to try to say that "the system is working when there are no errors anywhere".
Some sort of threshold needs to be arrived at where we can say "it's working".
What that threshold looks like is going to vary from project to project.
I'm not a fan of the enterprisey hexagonal-style code this generates, but I can understand where this might be useful for someone who does follow that.
A question regarding evolution: it's rare that schemas stay constant. I'm not sure if this tool will lend itself well when the time comes to, say, add another table, though I might be misunderstanding here.
When I was in high school, I was kind of into competitive programming. We wanted to conduct contests, but the labs didn't have internet access, so we couldn't use stuff like SPOJ/Codeforces.
To make it easier for our computer club to conduct small contests, I made a small application in Python that could display problems, accept submissions, and automatically grade them.
It had a horrible "single page" UI that used jquery to hide and show divs to switch pages, and obviously had 0 sandboxing, but it got the job done for our purposes.
A couple of years later, a CEO of a local startup was visiting my high school, and he happened to catch the program in action. His business had been struggling with a hairy Google Drive integration and he asked me if I had any ideas. That eventually led to a part-time offer, which became full time after I graduated.
So yeah, it was quite serendipitous. While the project wasn't directly related to my job, it did give me an in, even though the code quality was so shoddy it makes me shudder to even think about it now.