| Base Classes | Base classes that simplify implementation of functionality | 
| ▼Components | Components that could be used with utils::DaemonMain like functions; see Component system for an intro | 
| HTTP Handlers | Handlers are components that could be used by components::Server to process the incoming requests | 
| Component Default Names | Default names of components that are used in static config files | 
| Clients | Clients are classes that provide interfaces for requesting and retrieving data usually from remove server | 
| Concurrency | Task construction and synchronization primitives for coroutines | 
| Universal | Functions and classes that could be used with or without coroutine environment | 
| Containers | Utility containers | 
| ▼Formats | Different containers that share the same interface and manipulate tree-like formats | 
| Serializers | Files with serializers into formats | 
| SAX Serializers | Files with SAX serializers into formats | 
| Parsers | Files with parsers from formats | 
| Postgres parsers and formatters | Files with Postgres parsers and formatters | 
| Readers and writers for dump::Dumper | Files with dump readers and writers, used mostly by the caches | 
| Clickhouse types | Files with implemented ClickHouse types | 
| ▼Testsuite Python support | Functions, fixtures and classes to do functional testing with testsuite | 
| Fixtures | Fixtures to use with testsuite | 
| Unit-testing (utest) | Versions of gtest macros that run tests in a coroutine environment and other helpers |