TJ Holowaychuk, creator of Express and Apex, writes on Node.js, AWS Lambda, serverless tools, Go and C libraries.
HN links it for serverless advice on AWS Lambda and Up, his Apex logging approach, and his post Farewell Node.js on moving to Go.
This looks interesting but the screencast video kind of failed to make the point in my opinion. Take a look at serverless talks or apex intro https://medium.com/@tjholowaychuk/introducing-apex-800824ffaa70 for how to prepare a better illustration that proves your point.
> Isolation is not a real issues today, containers can provide complete isolation between runtimes and much more.
Most people will not necessarily agree. Containers don’t provide complete isolation and from a theoretical standpoint they never will (unless we rewrite the Linux kernel). There have been security vulnerabilities in the past about this and there will be, it’s just the way it is. Your argument here should probably be ”it's safe for single tenant use“ i.e. all the code runs on effe is your company's code.
Also coming back to the video again, I just can't fully understand what this project does, it just looks like a Go web server framework.
This is an excellent write-up and a great use-case for what S3+Lambda can do. As AWS offerings go, I believe Lambda has a tremendous upside and will be growing significantly over the next few years.
I've been throwing a lot of my own personal resources into building some things on top of both S3 and lambda and have found a few tools that help with it quite a bit. For one - the lambduh project from Russ Matney has been a great resource for abstracting out some of the more common s3->lambda workflow: https://github.com/lambduh/lambduh. On a different note is T.J. Holowaychuk's Apex project: https://medium.com/@tjholowaychuk/introducing-apex-800824ffaa70
IMO it'd be a really smart move for Google to hire Vitaly to help with the launching of this feature and things around it. He has done a great job with PhantomJS.
Even an acquisition[1] of PhantomJS would totally make sense, then let him keep working on it but based on headless Chrome and with real resources.
[1] Careful how you spin it for this route, learn from TJ/Express https://medium.com/@tjholowaychuk/strongloop-express-40b8bcb8e5af
This was in response to TJ Holowaychuk's blog post: "Blueprints for up" https://medium.com/@tjholowaychuk/blueprints-for-up-1-5f8197179275 (running express/connect as a child process of Lambda)
and curiosity as to how far Lambda is from being used for anything latency sensitive - but it turns out Lambda isn't the slow part - it's API Gateway.
Amount of "otel" instrumentation required in your code by LOC looks ridiculous to me.
Isn't it a better approach to just use logs?
e.g.
defer ctx.WithField("path", path).Trace("opening").Stop(&err)
from https://medium.com/@tjholowaychuk/apex-log-e8d9627f4a9a
I must say that this sounds exactly like TJ's Up blueprints [1]. TJ've been working on Apex Up for over a month [2].
[1]: https://medium.com/@tjholowaychuk/blueprints-for-up-1-5f8197179275
[2]: https://github.com/apex/up