Remove Infrastructure Remove Java Remove Traffic Remove Transportation
article thumbnail

Building Netflix’s Distributed Tracing Infrastructure

The Netflix TechBlog

Now let’s look at how we designed the tracing infrastructure that powers Edgar. This insight led us to build Edgar: a distributed tracing infrastructure and user experience. Our tactical approach was to use Netflix-specific libraries for collecting traces from Java-based streaming services until open source tracer libraries matured.

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

Data Movement in Netflix Studio via Data Mesh

The Netflix TechBlog

Data Mesh provides a drag-and-drop, self-service user interface for exploring sources and creating pipelines so that users can focus on delivering business value without having to worry about managing and scaling complex data streaming infrastructure. CDC events can also be sent to Data Mesh via a Java Client Producer Library.

Big Data 253
article thumbnail

Evolution of Netflix Conductor:

The Netflix TechBlog

Instead, we use a wrapper that pulls in the latest version of Conductor and adds Netflix infrastructure components and libraries before deployment. This addition also provides the option to use the Elasticsearch RestClient instead of the Transport Client which was enforced in the previous version.

Lambda 189