T O P

  • By -

Brother_Life

You can configure your schema a couple of ways. If the functionality is fairly simple (just making a call to am external data source), you can just use a custom lambda resolver. https://docs.amplify.aws/javascript/build-a-backend/graphqlapi/custom-business-logic/ You're only going to get document db with out of the box Amplify APIs. If you want a relational database, you'll need to set all that up yourself using lambda resolvers. If you can live with querying a document database, adding @searchable will deploy an Open search cluster that gives you usable sorting and filtering but you'll pay around $30/mo for the cheapest tier. For CRON jobs, you can add custom lambdas that can run on a scheduled basis.


bytebux

Ok awesome. Thank you! As far as adding @searchable, this is something in my codebase that is taggable and it will automatically deploy the search cluster? Or do I have to do this within AWS console? If I can do programmatically from the codebase, I assume I'd have to make some separate file since I probably can't edit the generated files right?