Lewati ke konten
Gin Web Framework

Build tanpa MsgPack

MsgPack (MessagePack) adalah format serialisasi binary yang ringkas — anggap saja sebagai alternatif JSON yang lebih cepat dan lebih kecil. Gin menyertakan dukungan rendering dan binding MsgPack secara default, yang berarti aplikasi Anda dapat menerima dan mengembalikan data berenkode MsgPack langsung menggunakan c.Bind() dan c.Render() dengan tipe konten yang sesuai.

Namun, banyak aplikasi hanya menggunakan JSON dan tidak pernah membutuhkan MsgPack. Dalam kasus tersebut, dependensi MsgPack menambah bobot yang tidak perlu ke binary yang dikompilasi. Anda dapat menghapusnya dengan tag build nomsgpack.

Building without MsgPack

Pass the nomsgpack tag to go build:

Terminal window
go build -tags=nomsgpack .

This also works with other Go commands:

Terminal window
go run -tags=nomsgpack .
go test -tags=nomsgpack ./...

What changes

When you build with nomsgpack, Gin excludes the MsgPack rendering and binding code at compile time. This has a few practical effects:

  • The compiled binary is smaller because the MsgPack serialization library is not linked in.
  • Any handler that attempts to render or bind MsgPack data will no longer work. If you use c.ProtoBuf() or other non-MsgPack renderers, those are unaffected.
  • All JSON, XML, YAML, TOML, and ProtoBuf features continue to work normally.

Verifying the result

You can confirm the binary size reduction by comparing builds:

Terminal window
# Standard build
go build -o gin-app .
ls -lh gin-app


# Build without MsgPack
go build -tags=nomsgpack -o gin-app-nomsgpack .
ls -lh gin-app-nomsgpack

The exact savings depend on your application, but removing MsgPack typically shaves a small amount off the final binary. For more background, see the original pull request.