Collector Exporter - split into 3 packages

[obecny]

Some people are using for example aws lambda, this means the size of overall matters and there is some limitation in package size. Currently we have grpc and protobufjs installed always. For this reason if someone wants to use the exporter and never want to use grpc or proto he could use an exporter package without grpc and proto. This would means splitting exporter into 3 packages:
collector-exporter-node
collector-exporter-node-proto
collector-exporter-node-grpc

The benefit would be the decrease in size and we would get rid of protocolNode param from config.

opentelemetry-exporter-collector would be a main package for web and for node using json over http only.
opentelemetry-exporter-collector-proto would extend opentelemetry-exporter-collector and override the transport method with proto over http
opentelemetry-exporter-collector-grpc would extend opentelemetry-exporter-collector and override the transport method with grpc

The naming for packages
@opentelemetry/exporter-collector
@opentelemetry/exporter-collector-proto
@opentelemetry/exporter-collector-grpc

[obecny]

@open-telemetry/javascript-approvers ^^

[dyladan]

Seems like a decent compromise to me. @mayurkale22 ?

[obecny]

Updated naming for packages ^^

[mwear]

FWIW. This is exactly what is being asked for in this specification issue: open-telemetry/opentelemetry-specification#678.

Protobuf is a relatively big dependency, which some clients are not willing to take. For example, webjs, iOS/Android (in some scenarios, the size of the installation package is limited, do not want to introduce protobuf dependencies). Plain JSON is a smaller dependency and is built in the standard libraries of many programming languages.

[mayurkale22]

Makes sense to me. This would definitely simply the collector codebase and provide an easy way to use it.

Couple of questions:

1. @opentelemetry/exporter-collector is for HTTP and can be used in both Node and Web right?
2. Seems like there will be some overlap of code (utils, types, const etc.) between these 3 packages, where do you plan to keep them?

[mayurkale22]

opentelemetry-exporter-collector would be a main package for web and for node using json over http only.

Looks like you already answered the first question in the description. My Bad!

[obecny]

2. Seems like there will be some overlap of code (utils, types, const etc.) between these 3 packages, where do you plan to keep them?

They will be in main package as they are needed there anyway - I have already started working on that :)