Agree with you. Looking forward to the detailed plan
Guangdong Liu <[email protected]> 于2024年9月22日周日 11:42写道： > Hello dev; > > The current rest api implementation is to use the native Hazelcast rest > api, which is simple but there are very many limitations, such as the > inability to customize the url, the performance is not as good as jetty, > and scalability is not enough. Below is a detailed comparison. > > *Shortcomings of Hazelcast Native REST API* > > - Limited Functionality > > The Hazelcast Native REST API offers basic functionalities and > lacks support for complex web features such as advanced routing, session > management, and middleware, making it unsuitable for intricate web > applications. > > - Insufficient Scalability > > Designed primarily for internal REST command handling, the > native REST API lacks high customizability and extensibility, limiting its > ability to meet projects with complex business logic and customization > requirements. > > - Performance Bottlenecks > > In high-concurrency scenarios, the performance of the native > REST API may lag behind specialized web servers like Jetty, potentially > leading to increased response latency and resource consumption. > > - Security Limitations > > Hazelcast Native REST API provides limited security features, > lacking advanced authentication and authorization mechanisms, which > elevates the security risks within the application. > > - Limited Community Support > > Being a part of Hazelcast, the native REST API has relatively > scant community support and documentation resources, making it challenging > for developers to obtain timely assistance when issues arise. > > *Advantages of Jetty* > > - High Performance and Concurrency Handling > > Jetty, as a high-performance Java HTTP server, efficiently > manages a large number of concurrent requests, making it suitable for > applications requiring high throughput and low latency. > > - Comprehensive Feature Support > > Jetty fully supports the Servlet specification and offers > advanced routing, session management, filter chains, and other middleware > functionalities, making it ideal for building complex web applications. > > - Highly Customizable and Extensible > > With rich APIs and a plugin mechanism, Jetty allows developers > to customize server behavior and functionalities flexibly based on project > requirements, enhancing system flexibility and maintainability. > > - Robust Security Features > > Jetty provides extensive security features, including SSL/TLS > support, various authentication and authorization mechanisms, and security > plugins, ensuring the security of data transmission and access controls. > > - Extensive Community Support and Documentation > > Jetty boasts an active community and comprehensive > documentation, enabling developers to easily access support, share > experiences, and utilize a plethora of open-source plugins and tools, > thereby reducing the learning curve and integration challenges. > > - Stability and Reliability > > As a mature project, Jetty has been extensively validated in > production environments, offering excellent stability and reliability, > which helps minimize system failures caused by server issues. > > *Conclusion* > > In summary, the Hazelcast Native REST API presents significant limitations > in functionality, scalability, performance, security, maintenance, and > integration, which hinder its effectiveness in complex front-end and > back-end unified projects. On the other hand, Jetty stands out as a > high-performance, feature-rich, and highly customizable web server capable > of addressing the demands of modern Java applications. > > Therefore, it is recommended to phase out the Hazelcast Native REST API and > adopt Jetty as the unified front-end and back-end server solution. This > transition will enhance system performance, strengthen security, improve > maintainability, and provide a robust foundation for future feature > expansions. > > -- > > Best Regards > > ------------ > > Liugddx > [email protected] >
