mxsm commented on issue #4474: URL: https://github.com/apache/eventmesh/issues/4474#issuecomment-1773974551
> @mxsm Hi, I just wanted to say that this was the second issue I worked on. Although no contribution is a small contribution I believe that I can contribute to the core development of Apache Eventmesh. I am very much interested in the development of NodeJS SDK for Eventmesh. But when that begins (as it is currently planned) I have to be familiar with the majority of the codebase of Apache Eventmesh. In case if you have any suggestions then please let me know. I will be going through the documentation and merged pull requests to get better clarity. But still wanted to know your opinion if you can provide. Thanks!! @VishalMCF 1. You can get an overview of the entire project's code architecture and the relationships between each module. 2. Choose a protocol, like making gRPC calls, and familiarize yourself with making gRPC calls corresponding to the examples module. This will help you understand how the entire EventMesh system interacts and provide insights into its internal workings. 3. Once you've grasped the internal implementation, you can start writing an SDK for Node.js based on your interests. You can refer to the Java SDK as a guide. As you've seen with the Rust SDK, I developed it based on the Java SDK. However, you're also free to make improvements and optimizations based on your own insights. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
