Closed Filip785 closed 1 year ago
Hi @Filip785. A common way of addressing this is with a schema registry, where each schema has a unique ID which you serialize alongside the data. If you have few events you could also combine them into a single union type which you would then use to serialize the messages (sending the combined schema when you first connect for example, so you don't need a separate registry).
Hi, thanks for the library.
I'm trying to use it to decode message in the browser, through WebSocket. I'm sending message from the websocket server in avro binary format as so:
Now, on the frontend I receive binary message like this:
Now, my question is, how can I know what type of schema is coming in from the message (as there can be multiple message types)? How can I know this beforehand so I can convert to correct object? Is it even possible?
Thanks.