Remove AWS Remove Java Remove Traffic Remove Transportation
article thumbnail

Building Netflix’s Distributed Tracing Infrastructure

The Netflix TechBlog

Our tactical approach was to use Netflix-specific libraries for collecting traces from Java-based streaming services until open source tracer libraries matured. We chose Open-Zipkin because it had better integrations with our Spring Boot based Java runtime environment. Stream Processing: to sample or not to sample trace data?

article thumbnail

DBLog: A Generic Change-Data-Capture Framework

The Netflix TechBlog

Nonetheless, we found a number of limitations that could not satisfy our requirements e.g. stalling the processing of log events until a dump is complete, missing ability to trigger dumps on demand, or implementations that block write traffic by using table locks. Blocking write traffic by locking tables. Writing events to any output.

Database 197
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

DBLog: A Generic Change-Data-Capture Framework

The Netflix TechBlog

Nonetheless, we found a number of limitations that could not satisfy our requirements e.g. stalling the processing of log events until a dump is complete, missing ability to trigger dumps on demand, or implementations that block write traffic by using table locks. Blocking write traffic by locking tables. Writing events to any output.

Database 212
article thumbnail

Evolution of Netflix Conductor:

The Netflix TechBlog

Our cluster size ranges from 12–18 instances of AWS EC2 m4.4xlarge instances, typically running at ~30% capacity. *?—?Cassandra This addition also provides the option to use the Elasticsearch RestClient instead of the Transport Client which was enforced in the previous version. Cassandra persistence module is a partial implementation.

Lambda 189