Summary

The outcome of NODE-4004 has determined that the js-bson library has significantly worse deserialization performance than bson-ext which is a large barrier to sunsetting bson-ext. We want to identify and address bottlenecks to deserialization in the js-bson library so that we can improve js-bson and make it a viable option for users of bson-ext

Motivation

Who is the affected end user?

Users of bson-ext (and likely driver versions <=4) that require the higher deserialization performance of that library.

How does this affect the end user?

Provides a viable path to migrating to js-bson from bson-ext

How likely is it that this problem or use case will occur?

Very likely if migrating from bson-ext to js-bson

If the problem does occur, what are the consequences and how severe are they?

Migrating directly to js-bson to bson-ext will result in drops of deserialization performance of a minimum of ~30% at time of writing (Dec 14, 2023).

Is this issue urgent?

Targeting FY25Q3 or FY25Q4.

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

No

Cast of Characters

Engineering Lead:
Document Author:
POCers:
Product Owner:
Program Manager:
Stakeholders: 

Channels & Docs

Slack Channel

[Scope Document|some.url]

[Technical Design Document|some.url]