Framework
sofastack/sofa-bolt avatar
sofastack/sofa-bolt

SOFABolt: a Netty remoting framework whose user list and call types are both images

SOFABolt is a lightweight, easy to use and high performance remoting framework based on Netty.

2,505 stars864 forksJavaApache-2.0

At a glance

What is it?
Ant's Apache-2.0 communication framework, where the feature list is organised by module name, the README skips from section 2 to section 4, the contact section is five dead chat rooms, and the header publishes an abandonment badge on purpose.
Who is it for?
SOFABolt fits a Java team that has outgrown hand-rolled Netty plumbing and wants either a ready RPC protocol or the communication model without anyone else's message format. Four things to weigh.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 81 days ago.
What is it written in?
Mainly Java, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • sofastack/sofa-bolt2,505 ★ · +0
Star history
Repository2026-09-302026-11-15
sofastack/sofa-bolt2.5k2.5k

0 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The header publishes an abandonment badge on purpose

Three badges sit at the top of the file: a continuous integration badge pointing at a Travis endpoint, a code coverage badge, and one for whether the project is still maintained.

The third is the interesting one. It links to a service that reports the percentage of issues that remain open, which is a proxy for whether maintainers are answering. Most projects leave that to a reader's judgement. Publishing it in the header means the project has made a claim about its own responsiveness that anyone can check without asking.

The name comes from the dog in the Disney animated film Bolt, and the file says so plainly. That is a small thing, but it is the only part of the project's presentation that is not a technical claim, and it is the part most people will remember.

The file is written in Chinese throughout, so the practical audience this document was written for is a Chinese-speaking Java developer.

Two ways in, and the difference is who owns the protocol

The two usage sections are the whole design decision, and they are alternatives rather than layers.

The first treats SOFABolt as a remoting framework. You do not deal with the details of a private protocol at all; you use the RPC protocol that ships with it, start a client and a server, register a user request processor, and connection management, heartbeats and the rest are available by default. The stated benefit is that you spend your effort on business logic rather than on the transport.

The second treats it as a protocol framework. You reuse the communication model and the interface definitions the protocol layer provides, and you write your own Command types, command handlers and codec handlers for your own message format.

So the question is whether the RPC protocol is acceptable to you. If it is, the first route is a few classes. If it is not, the second gives you the transport and the threading without the format, at the cost of owning the codec.

The feature list is organised by module name

Rather than a flat list of capabilities, the features are grouped under the three module names they belong to, which doubles as the architecture.

The remoting core carries Netty's network IO and threading model, connection management described as lock-free connection establishment with periodic disconnection and automatic reconnection, timeout control, batch unpacking and batch submit handlers, and heartbeat and idle event handling. It also names the four call models the library supports: oneway, sync, future and callback.

The protocol skeleton is the extension surface: commands and command handlers, codec handlers, and heartbeat triggers. Those are the three things you implement when you use the framework mode.

The protocol implementation is where the shipped RPC protocol lives, and it has the most specific items in the file: the protocol design itself, flexible control over when deserialization happens, a fail-fast mechanism for request processing timeouts, the user request processor, and duplex communication.

The deserialization timing and the fail-fast timeout are the two items that show design attention: the first lets you decide when a message body is parsed, the second fails a request early rather than letting it sit.

The call types and the user list are both images

Two of the sections a reader would most want are not in the text at all.

The usage section states that the currently supported call types are shown in a figure, and the figure is not part of the file's text. So the enumeration of what the library can do, which the surrounding prose sets up as the main question, exists as a picture.

The users section is worse in the way that matters for a reader trying to judge adoption. It is a table of logo images, and in the text of the file every cell is empty. The claim being made is that a set of companies use this framework, and the evidence is a grid of images with no names, no captions and no links in the version you can read.

Both patterns are normal for a project page rendered on a hosting site, where images load. They are not normal for a repository, which is where people land when they want to evaluate something. Anyone assessing adoption from this file has to take the claim on trust.

The section numbering jumps from two to four

The headings run one, two, four, five, six and seven. There is no section three, and nothing in the file refers to one.

The content that would have been a section three is plausibly the usage material, which is split across two unnumbered subsections after the feature list, so the number looks retired rather than omitted by accident. That is an editing artefact rather than a decision, and it is the kind of detail that suggests the file is maintained less often than the code.

It matters more than it looks for one practical reason. This file is the entry point for a framework with three modules, two usage modes, four call models and a wiki behind it, and the whole document fits in a page and a half of text plus two diagrams. If the summary is not being kept current, the handbook it points to is where you should be reading instead.

The contact section is a list of full rooms

The last section is the one with the most specific numbers in the file, and most of them are dead.

Five DingTalk groups are struck through, each with a group number and each marked as full. The sixth group is listed without strikethrough and carries a number, so it is the one still accepting people. Then there is a separate group described as a gold user service group for people who are already running SOFAStack components in production, who are invited on request so that support is faster.

The invitation-only production group is a sensible design: it puts people with real deployments in a smaller channel. The five struck-through groups are the residue of a project that outgrew its community chat, left in place because deleting them would have removed the record.

The other channel named is a WeChat public account for distributed architecture practice in financial scenarios, described as a platform for discussing financial technology approaches rather than as a support channel for this framework.

A Maven wrapper, a header template and a contributor agreement

The build is Maven with the wrapper committed, including the Unix and Windows launchers and the wrapper's own configuration directory, so a clone builds without a matching Maven installation on the machine.

Continuous integration is configured through a Travis file rather than a GitHub workflow, matching the badge in the header. Two other root entries say something about how the project is run: a file named `HEADER` that exists to be the license header applied to source files, and a shared configuration directory whose name suggests it is inherited from a wider middleware project rather than owned here. Assembly descriptors and Maven plugins are also built in this tree.

Contribution has a gate before the code does. The file says the code is open and contributions are welcome after signing an agreement, with the process in the contributing guide, and separately that modifications must comply with the copyright terms in the license. There is also a security policy file at the root.

On cadence, the tags are v1.6.10 in May 2024, v1.6.11 in December 2024 and v1.6.12 in April 2025, while the last commit on the default branch is dated 2026-08-26. The branch is therefore moving well past the last published artifact, and ports exist for Node, Python and C++ in sibling repositories.

Editorial conclusion

SOFABolt fits a Java team that has outgrown hand-rolled Netty plumbing and wants either a ready RPC protocol or the communication model without anyone else's message format. Four things to weigh. Pick your entry point deliberately, because the framework mode and the remoting mode differ in who owns the protocol, and migrating later means rewriting your Command types. Judge maintenance from the numbers rather than the prose: the newest tag is from April 2025 while the branch has commits into August 2026, so the tree is moving on a slower clock than a weekly cadence, and the project is honest enough to publish an open-issue percentage badge in its own header. The documentation you actually need is not in the repository, since the supported call types and the user list are only present as images and the handbook lives on the project's wiki. And if you intend to contribute, the process starts with signing a contributor agreement, which is a heavier gate than an issue tracker.

Frequently asked questions

What are the two ways to use SOFABolt?

As a remoting framework with its built-in RPC protocol, where you start a client and server and register a user request processor, or as a protocol framework where you reuse the communication model and define your own Command types, command handlers and codec handlers.

Which communication models does SOFABolt support?

Four are named in the feature list: oneway, sync, future and callback. The remoting core also covers connection management with lock-free connection establishment, periodic disconnection and automatic reconnection, timeout control, batch unpacking and batch submit handlers, and heartbeat and idle event handling.

Which Java versions and modules does SOFABolt cover?

The features are grouped under three module names: a remoting core for IO, connections and the call models, a protocol skeleton holding commands, command handlers, codec handlers and heartbeat triggers, and a protocol implementation carrying the RPC protocol with configurable deserialization timing, a fail-fast timeout, a user request processor and duplex communication.

How do I contribute to SOFABolt?

The code is open and contributions are accepted after signing a contributor agreement, with the process described in the contributing guide. Modifications must also comply with the copyright terms in the license file.

Where do I get support for SOFABolt?

From the project handbook in its wiki and its discussion channels. Five DingTalk groups listed in the README are struck through and marked full, the sixth is open, and a separate production user group is invitation only for people already running the components.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. sofastack/sofa-bolt on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sofastack-sofa-bolt.svg)](https://hysenlabs.com/projects/sofastack-sofa-bolt)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sofastack-sofa-bolt.svg)](https://hysenlabs.com/projects/sofastack-sofa-bolt)

Was this useful?