+1 1 0
Published 8 years ago by NerfYoda with 2 Comments

Join the Discussion

  • Auto Tier
  • All
  • 1
  • 2
  • 3
Post Comment
  • jmcs
    +3

    He forgot that HTTP and JSON are universally supported and that 90% of the issues described are bad engineering and bad development practices and not a problem with REST.

  • crincon
    +3

    Yikes, no. HTTP and JSON, are simple, platform- and language-agnostic, and easy to write and to understand. There's no complexity, no room to hide bugs in the transport layer. It's all at application level, where you can get at without having to become an expert in silly XML schemas, or some RPC library, or, God help us, bloody CORBA or DCOM, or whatever monstrosity these object oriented, "static typing" herberts come up with next.

    There is absolutely nothing wrong with there being no batching, paging, sorting, in the transport layer. It doesn't belong there. There's nothing wrong with "reinventing JSON RPC" if you really need it -- it's dead simple. Or, if you really need XA transactions and stuff, well then use MQ or whatever for your particular fancy service. It is way better that you have to do this, than for the vast majority of us, who just need to pass a simple message through, to be forced to deal with all that rubbish.

    Yeah, this bloke is off his rocker.

Here are some other snaps you may like...