Roadmap · 0.1.0 and the next versions
What is in 0.1.0.
The first release covers the core of a game backend. The next versions add the social and scaling features on top.
0.1.0 contains
| Part | What |
|---|---|
| core | the builder, modules, databases, migrations, HTTP, OpenAPI, command line |
| accounts | the Auth module, rate limits, trusted proxies, app commands |
| WebSocket | the hub: the client's envelope, handlers, pushes, rooms, bounded outboxes, close codes, revocation closes, AsyncAPI |
| modules | storage (saves) and chat (with presence); typed routes from the protocol's HttpCall |
| deployment | Docker Compose or systemd, Caddy, backups, a measured load test |
Released together at 0.1.0: net_backend_server, net_backend_protocol and net_backend_client (HTTP with automatic token refresh, async and blocking, WebSocket, SSH and SFTP), alongside bevy_net_backend 0.1.0 for Bevy games.
Next versions
- OAuth providers
- Notifications
- Friends
- Leaderboards
- Groups
- Lobbies
- An optional SeaORM layer reusing the framework's pool
- Multi-instance pub/sub
- Payment connectors
Scope of 0.1.0
- Logins are email + password and Steam; OAuth providers are part of the next versions.
- One process: WebSocket rooms, presence and rate limits are per instance. Several instances share pushes through a
Broadcaster; multi-instance pub/sub is part of the next versions. - Storage values are JSON (binary data as a string in JSON).
- TLS and response compression belong to the reverse proxy (Caddy in the deployment files).
Ideas and pull requests are welcome on GitHub.