News for hackers. Stuff that matters.
Re:Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda by MichaelBurge on Monday April 24, 2017 @05:31PM (#14188504)
Seeing all those services hooked together gives me the willies. It sounds like a right PITA to debug, and chaining them together in serial for a single request multiplies the chance of an error even if each individual node is pretty stable.

I guess it's okay for a demo though. They're probably not setting an example so much as trying to throw as many services together to show off the technique.

Re:Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda by zackmorris on Monday April 24, 2017 @06:01PM (#14188782)
Ya the only way I could ever see this being maintainable is if it's declarative. It takes a tremendous amount of boilerplate and configuration to perform what comes down to a one liner in any functional language or a formula in any spreadsheet. I think I would be more interested in a transform that converts a series of goroutines to lambda functions or something.
Re:Going Multi-Cloud with Google Cloud Endpoints and AWS Lambda by jankedeen on Tuesday April 25, 2017 @05:59PM (#14198503)
You know, architecturally, at application level no one wants to deal with this but devs orchestrate nightmarish dependencies for deploys and hit 'endpoints' with aplomb in service architectures with only a playbook or data blueprint to follow. What's the point of fighting this?

Let the kids play.