Seata-server
Apache Seata is a tool that ensures complex digital transactions stay synchronised.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
84/100 Excellent
- Maintained
- 100last commit 1 day ago
- Popular
- 8826,004 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 94no serious findings, 1 minor, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed 54 days ago
- GitHub stars
- 26,004
- Open issues
- 903
- Last commit
- 2026-11-20
- Latest release
- v2.6.0
- License
- Apache-2.0
- Activity
- rising
Checked yesterday - source: GitHub (apache/incubator-seata)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Keep your Naming Server config files Protect the Seata Naming Server folder, especially conf/application.yml, which holds its settings. If that config is lost or broken, the Naming Server can stop finding the Seata server, so your apps will not be able to start transactions. source
- Check Naming Server on port 8080 After starting the Naming Server, open http://127.0.0.1:8080/naming/v1/clusters?namespace=public on the machine where it is installed. This is the port used to ask where Seata server nodes are running; if it is blocked or the request fails, clients cannot find the Seata server. source
- Use -e test only for test settings Use sh seata-server.sh -e test only if you want Seata to load its separate 'test' configuration. If you add or forget this flag on a machine that has multiple settings, Seata may use the wrong config and your apps may not connect. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do Seata clients discover running server nodes?
Clients use the Seata Naming Server on port 8080 to find where Seata server nodes are running. If that port is blocked or the request fails, clients cannot find the Seata server.
Which Naming Server file is critical to keep intact?
Keep the Seata Naming Server folder, especially conf/application.yml, backed up. If it is lost or broken, the Naming Server can stop finding the Seata server and apps cannot start transactions.
How should I use the -e option when starting Seata Server?
Use sh seata-server.sh -e test only when you want the server to load a separate test configuration. If multiple configurations exist and the flag is added or forgotten, Seata may use the wrong config and apps may not connect.
How does the Seata Docker environment variable affect startup configuration?
The variable is optional and specifies an environment such as dev or test. At startup, the server then looks for a matching registry file, such as registry-dev.conf, under the configuration path.
Answers sourced from github.com, github.com, github.com, seata.apache.org
Community
No community discussions collected yet.