4 ms·
It's a tough tradeoff between performance flexibility. Relying on HTTP + JSON is very nice when you have lots of teams, codebases in several languages, and want
by sbilstein 12y ago
It's a tough tradeoff between performance flexibility. Relying on HTTP + JSON is very nice when you have lots of teams, codebases in several languages, and want to preserve the ability to talk quickly to any service over HTTP.
I like working HTTP but certainly tools like thrift have there. LinkedIn is all about http://rest.li/ http://rest.li/ for our services though I've been working with DropWizard on a side project and really love it.