2,615 karma · joined January 9, 2014
Stuff I’ve built/participated in:
https://www.narakeet.com, https://votito.com, https://bugmagnet.org
Previously worked on https://www.mindmup.com, https://claudiajs.com
My books: https://gojko.net/books/
the big difference is that for the most part, google users/developers/... are not really customers.
I assume that 50 years ago the cost of getting information out to people was quite significant. printing, distribution, logistics... a single researcher wouldn't be able to deal with lots and lots of publishing institutions efficiently, and a single institution (except for the largest ones) wouldn't be able to publish efficiently. at my uni school, they had 2 geometry professors, and they perhaps published something every few years. no need for the school to publish its own geometry journal. middle-men such as Elsevier emerged to provide a useful service, achieving efficiencies of scale on both ends, providing a publishing channel for smaller schools and a discovery service for researchers. kind of the same as why travel agents existed. it was too difficult for a single person to deal with all the hotels and airlines in the world, and they didn't even know where to go and ask about that stuff.
Today, the cost of getting the information out to people being insignificant, they are an obstacle instead of being an enabler, adding very little value to what people can do directly. On the other hand, as long as they can keep the effective monopoly going, they can milk the market. Travel agents didn't have a chokehold on a market, and got easily disrupted by web sites. Elsevier requires regulators to step in.
http://stackoverflow.com/questions/4456438/how-to-pass-null-...
useful depends on the target. something might be useful to you but not to other people. big part of successful product management is deciding on good market segments. as a casual user of a tool, you might not be in a segment that the project maintainers care a lot. annoying maintainers won't help at all if that is the case. learning about the code and fixing it will.
instead of trying to annoy people who volunteered their own time to build something useful, why not submit a pull request instead? if it's that important to you, invest a bit more into solving the problem than just complaining online.
It's funny how the plunge, a singular event, is now news, rather than the trend over time. sure enough, last week it was the surge, another singular event... short term view presented in market news never stops amusing.
I recently published the scripts evolved from our usage to simplify deployments as https://Github.com/claudiajs - the tool is mature, and allows teams to use API GW almost as easy as if it were a lightweight web server
Likewise, Lambda can execute events from SNS, Cloudwatch Events, Dynamo and a lot more, including the Amazon workflow system.
another thing is that although Api GW can behave like a web server for most things, some things are more restricted than with a fully programmable server. for example, you need to declare all HTTP response codes upfront, so that the pipeline can be configured. There can be only one success code (so eg returning 204 when there is no content and 200 with content from the same endpoint isn't trivial).
the third thing, that several commenters mentioned on this page, is that if you want to use API Gateway, processing binary data requires S3 or something else for storage. We currently let people convert files by using ApiGW + Lambda to get a signed URL for S3, then post to S3, another Lambda converts it into PDF and saves back to S3, and the client polls S3 to pick up the result. It's fantastically scalable with that design, much better than posting a file to heroku and then getting a synchronous response, but it takes a bit of rearranging the code to work.
We've been running APIs on it for six months with no issues, and are now in the process of moving the entire backend from heroku to Lambda. So far, no major issues.
Regarding Lambda being a building block, I actually like that. Werner Vogels points out [1] that one of the key lessons from 10 years of AWS is that the market wants primitives, and that the higher-level toolkits emerge from that. A ton of third-party helpful stuff is already out, such as apex, serverless and so on. We built a toolkit[2] that lets people use Lambda and API Gateway from JavaScript very similar to lightweight web frameworks (eg api.get('/hello', function (request) {...})
Documentation is there, just not in the most sensible places, and the whole pipeline is optimised for Java processing (eg Velocity VTL for API Gateway transformations allows people to do everything they need, as long they know the Java collections API executed below).
[1] http://www.allthingsdistributed.com/2016/03/10-lessons-from-...
For access keys, so far I stored them as stage variables in the API Gateway config. Claudia adds all stage variables to the env key of the request passed to the Node.js handler. That way, they are instantly available to your function, but never shared with Web clients.
I'm not entirely sure how secure this is, but the use cases I used it for are not highly risky. This is, I imagine, equivalent to storing them in the ENV variables for heroku services. (what I migrated from)
one additional benefit of stage vars is that you can use different values for production, dev and testing, and it all works out of the box.