@southpolesteve have you ever tried something like this: https://github.com/jbaxleyiii/basic-up-engine-example …? Deploying a Express service to Lambda, all without importing _any_ Lambda code . . . Pretty neat!!
I've done it this way. I find you quickly grow out of it. One big benefit of lambda is route isolation. Dumping it all in one fn leads to cold start issue and slow deploys. Matters less for graphql I guess. But why even include express then?
-
-
Still I'm not opposed to it as a way to start off with serverless. Not everyone agrees. Side note: I don't get why I need to deploy apollo engine. Would much prefer they expose an API I can send tracing data however I choose.
-
Another thought. I think we'll see more frameworks pop up that are serverless first. They prob won't be lambda specific either. But they will force you into app structures that can be easily code split into functions and also run locally as one big application.
-
Yeah. We have been thinking a lot about defining remote Apollo Data sources that are actually just Lambdas, and having your Gateway just be one big merge. I feel like a framework could definitely make use of that.
-
Would also be super cool if there was a wrapper for Node Lambda function handlers where instead of exposing this: function(event, context) {} you exposed: wrapper((parent, args, context, info) => {})
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.