I’ve been working on my first open-source framework in Go, called Anclax.
The main ideas:
- One Postgres for all: Postgres here is not only the database, but also the message queue， maybe more in the future — while still allowing seamless migration to Kafka or other BIG systems later if the project grows.
- Built-in modules: starts with async/event queue, later may include more common services in web dev.
- Definition-first: use OpenAPI spec to define HTTP, SQL to define schema/queries, etc, then generate the glue code.
- New attempts: for example, macaroons tokens for auth.
- Convention over configuration: reduce hesitation, do more with less setup.
I’m an independent developer who often builds small projects. Over time I found myself repeating the same work again and again, so I turned that repetition into Anclax.
This is my first time releasing a framework. I don’t have much experience with open source projects, so I’d really appreciate feedback and discussion.
3 comments
[ 3.2 ms ] story [ 15.7 ms ] threadThe main ideas:
- One Postgres for all: Postgres here is not only the database, but also the message queue， maybe more in the future — while still allowing seamless migration to Kafka or other BIG systems later if the project grows.
- Built-in modules: starts with async/event queue, later may include more common services in web dev.
- Definition-first: use OpenAPI spec to define HTTP, SQL to define schema/queries, etc, then generate the glue code.
- New attempts: for example, macaroons tokens for auth.
- Convention over configuration: reduce hesitation, do more with less setup.
I’m an independent developer who often builds small projects. Over time I found myself repeating the same work again and again, so I turned that repetition into Anclax.
This is my first time releasing a framework. I don’t have much experience with open source projects, so I’d really appreciate feedback and discussion.
Repo: https://github.com/cloudcarver/anclax