rest - Be RESTful: performance issue? -


our mobile application uses rest api communicate our server. @ beginning wanted keep restful, , keep using practices. but:

  • our api never public (only internal use)
  • the application more , more complex, , number of requests growing lot

i have observed public api big services not restful, because it's hard respect constraints.

so think instead of making 5 requests retrieve data, can make 1 request, parse json on client side? breaks important rest rule, improve performance on mobile application?

thanks

being restful provides no benefit. benefits of rest come individual properties (statelessness, client-server, resource-based), not being restful (or using word). can pick important properties of rest, implement them, , not rest (no pun intended).

for example don't need urls , meaningful verbs internal api. aethetic, not more productive. example: soap-based web-services away of less important rest principles keep of ones. webservices are productive technology, counts.

you should use middleware package internal api based on standard protocols ws-* , soap. web-services framework solves rpc-part of internal api. don't need create/parse urls , don't need deal serialization.


Comments

Popular posts from this blog

assembly - 8086 TASM: Illegal Indexing Mode -

Java, LWJGL, OpenGL 1.1, decoding BufferedImage to Bytebuffer and binding to OpenGL across classes -

javascript - addthis share facebook and google+ url -