[GH-ISSUE #245] Use protobuf to encode messages stored in Redis #91

New issue

Closed

opened 2026-03-02 05:18:35 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 05:18:35 +03:00

Owner

Originally created by @hibiken on GitHub (Feb 15, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/245

Originally assigned to: @hibiken on GitHub.

Currently, all task messages are serialized in JSON format and stored in redis.
This comes with two issues:

JSON takes more space compared to other serialization scheme (e.g. protobuf, msgpack). We can expect less memory usage with these more compact serialization schemes.
Protocol Buffer has clearer forward/backward compatibility semantics as we evolve the library. We can expect that fields will be added/removed from the task messages stored in redis.

Originally created by @hibiken on GitHub (Feb 15, 2021). Original GitHub issue: https://github.com/hibiken/asynq/issues/245 Originally assigned to: @hibiken on GitHub. Currently, all task messages are serialized in JSON format and stored in redis. This comes with two issues: - JSON takes more space compared to other serialization scheme (e.g. protobuf, msgpack). We can expect less memory usage with these more compact serialization schemes. - Protocol Buffer has clearer forward/backward compatibility semantics as we evolve the library. We can expect that fields will be added/removed from the task messages stored in redis.