And what happens when you start applying complex business rules that needs to scale? So many questions about this approach...
And what happens when you start applying complex business rules that needs to scale? So many questions about this approach...
Throw in ETAGs and you can do a lot of cool stuff to make things scale really well.
But sending SQL from the client is dangerous, and in this forum you'll get some interesting looks suggesting that.
Quite unclear why you'd layer all the HTTP and marshalling overhead on backend service calls, other than to ensure you always have slow requests.
More here in the value of services (Yegge's rant): https://plus.google.com/+RipRowan/posts/eVeouesvaVX
http://martinfowler.com/articles/microservices.html
http://martinfowler.com/bliki/MonolithFirst.html
http://martinfowler.com/articles/microservice-trade-offs.htm...
A database IS a service. It's just not a 'restful web service'. Making it one doesn't gain you any useful abstraction for SOA.