fries

Where the project came from

go-fries is a collection of Go components that the README says was migrated from the original github.com/go-kratos-ecosystem/components repository. The name change marks a move to a standalone home for the modules rather than a fork that tracks the old location. The README notes that the v4 line may include breaking changes compared with v3, and that backward compatibility is the default behavior within v4, with any incompatibilities recorded in the release notes. The package requires Go 1.26.0 or newer, which is a relatively recent toolchain, and it is installed with go get github.com/go-fries/fries/v4. The project advertises a MIT license and publishes documentation through pkg.go.dev, code coverage through codecov, and a Go Report Card, so the usual signals of a maintained Go library are present. For teams that already used the kratos ecosystem components, the migration means updating the import path and checking the v4 notes, but the intent is to keep the same building blocks available under a clearer name. The explicit warning about breaking changes is a sign the maintainers treat version boundaries seriously, and the request for caution on v4 tells a new adopter exactly where to look before upgrading. That honesty about stability is more useful than a silent major bump, because it points the reader at the release notes as the source of truth for what moved between versions.

What the modules cover

The README lists the public modules in the stable release set as a catalog of families. A Core family holds the base fries module plus errors, parallel, constraints, and capability, which the descriptions tie to release metadata, shared error helpers, parallel processing utilities, generic constraints, and capability contracts. A Cache family provides a cache abstraction and a Redis backed store through cache and cache/redis. A Crontab family is also listed in the table. The project description broadens this by naming the kinds of integration the components target, including Gin, Kratos, and Chi for web frameworks, along with Event, CloudEvents, and AMQP for messaging and event handling. The README is careful to say the catalog lists public modules and that examples and internal development tools are excluded, so the printed table is not the whole repository. This structure lets a team pick just the piece it needs, such as the Redis cache or the parallel helper, without pulling the entire set into a build. The split into families also helps with import size, because depending on cache/redis does not drag in the crontab code. For a developer, the practical reading is that go-fries is a menu of small, focused modules rather than one large framework, and the catalog is the place to check which path matches the problem before adding a dependency.

Packaging and versioning

Each module uses Go's semantic import versioning, so the v4 suffix appears in the import path and the pkg.go.dev links. The README points to a versions.yaml file that holds a module-sets.stable list, and it asks contributors to keep the catalog aligned with that file, which means the documented modules and the released modules are meant to stay in sync. Releases are tagged on GitHub and surfaced through a package version badge, and the project runs lint and test workflows on every change. For consumers, the practical takeaway is that go-fries behaves like a small library ecosystem under one roof: you depend on a specific module path, read its godoc, and upgrade within v4 without expecting breakage unless the release notes say otherwise. The migration from the kratos ecosystem and the explicit v4 caution suggest the maintainers treat stability as a promise they state up front rather than something left for users to discover. The alignment rule between the catalog and versions.yaml is a nice touch, because it prevents the docs from drifting ahead of what actually ships. A team adopting several of these modules can therefore trust that the table in the README matches the packages they can go get, which lowers the risk of following an example that references a module that was never released.

Editorial conclusion

The components are released under the MIT license and are written in Go, with the source at github.com/go-fries/fries.