redpanda-data / redpanda-data/console
Support user-provided custom SerDe
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
Users should have a way to write and use their own SerDes for serializing or deserializing messages when producing or listing messages via Console. Use cases could be:
- E2E message encryption
- Custom serialization strategies with common formats (e.g. storing protobuf metadata in headers instead of the key/value payloads)
- Custom formats (e.g. https://github.com/redpanda-data/console/issues/1177)
To achieve this we could potentially utilize Go's plugin system (which has a several downsides such as missing Windows support though), Hashicorp's plugin framework or WASM.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Begin by mapping Console’s produce and message-listing paths, then compare Go plugins, HashiCorp’s plugin framework, and WASM; done would require a settled extension design supporting user-provided SerDes for serialization and deserialization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, wasm
- Domain
- backend, stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100