What is this?
Sogou C++ Workflow is an enterprise-grade C++ engine for asynchronous networking and parallel computing, used internally by Sogou to power search, cloud input method, and ad services, handling billions of requests daily.
Sogou C++ Workflow is an enterprise-grade C++ engine for asynchronous networking and parallel computing, used internally by Sogou to power search, cloud input method, and ad services, handling billions of requests daily.Is it a framework or just a networking library?It is a full asynchronous programming framework: besides being a multi-protocol client/server library (HTTP, Redis, MySQL, Kafka), it also lets you build custom protocols, your own RPC system, and arbitrary DAG-based workflows combining networking and computation.
It is a full asynchronous programming framework: besides being a multi-protocol client/server library (HTTP, Redis, MySQL, Kafka), it also lets you build custom protocols, your own RPC system, and arbitrary DAG-based workflows combining networking and computation.How do I add this to my project?Install prebuilt packages via apt-get on Debian/Ubuntu or dnf on Fedora, build with xmake, or compile from source with make; then follow the tutorials (e.g. 'wget' client example) to write your first task.
Install prebuilt packages via apt-get on Debian/Ubuntu or dnf on Fedora, build with xmake, or compile from source with make; then follow the tutorials (e.g. 'wget' client example) to write your first task.What do I need to build it?A C++11-capable compiler and OpenSSL 1.1+ (BoringSSL also works); it has no boost or asio dependency, but the Kafka protocol needs lz4, zstd and snappy compression libraries.
A C++11-capable compiler and OpenSSL 1.1+ (BoringSSL also works); it has no boost or asio dependency, but the Kafka protocol needs lz4, zstd and snappy compression libraries.Is the Windows version on par with Linux?Windows support ships as a separate branch using IOCP instead of the Linux epoll-based implementation, though the user-facing interfaces are kept identical to the Linux version.
Windows support ships as a separate branch using IOCP instead of the Linux epoll-based implementation, though the user-facing interfaces are kept identical to the Linux version.Which platforms and CPUs does it run on?It runs on Linux, macOS, Windows and Android, across 32/64-bit x86, big- and little-endian ARM, and Loongson processors.
It runs on Linux, macOS, Windows and Android, across 32/64-bit x86, big- and little-endian ARM, and Loongson processors.How does Workflow relate to srpc?srpc is a separate open-source RPC system built on top of Workflow, adding support for the srpc, brpc, trpc and thrift protocols.
srpc is a separate open-source RPC system built on top of Workflow, adding support for the srpc, brpc, trpc and thrift protocols.Can workflows be more complex than simple series/parallel chains?Yes, in addition to common series and parallel structures the framework supports arbitrary DAG (directed acyclic graph) task topologies.
Yes, in addition to common series and parallel structures the framework supports arbitrary DAG (directed acyclic graph) task topologies.What clients come built in out of the box?It ships with ready-made asynchronous clients for HTTP, Redis, MySQL (and MariaDB/TiDB), and Kafka, so you don't need to write your own protocol code for these.
It ships with ready-made asynchronous clients for HTTP, Redis, MySQL (and MariaDB/TiDB), and Kafka, so you don't need to write your own protocol code for these.How does it avoid memory leaks in async callback code?Every task's lifetime runs from creation to its callback finishing, after which it's automatically reclaimed; unwanted tasks must be released via dismiss(), and the design deliberately avoids std::shared_ptr in favor of std::function-based callbacks.
Every task's lifetime runs from creation to its callback finishing, after which it's automatically reclaimed; unwanted tasks must be released via dismiss(), and the design deliberately avoids std::shared_ptr in favor of std::function-based callbacks.Which topics is it in?consul, dag, service-discovery, load-balancer, kafka, dns, concurrency, async, microservices, mysql, redis, http
consul, dag, service-discovery, load-balancer, kafka, dns, concurrency, async, microservices, mysql, redis, http