Is anyone running a load test for the Restful framework and would like to share the conclusion?
Thank you very much!
An important driver of REST is its scalability, the quality of the distributed system, you can Adapt to the increase in usage by increasing the system size and cost proportionally. Caching is a key technology for achieving scalability. Therefore, if you allow your representation to be cached, most of the load is actually not borne by the identity management system, but It is borne by the downstream web cache. This has nothing to do with the REST framework.
Your back-end database technology may be another major factor in system performance and expansion. Adjusting the database system and optimizing queries may pay off here. Also consider whether it makes sense to add a database caching layer (for example, OpenSymphony).
We found that the serialization cost is very important to us. If we use Kryo or Smile binary serialization, the overall request rate is the best Good. If you need text serialization, we found that the Jackson JSON serializer is much faster than the XStream XML serializer, doubling the overall request rate. This may be an area to consider.
So , If you have not done so, please check your system from a zoom perspective. See http://www.highscalability.com, Richardson and Ruby’s Restful Web Services (O’Reilly), Cal Henderson’s Building Scalable Web Sites, and Theo Schlossnagle’s Scalable Internet Architectures started.
I’m trying to figure out what the Java Restful framework is the most suitable identity manager server for overloading.
Someone has a Restful framework Run load tests and are willing to share conclusions?
Thank you very much!
Good question! You may find that the choice of framework is not the main determinant of performance/scalability. We use Restlet, based on a strong recommendation from a former colleague who used it to develop Overstock.com (a very large e-commerce site). It has Good performance, suitable for Overstock.com. But we did not make any head-to-head comparison.
An important driver of REST is its scalability, the quality of the distributed system, you can Adapt to the increase in usage by increasing the system size and cost proportionally. Caching is a key technology for achieving scalability. Therefore, if you allow your representation to be cached, most of the load is actually not borne by the identity management system, but It is borne by the downstream web cache. This has nothing to do with the REST framework.
Your back-end database technology may be another major factor in system performance and expansion. Adjusting the database system and optimizing queries may pay off here. Also consider whether it makes sense to add a database caching layer (for example, OpenSymphony).
We found that the serialization cost is very important to us. If we use Kryo or Smile binary serialization, the overall request rate is the best Good. If you need text serialization, we found that the Jackson JSON serializer is much faster than the XStream XML serializer, doubling the overall request rate. This may be an area to consider.
So , If you have not done so, please check your system from a zoom perspective. See http://www.highscalability.com, Richardson and Ruby’s Restful Web Services (O’Reilly), Cal Henderson’s Building Scalable Web Sites, and Theo Schlossnagle’s Scalable Internet Architectures started.