All geek questions in one place

Restlet vs Spring MVC for Restful web service

Iā€™m learning the best way to create a Restful web service in a Google application. My ultimate goal is to get the Android app to call the GAE web service to publish and retrieve data. At the moment, I'm not sure what the best approach is.

What I know at the moment is Spring MVC 3 provides the ability to create a web service, but does not provide a full implementation of JAX-RS. I also read several blogs that talk about how Spring and Restlet can be combined together. On the other hand, I read that I can only use Restlet in GAE. I would also like to provide an easy web interface for users to view their published data.

So my questions are these. 1. Should I just use Restlet. 2. Should I just use Spring MVC to provide my Restful web service. 3. Should I use Spring and Remlet together.

At this point, I think I should invest my time in Restlet, because this is the best approach for calling web services in Android. I also discuss if Spring MVC just killed.

Any thoughts would be helpful.

+4
source share
3 answers

I recently installed RESTlet on GAE and it was an absolute breeze! There are documents describing the procedure on the RESTlet website, and I ran RESTlet in GAE using the Google data store for two hours.

The main disadvantage is that the performance of the Google data warehouse for low volume applications is terrible. Timeouts are not uncommon. (Google requests a maximum request time of 30 seconds, and your application can easily take half of what comes out of sleep mode if it has not been available recently)

Now I am creating another RESTful application and have chosen the path Spring 3 MVC / Hibernate / MYSQL. I am not new to Spring DI or MySQL, but I am new to Spring MVC, and I need days to work on all the problems that I encounter. I am disappointed with the quality of the documentation available, and I could not find a reasonable and complete tutorial on

+1
source

I have no experience with Restlet, but Spring MVC 3.0 is efficient enough to create a calm webservice AND webapps. Therefore, if you also plan to make your service accessible through browsers, then this is a great solution, since your controllers can serve both applications and browsers.

Perhaps this is also possible with Restlet, but I have not heard about its capabilities for creating webapps.

Remember that Spring has a long boot time. This means that you must be careful to avoid slow responses from cold starts.

0
source

Source: https://habr.com/ru/post/1307203/

More articles:


All Articles