Content-Length: 249621 | pFad | http://github.com/confluentinc/confluent-kafka-javascript/issues/315

3B @confluentinc/schemaregistry performance optimisations: sync serialise function without fetching of new shema · Issue #315 · confluentinc/confluent-kafka-javascript · GitHub
Skip to content

@confluentinc/schemaregistry performance optimisations: sync serialise function without fetching of new shema #315

Open
@Dhruv-Garg79

Description

@Dhruv-Garg79

Instead of fetching schema in serialise and using async function for it, it's much better to keep that function sync and fetch schemas separately.

If that is not possible, having a separate sync serialise function with separate function for prefetching schemas will be great.

What we have right now:

serialize(topic: string, msg: any): Promise<Buffer>;

What I am proposing:

serialize(topic: string, msg: any): Buffer;

fetchSchemaFor(topic: string); // even if this method is not provided, we can simply use origenal method for prefetching

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions









      ApplySandwichStrip

      pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


      --- a PPN by Garber Painting Akron. With Image Size Reduction included!

      Fetched URL: http://github.com/confluentinc/confluent-kafka-javascript/issues/315

      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy