At the Nanjing Summit of the 2018 Yunqi Conference, Alibaba researcher Lin Hao officially released the 4th Alibaba Middleware Performance Challenge. The challenge is based on open source projects, and the core technologies are Dubbo and RocketMQ. The purpose is to convey the spirit of open source to technology enthusiasts through the competition.
Lin Hao said in the release, "For developers, a lot of work uses open source things, and open source has a great impact on the whole world. The same is true for Alibaba, which also uses open source. Software, in this process, we combined Alibaba's scenarios, made a lot of improvements to the entire open source products, and began to give back to the community."
Since 2017, Alibaba's open source pace is accelerating.
In September 2017, RocketMQ graduated from Apache and became an Apache top-level project (TLP). In October, OpenMessaging released the application development standard in the field of distributed message middleware and stream processing. It has now officially settled in the Linux Foundation. This is also the first international standard in the field of distributed messaging launched globally in China. In November, the community suddenly became lively, and Dubbo was updated quickly, which caused a lot of attention. This year, Dubbo entered Apache and is currently in the incubation period.
Jim Jagielski, co-founder of the Apache Foundation, said that RocketMQ, the Apache top-level project, is an extremely powerful and transformative software project, and many companies are its deep users. Dubbo is currently incubating within the Apache Software Foundation and has huge potential.
The middleware performance challenge has been held for the fourth time so far. This is the first time that the competition topic is set on an open source background, allowing more technology developers to participate.
Below, we will make a detailed in-depth analysis of this competition topic.
Friends who know Dubbo know that Dubbo is not only a high-performance RPC communication framework, but also a complete set of microservice solutions - service registration and discovery, load balancing, service governance, etc. These are all familiar to us. Ability. However, Dubbo also has natural shortcomings, and the question of the preliminary round comes from this.
Problem Analysis
Friends who know Dubbo know that Dubbo is not only a high-performance RPC communication framework, but also a complete set of microservice solutions - service registration and discovery, load balancing, service governance, etc. These are all familiar to us. Ability. However, Dubbo also has natural shortcomings, and the question of the preliminary round comes from this.
original intention
Dubbo has been committed to providing Java applications with efficient, stable and production-ready RPC communication capabilities. Without using a RESTful interface, it is difficult for users to interface Dubbo with systems implemented in other languages. Therefore, this competition will break the barriers of language, and the participating teams can choose your favorite technology, mainstream or non-mainstream - We don't care - let Dubbo take the first step in the direction of multi-language step.
When it comes to Dubbo, we can't help but talk about microservices, and when it comes to microservices, there must be a place for Service Mesh.
Traditional microservices show us the future blueprint of service, and also provide many methodologies and best practices to guide us to complete the transformation of the architecture. But obviously friends who have implemented microservices must know that this is an extremely complex and uncertain transformation process - stripping the monolithic system and introducing service-oriented components (if Dubbo is not your first choice, you There is more reason to pay attention to this competition), convert internal calls into remote calls, and solve various secondary problems (network problems, security problems, state management problems, consistency problems, etc.) caused by the remoteization and distribution of calls Wait). Inside an organization with complex systems, such a transformation is nothing short of a nightmare. Think about connecting and serving all kinds of non-standard Java applications, PHP applications, Python applications, etc., either you are dreaming, or your customers are dreaming.