fehguy

5 ms·

1.
by fehguy 9y ago
Isn't it more work to write tests than code? Not sure that's the best argument against a technology. You can easily hang yourself many different ways. The idea with Swagger includes some rules, which is what makes it useful. If
2.
by fehguy 10y ago
Going to 141 chars would solve all their problems imho
3.
by fehguy 11y ago
Looks great vlad. It is true, this was the first known visual swagger editor and was a very helpful project (also open sourced). The Apigee folks went on to build the current version, a separate effort from the swagger-ui.
4.
Adding OAuth support in Swagger API Explorer(developers-blog.helloreverb.com)
4 points by fehguy 13y ago|2 comments
5.
by fehguy 13y ago
Moved from the swagger core project which had language specific details.
6.
Swagger spec for rest apis(github.com)
2 points by fehguy 13y ago|1 comments
7.
by fehguy 13y ago
https://github.com/wordnik/swagger-codegen does javascript, scala, java, objective-c, php, python (3), ruby, android, and even flash Also has the benefit of a commercial backer ( https://helloreverb.com ) and
8.
by fehguy 13y ago
swagger-js uses the shred library ( https://github.com/automatthew/shred ) under the hood so HTTP connections between the browser and nodejs work the same.
9.
The Fastest Way to Connect to an API with JavaScript(developers-blog.helloreverb.com)
3 points by fehguy 13y ago|1 comments
10.
by fehguy 13y ago
Generating a server stub was done long ago, in swagger, which is completely OSS: https://github.com/wordnik/swagger-codegen#to-build-a-server... And it's based on an intuitive JSON structure.
11.
by fehguy 14y ago
very cool tech behind this--html5 fragments, websockets.
12.
by fehguy 14y ago
Technique for interface-driven development for APIs could save a lot of hassle--generate your API description, view it in swagger-ui, generate your client, and finally server stubs. The plumbing is done, the business logic is up to you.
13.
Generating nodejs server from Swagger specification(github.com)
10 points by fehguy 14y ago|2 comments
14.
by fehguy 14y ago
Yes, the graph in the blog is just a sample. There will be a detailed post about performance coming, including access from browsers and non-browsers across fast and latent connections. The chattiness of REST across slow connections is one
15.
by fehguy 14y ago
Both browsers and servers need something like SwaggerSocket this--SPDY is a good step but i feel it's more of a "pipelining" solution rather than an async + multiplexing issue.
16.
by fehguy 14y ago
As a subprotocol, it leverages the readability of REST into something much more efficient. Maybe pseudo-REST is a better term
17.
by fehguy 14y ago
We tried out enunciate as well. It's good but didn't quite fit our needs... You can run swagger with the built-in support via swagger-core/swagger-jaxrs. Play 1.4/2.0 support is there as well and a number of folks are creating support for
18.
by fehguy 14y ago
I think the biggest difference is that this is a framework, not just a spec, and you can implement the server with the libraries. The google explorer makes it easy to consume google apis, which is great if that's what you're trying to do.
19.
by fehguy 14y ago
there is node.js... https://github.com/wordnik/swagger-node-express
20.
by fehguy 15y ago
We have a common communication interface (swagger) and have developed websocket-based communication between servers using the Atmosphere framework. Yes, HTTP overhead isn't trivial for chatty server communication. Sockets solve that
21.
by fehguy 15y ago
Yes! For communication this is part of the motivation for developing Swagger. For configuration & monitoring, our Caprica configuration tool keeps all the servers talking to the right services. It's not terribly complicated but not s
22.
by fehguy 15y ago
Netflix is an example to the opposite. But it is worth noting that a great model is a hybrid physical/cloud, once you have established predictable, steady load.
23.
by fehguy 15y ago
And when you need another data center, you shell out major coin. That's what we needed to avoid. At some point, even your finest physical server has limits. If you can split the work up into smaller pieces that execute in "parallel" fashi
24.
by fehguy 15y ago
There is no question that physical machines are faster than VMs. The main issues are fixed cost, burst capacity, multi-datacenter deployments and linear scaling. That was the main point of the migration. There is nearly zero unused capac
25.
by fehguy 15y ago
Sounds like the open-sourcing of http://swagger.wordnik.com is well timed and can help with this
26.
by fehguy 15y ago
Creating an easy mechanism for declaring a web service signature AND it's models makes this work. Does this pick up where WADL left off?
27.
Wordnik's swagger api framework(swagger.wordnik.com)
5 points by fehguy 15y ago|2 comments
28.
by fehguy 15y ago
super slick
29.
by fehguy 16y ago
I'm somewhat biased but after looking long and hard for a good rest documentation system, i think this is the right way to do it.
30.
by fehguy 16y ago
Kinda depends on the use case. Let's say you have a caching layer and update a subtree in your RDBMS. Then you need to go find all values referencing that object and invalidate them. That's potentially a lot of complexity. Of course you

More ›