REST Anti-patterns

Re:REST Anti-patterns by PaulHoule on Monday September 12, 2016 @11:23AM (#12480480)

This type of approach can be great. It is parallel to the idea to the "business is an exchange of documents", and the documents represent "transactions" in the sense of "an invoice", "a packing slip", "a deposit slip", "an order", etc.

[ Parent | on HN ]

Re:REST Anti-patterns by seagreen on Monday September 12, 2016 @11:32AM (#12480574)

> "business is an exchange of documents"

Did you just make up this phrase? It's really good!

[ Parent | on HN ]

Re:REST Anti-patterns by pbh101 on Monday September 12, 2016 @12:27PM (#12481066)

You would probably like reading [1] by Dan North.

[1]: https://dannorth.net/classic-soa/

[ Parent | on HN ]

Re:REST Anti-patterns by seagreen on Monday September 12, 2016 @04:12PM (#12483245)

  Imagine you want to implement a vacation-booking service 
  as part of an enterprise system. The first step is to 
  remove any reference to computers or modern technology. 
  This will allow you to concentrate on the business 
  objectives of the service, without getting sidetracked by 
  technological considerations. In other words, it enables 
  you to separate the “what” from the “how.”

That's pretty great advice.

[ Parent | on HN ]

Re:REST Anti-patterns by PaulHoule on Monday September 12, 2016 @12:33PM (#12481125)

I've been saying it for a while. I talked to the developers of this product about a decade ago:

https://www.kuali.org/kfs

and that was the thinking behind how that system was built. Also this is the paradigm behind

http://www.enterpriseintegrationpatterns.com/

and it must predate the computer.

[ Parent | on HN ]