# different job_serializer/job_parser function by tube

I using Beanstalk as primary message queue with Beaneater. In my scenario, every service got its own Beanstalkd Tube.

As system growing, There is an idea about using optimized job serializer/parser for different service to get better performance.

Any suggestion :D?

The issue proposes different job serializers and parsers for each Beanstalkd tube in Beaneater. No files, tests, or implementation entry points are identified; first determine the current serialization path and the scope of the per-tube design before defining completion criteria.

Written by the indexing model from the issue text.