home.social

#protocolbuffers — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #protocolbuffers, aggregated by home.social.

  1. #Confluent introduces a new approach in #ApacheKafka that moves schema IDs from message payloads to record headers.

    ✅ Simplify schema governance & evolution.
    ✅ Improve compatibility across serialization formats
    ✅ Reduce coupling between data & metadata in event-driven architectures

    Read the deep dive on #InfoQbit.ly/4tF7Fot

    #ML #EventStreamProcessing #ProtocolBuffers #DataPipelines #DataAnalytics

  2. #Confluent introduces a new approach in #ApacheKafka that moves schema IDs from message payloads to record headers.

    ✅ Simplify schema governance & evolution.
    ✅ Improve compatibility across serialization formats
    ✅ Reduce coupling between data & metadata in event-driven architectures

    Read the deep dive on #InfoQbit.ly/4tF7Fot

    #ML #EventStreamProcessing #ProtocolBuffers #DataPipelines #DataAnalytics

  3. #Confluent introduces a new approach in #ApacheKafka that moves schema IDs from message payloads to record headers.

    ✅ Simplify schema governance & evolution.
    ✅ Improve compatibility across serialization formats
    ✅ Reduce coupling between data & metadata in event-driven architectures

    Read the deep dive on #InfoQbit.ly/4tF7Fot

    #ML #EventStreamProcessing #ProtocolBuffers #DataPipelines #DataAnalytics

  4. #Confluent introduces a new approach in #ApacheKafka that moves schema IDs from message payloads to record headers.

    ✅ Simplify schema governance & evolution.
    ✅ Improve compatibility across serialization formats
    ✅ Reduce coupling between data & metadata in event-driven architectures

    Read the deep dive on #InfoQbit.ly/4tF7Fot

    #ML #EventStreamProcessing #ProtocolBuffers #DataPipelines #DataAnalytics

  5. introduces a new approach in that moves schema IDs from message payloads to record headers.

    ✅ Simplify schema governance & evolution.
    ✅ Improve compatibility across serialization formats
    ✅ Reduce coupling between data & metadata in event-driven architectures

    Read the deep dive on bit.ly/4tF7Fot

  6. Protobuf library flaw enables remote JavaScript code execution

    A critical flaw in the popular protobuf.js library has been exposed, allowing hackers to execute JavaScript code remotely - and a proof-of-concept exploit has already been published, putting countless systems at risk.

    osintsights.com/protobuf-libra

    #RemoteCodeExecution #Javascript #Protobuf #ProtocolBuffers #EmergingThreats

  7. 😆 Ah, #Skir, the "revolutionary" tool that claims to outshine Protocol Buffers! Because, of course, adding yet another layer of complexity with its own .skir files and #YAML wizardry is exactly what every developer needs to clutter their toolchain. 🚀 But hey, at least it promises to make that #TypeScript code feel like home, as if we weren't already comfy enough in our coding caves. 🙄
    skir.build/ #ProtocolBuffers #DeveloperTools #HackerNews #ngated

  8. 😆 Ah, #Skir, the "revolutionary" tool that claims to outshine Protocol Buffers! Because, of course, adding yet another layer of complexity with its own .skir files and #YAML wizardry is exactly what every developer needs to clutter their toolchain. 🚀 But hey, at least it promises to make that #TypeScript code feel like home, as if we weren't already comfy enough in our coding caves. 🙄
    skir.build/ #ProtocolBuffers #DeveloperTools #HackerNews #ngated

  9. 😆 Ah, #Skir, the "revolutionary" tool that claims to outshine Protocol Buffers! Because, of course, adding yet another layer of complexity with its own .skir files and #YAML wizardry is exactly what every developer needs to clutter their toolchain. 🚀 But hey, at least it promises to make that #TypeScript code feel like home, as if we weren't already comfy enough in our coding caves. 🙄
    skir.build/ #ProtocolBuffers #DeveloperTools #HackerNews #ngated

  10. 😆 Ah, #Skir, the "revolutionary" tool that claims to outshine Protocol Buffers! Because, of course, adding yet another layer of complexity with its own .skir files and #YAML wizardry is exactly what every developer needs to clutter their toolchain. 🚀 But hey, at least it promises to make that #TypeScript code feel like home, as if we weren't already comfy enough in our coding caves. 🙄
    skir.build/ #ProtocolBuffers #DeveloperTools #HackerNews #ngated

  11. #GoogleCloud announces #gRPC as native transport for #MCP #AI

    #MachineLearning #opensource

    🔌 Eliminates need for transcoding gateways between #gRPC services and #MCP JSON-RPC

    ⚡ Binary encoding via #ProtocolBuffers shrinks messages up to 10x compared to JSON - dramatically lower latency, reduced bandwidth consumption & faster serialization

    🧵 👇

  12. #GoogleCloud announces #gRPC as native transport for #MCP #AI

    #MachineLearning #opensource

    🔌 Eliminates need for transcoding gateways between #gRPC services and #MCP JSON-RPC

    ⚡ Binary encoding via #ProtocolBuffers shrinks messages up to 10x compared to JSON - dramatically lower latency, reduced bandwidth consumption & faster serialization

    🧵 👇

  13. #GoogleCloud announces #gRPC as native transport for #MCP #AI

    #MachineLearning #opensource

    🔌 Eliminates need for transcoding gateways between #gRPC services and #MCP JSON-RPC

    ⚡ Binary encoding via #ProtocolBuffers shrinks messages up to 10x compared to JSON - dramatically lower latency, reduced bandwidth consumption & faster serialization

    🧵 👇

  14. #GoogleCloud announces #gRPC as native transport for #MCP #AI

    #MachineLearning #opensource

    🔌 Eliminates need for transcoding gateways between #gRPC services and #MCP JSON-RPC

    ⚡ Binary encoding via #ProtocolBuffers shrinks messages up to 10x compared to JSON - dramatically lower latency, reduced bandwidth consumption & faster serialization

    🧵 👇

  15. #GoogleCloud announces #gRPC as native transport for #MCP #AI

    #MachineLearning #opensource

    🔌 Eliminates need for transcoding gateways between #gRPC services and #MCP JSON-RPC

    ⚡ Binary encoding via #ProtocolBuffers shrinks messages up to 10x compared to JSON - dramatically lower latency, reduced bandwidth consumption & faster serialization

    🧵 👇

  16. 🚀 gRPC es el framework de Google que acelera la comunicación entre servicios. Usa HTTP/2 y Protocol Buffers para máximo rendimiento. ¡Conoce cómo funciona! 💻

    Lee más 👉 soloingenieria.org/ingenieria-

    #gRPC #Microservicios #IngenieríaDeSistemas #DesarrolloBackend #ProtocolBuffers #HTTP2

  17. En microservicios, la velocidad de comunicación define el rendimiento total. gRPC existe porque Google entendió esto antes que nadie. 🚀

    #gRPC #Microservicios #IngenieríaDeSistemas #DesarrolloBackend #ProtocolBuffers #HTTP2

  18. Achievement unlocked... I've just successfully transmitted the first Protocol Buffers messages over a UART link between an STM32G070 MCU (code written in Rust using Embassy) and a Python test program running on my Debian Linux laptop.

    Messages are sent with a small header (sync byte and length) and a CRC-16 trailer, and all worked on the second try (on the first try the CRC-16 calculation on the MCU was ignoring the first two bytes of the message - doh!).

    #Python #Rust #ProtocolBuffers #RustEmbedded

  19. Achievement unlocked... I've just successfully transmitted the first Protocol Buffers messages over a UART link between an STM32G070 MCU (code written in Rust using Embassy) and a Python test program running on my Debian Linux laptop.

    Messages are sent with a small header (sync byte and length) and a CRC-16 trailer, and all worked on the second try (on the first try the CRC-16 calculation on the MCU was ignoring the first two bytes of the message - doh!).

    #Python #Rust #ProtocolBuffers #RustEmbedded

  20. Achievement unlocked... I've just successfully transmitted the first Protocol Buffers messages over a UART link between an STM32G070 MCU (code written in Rust using Embassy) and a Python test program running on my Debian Linux laptop.

    Messages are sent with a small header (sync byte and length) and a CRC-16 trailer, and all worked on the second try (on the first try the CRC-16 calculation on the MCU was ignoring the first two bytes of the message - doh!).

    #Python #Rust #ProtocolBuffers #RustEmbedded

  21. Achievement unlocked... I've just successfully transmitted the first Protocol Buffers messages over a UART link between an STM32G070 MCU (code written in Rust using Embassy) and a Python test program running on my Debian Linux laptop.

    Messages are sent with a small header (sync byte and length) and a CRC-16 trailer, and all worked on the second try (on the first try the CRC-16 calculation on the MCU was ignoring the first two bytes of the message - doh!).

    #Python #Rust #ProtocolBuffers #RustEmbedded

  22. Achievement unlocked... I've just successfully transmitted the first Protocol Buffers messages over a UART link between an STM32G070 MCU (code written in Rust using Embassy) and a Python test program running on my Debian Linux laptop.

    Messages are sent with a small header (sync byte and length) and a CRC-16 trailer, and all worked on the second try (on the first try the CRC-16 calculation on the MCU was ignoring the first two bytes of the message - doh!).

    #Python #Rust #ProtocolBuffers #RustEmbedded

  23. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  24. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  25. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  26. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  27. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  28. Z pewnością przy przesyłaniu danych korzystacie z takich formatów jak XML czy JSON - są tak popularne, że słyszały o nich nawet osoby, które na co dzień nie zajmują się informatyką. Ale czy słyszeliście o Protocol Buffers i tym, jak potrafią przyspieszyć transport informacji? No to już słyszeliście.

    devszczepaniak.pl/protocol-buf

    #ProtocolBuffers #programowanie #HTTP #WebDev

  29. Z pewnością przy przesyłaniu danych korzystacie z takich formatów jak XML czy JSON - są tak popularne, że słyszały o nich nawet osoby, które na co dzień nie zajmują się informatyką. Ale czy słyszeliście o Protocol Buffers i tym, jak potrafią przyspieszyć transport informacji? No to już słyszeliście.

    devszczepaniak.pl/protocol-buf

    #ProtocolBuffers #programowanie #HTTP #WebDev

  30. Curious about how Lyft uses #ProtocolBuffers for inter-system integration?

    They prioritize collaborative protocol design, ensuring shared definitions across teams & systems. This approach not only enhances knowledge sharing but also boosts consistency and elevates development process quality.

    More on #InfoQ 👉 bit.ly/3ZpYa0M

    #SoftwareArchitecture #API #TeamCollaboration #CaseStudy

  31. Curious about how Lyft uses #ProtocolBuffers for inter-system integration?

    They prioritize collaborative protocol design, ensuring shared definitions across teams & systems. This approach not only enhances knowledge sharing but also boosts consistency and elevates development process quality.

    More on #InfoQ 👉 bit.ly/3ZpYa0M

    #SoftwareArchitecture #API #TeamCollaboration #CaseStudy

  32. Curious about how Lyft uses #ProtocolBuffers for inter-system integration?

    They prioritize collaborative protocol design, ensuring shared definitions across teams & systems. This approach not only enhances knowledge sharing but also boosts consistency and elevates development process quality.

    More on #InfoQ 👉 bit.ly/3ZpYa0M

    #SoftwareArchitecture #API #TeamCollaboration #CaseStudy

  33. Curious about how Lyft uses #ProtocolBuffers for inter-system integration?

    They prioritize collaborative protocol design, ensuring shared definitions across teams & systems. This approach not only enhances knowledge sharing but also boosts consistency and elevates development process quality.

    More on #InfoQ 👉 bit.ly/3ZpYa0M

    #SoftwareArchitecture #API #TeamCollaboration #CaseStudy

  34. Curious about how Lyft uses for inter-system integration?

    They prioritize collaborative protocol design, ensuring shared definitions across teams & systems. This approach not only enhances knowledge sharing but also boosts consistency and elevates development process quality.

    More on 👉 bit.ly/3ZpYa0M

  35. Comments from the .proto file are now carried over to the .dylan file, and add-foo methods are created for repeated fields.

    github.com/cgay/protocol-buffe

    #DylanLang #ProtocolBuffers

  36. Comments from the .proto file are now carried over to the .dylan file, and add-foo methods are created for repeated fields.

    github.com/cgay/protocol-buffe

    #DylanLang #ProtocolBuffers

  37. Comments from the .proto file are now carried over to the .dylan file, and add-foo methods are created for repeated fields.

    github.com/cgay/protocol-buffe

    #DylanLang #ProtocolBuffers

  38. This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)

    github.com/cgay/protocol-buffe

    #DylanLang #ProtocolBuffers

  39. This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)

    github.com/cgay/protocol-buffe

    #DylanLang #ProtocolBuffers

  40. This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)

    github.com/cgay/protocol-buffe

    #DylanLang #ProtocolBuffers

  41. This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)

    github.com/cgay/protocol-buffe

    #DylanLang #ProtocolBuffers