Seastar VS cpp-httplib

I used glommio as the async executor (instead of something like tokio), and it is wonderful. For people wondering whether it's "good enough" or to use C++ and seastar (as I have thought about a lot before starting this project), take the leap of faith, it's fast - both in terms of run time and to code.

b) It's proven now e.g Seastar, Glommio that the fastest way to run a multi-threaded application is to have one instance with one thread pinned per CPU core. Then to have fibers/lightweight threads on top handling all of the asynchronous code. Your approach of lots of instances is the slowest so there will be a ton of unnecessary thread context-switching.

The most common example is DPDK [1]. It's a framework for building bespoke networking stacks that are usable from userspace, without involving the kernel.

You'll find DPDK mentioned a lot in the networking/HPC/data center literature. An example of a backend framework that uses DPDK is the seastar framework [2]. Also, I recently stumbled upon a paper for efficient RPC networks in data centers [3].

If you want to learn more, the p99 conference by ScyllaDB has tons of speakers talking about some interesting challenges.

[1] https://www.dpdk.org/.

[2] https://github.com/scylladb/seastar

[3] https://github.com/erpc-io/eRPC

I assume Tokio itself, see e.g monoio or glommio, but also Seastar for C++.

https://core.dpdk.org/supported/ lists supported nics. You're best just reading material from the dpdk website for figuring out roughly what it is. It is used for a lot of different goals. For most web C++ stuff it's mainly used because you can avoid round trips of data passing through the kernel and can reference network data without tons of copying. For an example check out the SeaStar framework, https://seastar.io/, which is under the hood of ScyllaDB.

As this is a Kafka sub, this may be a good opportunity to mention that Redpanda is based on the same framework (seastar) as Scylla. The idea of sharding work to CPU cores turns out to apply very well to the Kafka data model, too!

Seastar which is a thread per core runtime written by the Scylla devs thats used in both Redpanda and Scylla as the underlying runtime. https://github.com/scylladb/seastar

ScyllaDB is, ironically, maybe one of the worst examples the author could have come up with for "abstraction" in the article.

If folks aren't familiar with their work/internal tech, go check out some of their repos like Seastar. They have some of the most talented systems programmers on the planet writing thin veneers over kernel and hardware API's to squeeze every ounce out of performance.

https://github.com/scylladb/seastar

I know it's beside the point, but I just had to share because I thought that was funny

I’ve seen frameworks for c++ (https://seastar.io/) and rust (https://github.com/actix/actix) which support what you’re describing out of the box.

If you're interested in scaling and asynchronous programming in c++ I highly recommend you investigate the SeaStar application framework. You wouldn't build a web service with SeaStar, rather you would build the infrastructure that you would use to build the web service on top of. https://github.com/scylladb/seastar

Alternatives at the low to medium level of abstraction include civetweb and mongoose, which have a common ancestor. Both of these appear to be C rather than C++, but seem to be production quality and well-documented. Another C library is cpp-httplib, which is probably too low-level for me.

I use this all the time to expose an admin rest interface to my public installations.

I'm using this one: https://github.com/yhirose/cpp-httplib

Every one of these libraries uses CMake to make it easier for end users to consume their libraries. In fact your example uses CMake as well such that I can consume it the way I describe above.

# Template file for 'yuzu-mainline' pkgname=yuzu-mainline version=1295 revision=1 _cubeb_version=75d9d125ee655ef80f3bfcd97ae5a805931042b8 _sanitizers_cmake_version=aab6948fa863bc1cbe5d0850bc46b9ef02ed4c1a _dynarmic_version=bd570e093ca1d1206961296b90df65cda7de8e87 _sirit_version=d7ad93a88864bda94e282e95028f90b5784e4d20 _mbedtls_version=8c88150ca139e06aa2aae8349df8292a88148ea1 _xbyak_version=348e3e548ebac06d243e5881caec8440e249f65f _SDL_version=f17058b562c8a1090c0c996b42982721ace90903 _cpp_jwt_version=e12ef06218596b52d9b5d6e1639484866a8e7067 _cpp_httplib_version=305a7abcb9b4e9e349843c6d563212e6c1bbbf21 _Vulkan_Headers_version=00671c64ba5c488ade22ad572a0ef81d5e64c803 create_wrksrc=yes build_wrksrc=${pkgname}-mainline-0-${version} build_style=cmake configure_args="-DYUZU_CHECK_SUBMODULES=OFF -DYUZU_TESTS=OFF -DSIRIT_USE_SYSTEM_SPIRV_HEADERS=ON" hostmakedepends="pkg-config qt5-host-tools qt5-qmake clang" makedepends="fmt-devel libenet-devel inih-devel libusb-devel liblz4-devel opus-devel zlib-devel libzstd-devel boost-devel qt5-devel qt5-multimedia-devel libva-devel ffmpeg-devel glslang-devel SPIRV-Headers catch2 json-c++ speexdsp-devel" short_desc="Nintendo Switch Emulator" maintainer="Owen Law " license="GPL-3.0-or-later" homepage="https://github.com/yuzu-emu/yuzu-mainline" changelog="${homepage}/releases/tag/mainline-0-${version}" distfiles="${homepage}/archive/refs/tags/mainline-0-${version}.tar.gz https://github.com/herumi/xbyak/archive/${_xbyak_version}.tar.gz https://github.com/MerryMage/dynarmic/archive/${_dynarmic_version}.tar.gz https://github.com/yuzu-emu/mbedtls/archive/${_mbedtls_version}.tar.gz https://github.com/mozilla/cubeb/archive/${_cubeb_version}.tar.gz https://github.com/arsenm/sanitizers-cmake/archive/${_sanitizers_cmake_version}.tar.gz https://github.com/yuzu-emu/sirit/archive/${_sirit_version}.tar.gz https://github.com/libsdl-org/SDL/archive/${_SDL_version}.tar.gz https://github.com/arun11299/cpp-jwt/archive/${_cpp_jwt_version}.tar.gz https://github.com/yhirose/cpp-httplib/archive/${_cpp_httplib_version}.tar.gz https://github.com/KhronosGroup/Vulkan-Headers/archive/${_Vulkan_Headers_version}.tar.gz" checksum="b8b2616a24653352b8afd145ee46eb9ead07c6ef3aff8c0ff3a6225b381b4b85 fbe54fc881cdfb0876ddc8f29f74674a311ba7ae4b774751cb1b637c043e3bae 170530852547ee2f5517b0a12e643646e51a9974414084d389a85632df7c4518 8d3553ea5c3b47789c5a1a6437f948525d0a8ce2a0897000a36b511000c6bad4 8c5b7ca55ee586a3e5e63de2d31c319045f92e949140a734846a0d69ad342e2e 9f5b073625375322236a94ce8d2d803cdedad321c91e63845f487b9ebfb2c433 6612f924d1f2b2c7cb37effcda5d78550fad276887ee8f9bc391b9ecbf9e4a64 2a149e79712027d2d8141e3233df2f6679825b6f78237db3db72bc6cfc08b845 b4cc0e1f89d3c60a4dde74baa730a90de13c5dd5155b09d8dd34cd3205a6e758 61a97686b03edffa737c396f54e48da2ff0a04c3f6859ec9e80853aea6508030 99443e30caee5d2c0019de6549cc0c7c0432214494617da445753fc46374a7c3" post_extract() { mv "xbyak-${_xbyak_version}" xbyak cp -r xbyak "${build_wrksrc}/externals" mv "dynarmic-${_dynarmic_version}" dynarmic cp -r dynarmic "${build_wrksrc}/externals" mv "mbedtls-${_mbedtls_version}" mbedtls cp -r mbedtls "${build_wrksrc}/externals" mv "SDL-${_SDL_version}" SDL cp -r SDL "${build_wrksrc}/externals" mv "cubeb-${_cubeb_version}" cubeb mv "sanitizers-cmake-${_sanitizers_cmake_version}" sanitizers-cmake cp -r sanitizers-cmake cubeb/cmake cp -r cubeb "${build_wrksrc}/externals" mv "sirit-${_sirit_version}" sirit cp -r sirit "${build_wrksrc}/externals" mv cpp-jwt-${_cpp_jwt_version} cpp-jwt cp -r cpp-jwt ${build_wrksrc}/externals mv cpp-httplib-${_cpp_httplib_version} cpp-httplib cp -r cpp-httplib ${build_wrksrc}/externals mv Vulkan-Headers-${_Vulkan_Headers_version} Vulkan-Headers cp -r Vulkan-Headers ${build_wrksrc}/externals }

Through development I've been making requests to my locally hosted sever using cpphttplib via HTTP and always had the intention of using HTTPS once my website was live. Not the smartest idea to leave this until the end, I know.

Have you tried searching the internet? https://github.com/yhirose/cpp-httplib

I'm new to C++, and have been trying to make a simple HTTP request. I stumbled on cpp-httplib and decided to try it out.