`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.
Thanks! I actually built this more as a migration tool for teams moving from other languages to Go. From experience, dealing with tech debt and scalability limits in older stacks can be painful. The plan is to extend it into an all-in-one solution that also handles schema evolution and regeneration smoothly.
I used to work in Salt Lake, it's a really weird place. Very jarring with all the glass buildings that heat up the place, and horrible connectivity to the main city (in terms of public transport).