Roadmap
The libraries a production REST API or network service needs, in the stdlib or as packages
fetched with ktm get.
Done
| Library | Kind | Since |
|---|---|---|
Packages: ktm.mod, ktm get, ktm build | tool | v0.20.0 |
net.tls, net.http client and HTTPS | stdlib | v0.20.0 |
crypto, with Argon2id and bcrypt | stdlib | v0.20.0 |
encoding.base64, encoding.hex, uuid, net.url, flag, config | stdlib | v0.20.0 |
Validation, net.http.middleware, ktm test | stdlib | v0.21.0 |
sql: SQLite with arguments and rows into structs | stdlib | v0.26.0 |
| ktm-pg (PostgreSQL) | package | v0.2.1 |
| ktm-jwt (JWT, JWE, JWK) | package | v0.2.1 |
| ktm-migrate (SQL migrations) | package | v0.1.1 |
Next
- ktm-redis, ktm-mysql, one SQL interface, WebSocket,
compress. - Metrics, tracing,
regex, templates,toml,decimal, time zones, testing helpers. - ktm-smtp, ktm-s3.
- Later, as people ask: HTTP/2, gRPC, messaging, OpenAPI, OAuth2.