What is Deno?
What about Fresh?
The lack of NPM packages means that larger frameworks like Next.js, Remix or even Gatsby are not available. Fresh now aims to fill that gap. In doing so, it also has intriguing approaches and features of its own.
- The second major feature of Fresh is that it does not require a build step. It does not require a web page to be pre-generated first.
- TypeScript is supported from the beginning, like routing.
Also, Fresh relies on the Edge. This means that Fresh is designed from the start to run on the Edge. But what does the Edge mean?
What is the „Edge“?
The „Edge“ denotes a specific server architecture. Instead of using a single server for all global requests, multiple servers with the same program across the world are used. By doing so, the distance between user and server is reduced. This results in faster communication between the server and the end user. However, in our use case the edge means mostly serverless functions that are distributed across multiple servers around the globe. The usefullness for the final application depends on the degree of decentralization of the given application. If the functions can be executed on their own, the edge can offer a speed advantage. However, if the data has to be loaded from a certain point, the advantage is sometimes limited.
Fresh has interesting approaches and a modern feature set. However, the „make or break“ point is the use of Deno. For the Deno world, Fresh is a very welcome framework as it extends the full stack capabilities of Deno. But if you have a complex application on top of an existing NodeJS architecture using many NPM packages, switching proves to be difficult.