I love the concept of Edge computations. MicroVMs do play a major role in enabling this lightweight execution layer. Need for more speed in web apps will always keep increasing with time. To develop a fast app there are always two parts to it:
Part 1 - Infrastructure - Bringing computations closer to users can effectively reduce the response time of applications. Fly makes this super easy with MicroVMs on Edge.
Part 2 - App Development- Converting business ideas to apps should be frictionless. This is the motivation for Fringe. GraphQL tooling in frontend can become complex as projects grows. But what if just like serverless functions we could declare our GraphQL queries in plain files which become active RESt endpoints on deployment. The differentiating factor here is the caching of GraphQL responses (Normalised Caching) available at edge. The project is inspired by the file based routing applications like NextJS, Flareact and good old php days. Fringe offers execution and caching at Edge for functions and graphql.
Fringe is still a work in progress. It would be great if you could please take some time to have a look at the repo and concept. I am also open to any suggestions, even negative 😅.
I am gradually adding optimisations with time. But at high level on Roadmap I have following
1.) React Server-Side Page Rendering with caching
2.) Cache Invalidation
I love the concept of Edge computations. MicroVMs do play a major role in enabling this lightweight execution layer. Need for more speed in web apps will always keep increasing with time. To develop a fast app there are always two parts to it:
Part 1 - Infrastructure - Bringing computations closer to users can effectively reduce the response time of applications. Fly makes this super easy with MicroVMs on Edge.
Part 2 - App Development- Converting business ideas to apps should be frictionless. This is the motivation for Fringe. GraphQL tooling in frontend can become complex as projects grows. But what if just like serverless functions we could declare our GraphQL queries in plain files which become active RESt endpoints on deployment. The differentiating factor here is the caching of GraphQL responses (Normalised Caching) available at edge. The project is inspired by the file based routing applications like NextJS, Flareact and good old php days. Fringe offers execution and caching at Edge for functions and graphql.
Fringe is still a work in progress. It would be great if you could please take some time to have a look at the repo and concept. I am also open to any suggestions, even negative 😅.
I am gradually adding optimisations with time. But at high level on Roadmap I have following 1.) React Server-Side Page Rendering with caching 2.) Cache Invalidation