scylladb/seastar

High performance server-side application framework

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 7th, 2026
Created on August 18th, 2014
Open Issues & Pull Requests: 578 (+0)
GitHub issues: Enabled
Number of forks: 1,706
Total Stargazers: 9,359 (+0)
Total Subscribers: 381 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Seastar is a high-performance event-driven framework for writing non-blocking, asynchronous server-side applications in C++.

The framework addresses the challenge of building scalable server applications by providing a futures-based model that allows developers to write asynchronous code in a relatively straightforward manner. It is built on an event-driven architecture and integrates with DPDK for high-performance networking capabilities. The framework handles the complexity of non-blocking I/O and asynchronous execution patterns, enabling developers to express concurrent logic without traditional threading overhead.

Seastar suits projects that demand high throughput and low latency, particularly those requiring efficient handling of many concurrent connections. It is well-suited for database systems, message brokers, and other performance-critical server applications. The framework is sensitive to allocators and compiler optimizations, with performance varying significantly across build modes—release builds are substantially faster than development or debug builds. Developers should be prepared for a steeper learning curve when adopting the futures-based programming model, though the README indicates this becomes manageable once understood.

The project maintains multiple build configurations tailored to different development phases: debug mode with sanitizers for initial development, dev mode for the build-and-test cycle, release mode for production deployment, and sanitize mode for tracking down bugs. The build system is CMake-based with a Python configuration wrapper, and the project can be consumed either directly from its build directory or after installation to the filesystem using pkg-config or CMake integration. Docker-based building is also supported for hosts that require it.