Last time someone submitted a draft of a blog post I accidentally published on my private blog titled "I'm doing HTTP wrong" about a talk I gave at PyGrunn 2012.
I since pulled that and rewrote it to better show what our infrastructure is actually like.
I'm more than happy to answer questions about that :-)
the original article isn't fresh in my mind anymore, but I enjoyed this one and found myself agreeing more. :)
FWIW, my opinion is it is very similar to how things are done on appengine. You want to schedule a task? you make a form post to an end point thats setup to be monitored by their service. you want to talk to a backend instance? post to it. maybe their rpcs work the same way (serialize to protocol buffer, post to endpoint, get response, deserialize protocol buffer).
it feels low tech and un-sexy, but it works and it's easy to understand.
So, I am just about writing something that would describe my REST API (possibly generate handlers from description) and integrate very nicely with Sphinx for docs, and I can see (on slides) you already have something like that. Am I right? Do you plan to share something like that? Thanks.
7 comments
[ 4.4 ms ] story [ 44.1 ms ] threadI since pulled that and rewrote it to better show what our infrastructure is actually like.
I'm more than happy to answer questions about that :-)
FWIW, my opinion is it is very similar to how things are done on appengine. You want to schedule a task? you make a form post to an end point thats setup to be monitored by their service. you want to talk to a backend instance? post to it. maybe their rpcs work the same way (serialize to protocol buffer, post to endpoint, get response, deserialize protocol buffer).
it feels low tech and un-sexy, but it works and it's easy to understand.