#apacheavro — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #apacheavro, aggregated by home.social.
-
🔥 Microcks 1.11.0 is out! 🚀
It's packed with new features like #API consumer validation, #gRPC headers and error simulation, and advanced @AsyncAPISpec + #ApacheAvro support!
It has been built with a secured software supply chain, including #sigstore signature, SBOM, and provenance attestations everywhere!
-
🔥 Microcks 1.11.0 is out! 🚀
It's packed with new features like #API consumer validation, #gRPC headers and error simulation, and advanced @AsyncAPISpec + #ApacheAvro support!
It has been built with a secured software supply chain, including #sigstore signature, SBOM, and provenance attestations everywhere!
-
#TechnicalWriting #APIs #APIDocumentation #AsynchronousAPIs #AsyncAPI #EventDrivenAPIs #ApacheAvro #JSON: "Luckily there's a specification similar to OpenAPI but directed at defining event-driven APIs. I'm talking about AsyncAPI. It's a specification that lets you define an API that's asynchronous in nature. By using AsyncAPI you can define, among other things, the different topics where events will be dropped, and the shape of the messages that represent each topic.
And this is where things get interesting. The shape of messages or, in other words, its payload, can adhere to specific standards. Without messages, there's no way to communicate events. And, following standards helps to guarantee the correct publishing, transport, and consumption of messages. If messages don't follow any standards, it's hard for developers to understand the shape of the messages. In addition, it's easy for consumers to stop working because, suddenly, messages are being shared in a slightly different format.
Among different message standards, there's one particularly interesting to me. Apache Avro isn't just a theoretical standard. It's also a serialization format. You can say it's a competitor to JSON but specialized in working with event-driven APIs. In the same way you can use JSON Schema to define the shape of JSON data you have Avro Schema to help you specify what Avro message payloads look like."
https://apichangelog.substack.com/p/how-to-document-event-driven-api
-
#TechnicalWriting #APIs #APIDocumentation #AsynchronousAPIs #AsyncAPI #EventDrivenAPIs #ApacheAvro #JSON: "Luckily there's a specification similar to OpenAPI but directed at defining event-driven APIs. I'm talking about AsyncAPI. It's a specification that lets you define an API that's asynchronous in nature. By using AsyncAPI you can define, among other things, the different topics where events will be dropped, and the shape of the messages that represent each topic.
And this is where things get interesting. The shape of messages or, in other words, its payload, can adhere to specific standards. Without messages, there's no way to communicate events. And, following standards helps to guarantee the correct publishing, transport, and consumption of messages. If messages don't follow any standards, it's hard for developers to understand the shape of the messages. In addition, it's easy for consumers to stop working because, suddenly, messages are being shared in a slightly different format.
Among different message standards, there's one particularly interesting to me. Apache Avro isn't just a theoretical standard. It's also a serialization format. You can say it's a competitor to JSON but specialized in working with event-driven APIs. In the same way you can use JSON Schema to define the shape of JSON data you have Avro Schema to help you specify what Avro message payloads look like."
https://apichangelog.substack.com/p/how-to-document-event-driven-api
-
How to use IBM's App Connect Enterprise to process #ApacheAvro serialized #Kafka messages
I spent some time helping a team do this yesterday, so I've shared the results here
-
How to use IBM's App Connect Enterprise to process #ApacheAvro serialized #Kafka messages
I spent some time helping a team do this yesterday, so I've shared the results here
-
Schema-Evolution in #ApachaKafka – dabei gibt es einiges zu beachten. Ansätze und Hilfsmittel wie #ApacheAvro zeigt Euch Goran im Blog: https://www.innoq.com/de/blog/2023/11/schema-evolution-avro/
-
Schema-Evolution in #ApachaKafka – dabei gibt es einiges zu beachten. Ansätze und Hilfsmittel wie #ApacheAvro zeigt Euch Goran im Blog: https://www.innoq.com/de/blog/2023/11/schema-evolution-avro/
-
In der neuen Blogserie von Paul Brebner erforscht er wie das #opensource Karapace Apache Kafka Schema Registry Add-on funktioniert und innerhalb verschiedener Schema-Typen arbeitet. In der ersten Folge stellen wir #ApacheAvro vor.
Lesen Sie Teil 1 hier: https://instaclustr.co/3XquQn2