miso

miso

main branch is unstable, install miso with tags instead

miso, yet another simple application framework. miso provides an opinionated way to write backend application, it 'subjectively' solves many common issues that we all have at some point during development.

It's mainly a fun project for me to prove: 'yes, we can just write a framework ourselves.'. Surprisingly, it does work.

The overall target is to make it as small and simple as possible, backward compatibility may break in future releases.

Include miso in your project

Install a specific release of miso:

go get github.com/curtisnewbie/miso@v0.3.0

You can also generate a new project using misogen (see CLI Tools).

Documentations

• CLI Tools
• Configuration
• Application Lifecycle
• HTTP Client
• HTTP API Declaration
• Tracing
• Database
• Distributed Task Scheduling
• Validation
• Service Healthcheck
• Json Processing Behaviour
• Rabbitmq and Event Bus
• Kafka
• API Documentation Generation
• Using pprof
• List of Supported Middlewares
• Upgrade & Migration

Projects that use miso

The following are projects that use miso (mine tho), see also moon-monorepo.

• gatekeeper
• event-pump
• mini-fstore
• vfm
• user-vault
• hammer
• goauth
• logbot
• doc-indexer

Updates

• Since v0.2.0, 21 configuration properties are renamed, these property names are not backward compatible. If you specify values for these configuration, make sure you update the property name before you upgrade miso.
• Since v0.3.0, a bunch of breaking changes are introduced, e.g., refactoring package structure, removing deprecated code and so on. Lots of methods and types are moved from /util pkg to pkgs such as cli, csv, errs, expr, flags, hash, heap, pair, queue, rfutil, slutil, stack, and strutil. Use ./patch/v0.3.0.patch for automatica migration. See Upgrade & Migration.