Encore VS trpc

In this tutorial you will create a REST API for a URL Shortener service using Encore for TypeScript, a new way of building fully type-safe and production-ready distributed systems in TypeScript using declarative infrastructure.

At Encore, we've made it easier by making Pub/Sub is a native component in Encore's Open Source Infrastructure SDK.

⭐️ Support the project by starring Encore on GitHub.

Very cool. Reminds me of the encore framework, also written in go: https://github.com/encoredev/encore

Need to spend some more time looking into these go based frameworks, they seem great for quick prototyping

package url import ( "context" "testing" ) // TestShortenAndRetrieve - test that the shortened URL is stored and retrieved from database. func TestShortenAndRetrieve(t *testing.T) { testURL := "https://github.com/encoredev/encore" sp := ShortenParams{URL: testURL} resp, err := Shorten(context.Background(), &sp) if err != nil { t.Fatal(err) } wantURL := testURL if resp.URL != wantURL { t.Errorf("got %q, want %q", resp.URL, wantURL) } firstURL := resp gotURL, err := Get(context.Background(), firstURL.ID) if err != nil { t.Fatal(err) } if *gotURL != *firstURL { t.Errorf("got %v, want %v", *gotURL, *firstURL) } }

For something in the same vein but for Go, there is Encore: https://encore.dev / https://github.com/encoredev/encore

The framework is Open Source and the Encore platform provides free cloud hosting for hobby projects.

Encore is a backend framework for creating cloud backend applications where infrastructure is provisioned automatically from business logic.

RESTful API: RESTful API does not have machine-readable metadata cacheable, and query validation is not available.(There are some libraraies tried to solve this issue like TRPC)

tRPC + Cloudflare Workers Example

Hi I'm working with trpc + nextjs app dir (unsupported by trpc currently) and trpc context

I'm using TRPC with Next13 App directory and I can't manage to invalidate queries. Seing from their example there is a way to do it https://github.com/trpc/trpc/blob/96956e790e6862bcc6dcc4622edc8e48da0adbcb/examples/.experimental/next-app-dir/src/app/post-example/page.tsx

It is. But RSC make many library authors and maintainers question whether their library is still needed in a RSC world and if so how they can support it. Same story with tRPC https://github.com/trpc/trpc/issues/3297

Also, while trying to debug this, and this is way outside my league but I noticed this: Is there possibly an error in the Updater TS-definitions in https://github.com/trpc/trpc/blob/main/packages/react-query/src/shared/proxy/utilsProxy.ts at lines 155+156 & 167+168 because they are duplicate-lines and seems to be where my issues are coming from.

Unfortunately, tRPC and NestJs do not play well together by default, and the tRPC team does not intend to integrate the two through an official plugin for the time being.

- https://github.com/trpc/trpc: End-to-end typesafe APIs made easy. Never write another API contract again.