Wissmueller

Hey HN, we're Sebastian and Mish and we are working on EdgeNode - A global serverless deployment platform. Typically, most applications are hosted in a single location. This makes the experience worse for the users based further away due to high latency. Higher latency leads to decreased conversion rates, impairs user interactions and ultimately reduces customer satisfaction.

Amazon and Google operate their services globally to eliminate this issue and increase service reliability. However, setting up and maintaining such an infrastructure is technically challenging and very costly.

With EdgeNode, we want to enable companies to scale globally in a cost-effective and developer-friendly way.

EdgeNode runs your existing apps (Next.js, Ruby on Rails, Laravel, Spring, Django) or Docker containers globally on the edge, no modifications required. Your application scales down to zero instances when there are no active requests, so you only pay for the resources you use.

We're committed to make global deployments as simple as possible. To achieve that, we will offer a one-click deployment process, eliminating complex configurations and minimizing the time and effort required to get your application up and running on the edge.

Please sign up for Early Access and let us know what you think!

Hey folks, We just released Garph 0.5

Garph enables you to build end-to-end type-safe GraphQL APIs using TypeScript. It aims to provide the best possible DX for GraphQL.

Changelog:

  - Updated the React-client
  - Added GraphQL Subscriptions
  - Cursor-based pagination
  - Included Relay building blocks (nodes, edges, connections)
  - Additional type-safety for resolvers
  - Updated Documentation

Perfect use-case for Garph:

You have a TypeScript backend and TypeScript frontend and want to expose the GraphQL API to third-party consumers or add a mobile app into the mix

And since Garph produces a spec-compatible GraphQL API you can use it with existing tools like Hasura, Apollo, Stellate, AWS AppSync, etc.

> Across all these frameworks, it feels like a footgun your users will discover on their own

Exactly. tRPC and other projects alike don’t provide you an actual API that you can later consume, but an RPC “glue”