3 ms·
For my recent projects, I've used Go + DynamoDB for a GraphQL backend, and Next.JS with SSR on the frontend. Deploying both to lambda with Apex Up. Stripe for b
by zhobbs 8y ago
For my recent projects, I've used Go + DynamoDB for a GraphQL backend, and Next.JS with SSR on the frontend. Deploying both to lambda with Apex Up. Stripe for billing, SendGrid for transactional email.
- 11235813213455 8y ago"Next.JS with SSR on the frontend" I call that backend, and node is pretty good for graphql too (graphql-js), full JS make a lot of sense (add flow/TS to get more type-strength)
- dpeck 8y agoAny tips on the go/dynamodb side of things? I’ve looked at it and experimented a little and it seems quite easy to get data into dynamodb and quite convoluted to get it out.
- zhobbs 8y agoI'm using https://github.com/guregu/dynamo https://github.com/guregu/dynamo for the data reading/writing. In my experience, the trick with Dynamo is the schema design. I haven't had problems with the libraries/queries as long as the schema made sense for how I'd be accessing the data.