[FEATURE] Implement jackson-blackbird for json serialization
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem
Blackbird is a object bytecode precompiler/optimizer that ties into the jackson pipeline and can help with json serialization performance. Reports on the interweb cite 20-40% memory and cpu usage on hard hit endpoints.
This issue is to introduce blackbird into dotCMS and allow it to be used in the defaultObjectMapper when serializing/unserializing data.
Goal
See attached article
I Switched to Jackson Blackbird and Slashed JSON Latency.pdf
Target Personas
- Developer teams
- Content teams
- DevOps teams
- System administrators (dotCMS)
Demo Expectations
Save memory/cpu cycles
Acceptance Criteria
No response
User Stories
No response
Links
No response
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
Start by locating dotCMS's defaultObjectMapper and the dependency configuration for Jackson. Review the closed pull requests linked from this issue and any existing serialization tests before deciding how Blackbird should be integrated. Done should include a usable default-mapper integration and evidence that memory or CPU usage improves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100