3 ms·

just drop this REST hype altogether and use adequate protocols for communication

• pyre 9y ago
  As in design a custom TCP/IP protocol for every application?
  • stingraycharles 9y ago
    I think there are a few GraphQL enthusiasts entering this thread right now, which has its own merits, but can live perfectly next to REST.
    • konschubert 9y ago
      In my company we use graphql for getting, and REST for all other operations. Might be an antipattern, but has served us well. We're also using a special flavor of graphql that returns the data as flat dictionaries instead of deeply nested dictionaries. Whether you need that or not of course depends on the client design.
  • kuschku 9y ago
    As in using GraphQL for this purpose, I presume. Or even offering an SQL-API. Seems more ideal than overly complicated URL schemes.