Skip to content

Java Server Transport #1097

@bruno-garcia

Description

@bruno-garcia

The goal is to have a transport with high transaction throughput.

Constraints and requirements:

  • Not required by Android
  • Doesn't require offline caching
  • Flushed data doesn't need to be sent in order
  • Measure from baseline each change as we experiment
  • Metrics on dropped items. i.e: Atomic increment for dropped items so we have visibility

Some ideas:

  • Parallelize envelope serialization
  • Maintain N concurrent open connections
  • Producer/Consumer Envelope to Requests
    • Requests are gzip compressed blobs ready for the network I/O
  • To test it out: Benchmarks with a fake HTTP simulating a 1ms latency.

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions