OpenAPI Arazzo : Non-functional Call Flows

OpenAPI Arazzo : Non-functional Call Flows

So you by now have seen the drama. I opened an issue with Openapi Arazzo project talking about how they didn't address internal redirects. What was their response?


A maintainer claimed I made it up. That I made up 'internal redirects' even though they exist in every api application:

  • spring/springboot (forward)
  • nodejs (loopback)
  • Aws Lambdas (step functions)

They even went so far as to LIE and say they sat down with Roy Fielding and he said their was no such thing:


What happened when I emailed Roy Fielding? He said the question was never asked and there DEFINITELY is internal redirects in APIs:

I don’t recall hearing that question (nor it’s context), but the term “internal redirect” was created for NCSA httpd (and continued by Apache) to refer to requests internal to the server implementation (like a file include), in contrast to "external redirect" being an HTTP 3xx response message.

So I reopened the ticket asking if they were going to say Roy Fielding was wrong. Their response?


Suddenly, they went from 'does not exist' to 'not planned'.

Does anyone at OpenAPI even understand API's?

Do these guys even know what they are doing?

They want a standard for API call flows and are going to leave out 50% of call flows!!!


Conclusion

Do no use Arazzo. These guys are only GUESSING their way through API's and don't even understand how backends work. The most experience they have is some Nodejs... and that will NOT cover your bases.

Until these guys start learning how to work with the experts they rely on, they are never going to have a product that is usable.

要查看或添加评论,请登录