liblifthttp VS sqldb-logger

https://github.com/jbaldwin/liblifthttp

I created a C++17 HTTP client which is backed by curl and libuv (linux only! sorry windows). I think a lot of people have done this or something similar but almost all of the ones I looked at either exposed the curl api directly in some fashion or had extremely weak async support. So my main motivation was extremely easy asynchronous queries for high throughput with a very modern C++ API that has as good as you can get memory safety, or at least as good as modern C++ will let you get. No raw curl calls or api exposed at all. I used to find it extremely difficult to make C++ HTTP calls, now its a real breeze.

My next project is a bit more ambitious: https://github.com/jbaldwin/libcoro/ -- I'd like to make a C++20 HTTP client from the ground up with first class coroutine support, and I'll be using lift as a benchmark to beat performance wise.

You can use this to get instant query logging for sql.DB. https://github.com/simukti/sqldb-logger

sqldb-logger: https://github.com/simukti/sqldb-logger

It's a thin layer that wrap Go (Golang) SQL database driver, it does not change sql.DB usage in any existing Go app.

It is because I prefer to use vanilla Go sql.DB in my web service and I could not find any SQL logger for Go SQL database standard library that can use structured JSON logging.