svelte-query VS serverless-graphql

Nice I was waiting for this! I'm using the old implementation: https://sveltequery.vercel.app/

I'm aware there's another Svelte Query here but it seems like it is not maintained and will be incorporated into Tanstack Query.

Until then I use Svelte Query

I like React Query so I would be excited to use this however it doesn't seem ready for Svelte given the docs "Coming Soon" and Svelte Query being relatively unmaintained.

Svelte Query :)

Or just use svelte-query and toss that observable junk to the side.

Exactly. That's the big thing I want to work on next. Not sure whether to use Svelte Query or manually cache the data. In an ideal scenario all the API calls are cached because if two users hit the site at the same time, for instance, there's no need to request the same data twice. This is getting to the edge of my skillset but psyched to try to learn this part.

That's it. Nothing highly sophisticated. It is mostly the tech I enjoy and I think is valuable in the future. There are also other libraries I really enjoy, like XState and React Query (there is also Svelte Query). Just to mention a few.

Caching: svelte-query, sswr

Since then, the ecosystem has changed. Using the Serverless Framework makes deployment simpler. We released the managed Tracetest App making any serverless-based systems simpler to instrument and test. You can now test public-facing apps with no infra overhead!

We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!

When we think about AWS serverless service, the first thing that comes to our mind is Lambda function. Yes, the quickest way to deploy this backend Express JS app to AWS is to deploy it as a Lambda function. The easiest way is using Serverless Framework.

Serverless Framework: https://www.serverless.com/

Github | Website

In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.

Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.

1 - Serverless + AWS CDK + Lift: An integration that amps up the traditional Serverless Framework with Lift's static frontend construct and CDK's robust infra definition.

It's a bit easier in Python if you use tools like https://www.serverless.com/. I'm not sure if Rust has something similar yet.

Serverless