Engineering Insights

OpenSSL and zlib update assessment, and Node.js Assessment workflow

The Cloud is Not a Railroad - An Argument Against the Vertical Separation of Cloud Providers

There's a move to regulate cloud providers by vertically separating the services they offer. Like railroads of yore, who were not allowed to provide freight services on top of their base services, cloud providers would not be allowed to provide services on top of their base platform services. Vertical separation would be new to the cloud industry. Is it a good idea? Would it actually solve any problems? My answers are no and no, but probably not for the reasons you think. Let's dive in. Here are

Evaluating Language Model Bias with 🤗 Evaluate

What is Vitess: resiliency, scalability, and performance

Overview In today’s fast-paced development landscape, building software that is fast, scalable, and that resists outages can make or break the success of any application. Containerized systems with orchestration layers like Kubernetes enable this robustness at the software level. Implementing these protections into your database, however, can often require an entire team of developers and database administrators dedicated to managing multiple database replicas with custom sharding logic to prote

Building an interactive WebGL experience in Next.js

WebGL is a JavaScript API for rendering 3D graphics within a web browser, giving developers the ability to create unique, delightful graphics, unlike anything a static image is capable of. By leveraging WebGL, we were able to take what would have been a static conference signup and turned it into .the immersive Next.js Conf registration page In this post, we will show you how to recreate the centerpiece for this experience using open-source WebGL tooling—including a new tool created by Vercel en

From PyTorch DDP to Accelerate to Trainer, mastery of distributed training with ease

Regional execution for ultra-low latency rendering at the edge

As we work to make a faster Web, increasing speed typically looks like moving more towards the edge—but sometimes requests are served fastest when those computing resources are close to a data source. Today, we’re introducing to address this. Regional execution of Edge Functions allow you to specify the region your executes in. This capability allows you to run your functions near your data to avoid high-latency waterfalls while taking advantage of the fast cold start times of Edge Functions a

Vercel Edge Functions can now be regional or global

This changelog entry is historical. Edge Functions are deprecated for new projects. Use with the Node.js runtime and . Use for request-time routing before a response completes.Note:Vercel FunctionsFluid computeRouting Middleware Vercel Edge Functions can now be deployed to a specific region. By default, Edge Functions run in every Vercel globally. At launch, teams could run functions using the Edge Runtime in a specific region, placing compute closer to a database. This keeps latency low due