Use JSON-B instead of an hardcoded Jackson
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 204
Description
Currently beam uses jackson directly everywhere, it either messes up environments where another version is here and can't be upgraded or it forces to shade and have a fat app where it is not needed. Using JSON-B will allow to switch the impl and beam will just rely on ~200k of API instead of megs of dependencies making it smoother to integrated in all environments.
Imported from Jira [BEAM-3992](https://issues.apache.org/jira/browse/BEAM-3992). Original Jira may contain additional context.
Reported by: romain.manni-bucau.
Contributor guide
Research direction
No files or tests are named. Start by inventorying Beam's direct Jackson usage and the affected dependency boundaries, then review how JSON-B implementations can be selected in supported environments. Done means Beam no longer hardcodes Jackson where JSON-B can be used and environments can supply an implementation without unnecessary shaded dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100