Unveiling Next.js Secret Sauce on the Edge

Mustafa Azeem is a full stack developer based in Amsterdam, Netherlands. He works at Shell and specializes in building portals and websites, with a focus on front-end development and deployment on the edge network.

Mustafa Azeem has expertise in building portals and websites, front-end development, and deployment on the edge network. He also has a background in data engineering.

Mustafa Azeem will discuss the edge network, edge zones, cost impact and optimization for portals and apps, edge runtime, and a hands-on demonstration of an edge runtime function specific to Verso.

The edge network is a series of globally distributed networks that provide low-latency, high-availability services by caching content and executing functions close to the user's location.

The edge network is important because it reduces latency and improves user experience by serving content from the nearest server, rather than a distant central server.

Edge zones are geographical locations where edge network servers are situated. These zones allow content to be cached and served from the nearest possible location to the user.

The edge network caches static content and serves it from the nearest server to the user, reducing the need to fetch data from a distant central server and thereby improving latency.

The cost implications of using the edge network include charges for edge requests, edge functions, and middleware functions. The costs vary based on the subscription plan and the number of requests.

An edge function is a piece of code executed at the edge network, close to the user's location. It is designed to reduce latency and improve performance by avoiding the need to create a dedicated VM or container.

Edge functions cannot use third-party libraries or packages that are not included in the standard Edge runtime APIs. They are also subject to executional unit limitations and may require careful planning to avoid overruns.