Hey apologies if this has been covered, i have an ...
# sst
b
Hey apologies if this has been covered, i have an SST Federated GraphQL side project I've been working on written in Typescript and Go, i wanted to switch the lambdas over to Graviton, currently the only way to do that in Go is using a custom runtime and naming the build file as bootstrap, is it correct to say its not possible to do this at the moment with SST/Live Lambda Dev? The TS Lambdas are moved over fine 😄
t
I have a fix for this in something I'm releasing soon, we'll build for arm64 if we detect graviton
b
@Bobby Ross I’d be really curious about your experience with federated graphql - I’ve been wanting to move my team towards that (and yeah, with sst). So I’d be very interested if you ever feel like sharing your experience 😄
b
Sounds great @thdxr ! I’ll keep the Go lambdas as they are for the time being, hopefully AWS make Go available in arm64 soon which would have made it much simpler.
Hey @Blake E Absolutely 😁! I’m always happy to talk Serverless, GraphQL or just code in general. Happy to share the repo here if that would be any use? It’s still very early in development - i built it as a POC to see how Federated GQL Works in a fully serverless environment and as something to demo when i start looking for a new role. Tech Stack/Infrastructure React App (TS) Cognito Auth to Apollo Gateway (TS & SST) Management Subgraph with JWT Authentication ( Go & SST ) Account Subgraph with JWT Authentication ( Go & SST ) - Todays task Backed by DynamoDB Dynamo may seem an odd choice, I'm a big fan of single table design with dynamo, i’ve used it successfully in the past but never with GraphQL, i wanted to see if planning the schema ahead/using shallow duplication I could get it to play nicely. I would say the biggest issue I've come across so far is with latency/authentication between the gateway and subgraphs. I deliberately choose to use 2 separate authentication types to understand how bad the latency could get ( i might not always be in control of the subgraphs authentication ) but i’m planning to switch over to a lambda authoriser in the next week to take advantage of token cacheing to see how that helps performance. Hopefully that is at least some use, I'll add a readme to the repo so if you did have any interest at looking it over/running it locally it might make a bit more sense
m
I’m using AppSync with lambda and prisma/aurora serverless
i dunno if you can do federation with appsync directly
b
For anyone interested here is the repository, still very much a work in progress - https://github.com/brossdev/serverless-federated-gql-api
b
Thanks for Sharing @Bobby Ross!