Why does Apache Avro use JSON to define a schema? Why not use IDL directly to define a schema? What is the advantage in transforming IDL to JSON?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why does Apache Avro use JSON to define a schema? Why not use IDL directly to define a schema? What is the advantage in transforming IDL to JSON?
Because JSON is trivially serializable, ubiquitous, and the original schema definition mechanism.
Bear in mind that Avro is platform-neutral, and it must continue to support platforms and libraries that use the original schema def–and that’s the schema that’s sent in the message. If you started transmitting only IDL then everything would break.