[bob1029]

I totally concur with the approach of building your own internal tools like this. There is a lot of technical value (and also some unique risks) with DIY tooling that is not usually apparent to the business owner. Being able to expose new APIs and interface things together with other parts of your business in new and open ways is a very powerful and compelling capability. Just knowing that you can do these things in the future is a powerful tool, as it keeps developers' minds more open to consider new integration and automation possibilities. Sure, most turn-key solutions offer some degree of an API and integration options, but if you control the source and CI/CD pipeline of your tools, it's a completely different ball game. I am sure most of us are acutely aware of the downsides of relying on 3rd party APIs at this point.

Also, Sqlite is a database engine to be seriously reckoned with if you know how to run a few magic PRAGMAs on your initial connection. I am still in awe of what can be achieved in terms of throughput and latency by a single connection on a WAL-journaled Sqlite db. If you don't need your app or service to scale beyond a single process per logical deployment, I cannot see any justification for using another engine.