Engineering Insights

OpenSSL November Security Release

Announcing Vitess 15

Vitess 15 is now generally available, with a number of new enhancements designed to make Vitess easier to use, more resilient, and easier to scale! VTOrc release VTOrc, a Vitess-native cluster monitoring and recovery component, is now GA. VTOrc monitors and repairs Vitess clusters, eliminating paging and manual intervention while automating recovery. This makes Vitess fully self-healing and resilient to MySQL server failures. It also replaces the third-party integration with Orchestrator that us

Node.js 18.12.0 (LTS)

Next.js 13

Next.js 13 introduces layouts, React Server Components, and streaming in the app directory, as well as Turbopack, an improved image component, and the brand new font component.

Introducing Turbopack

Vercel's mission is to provide the speed and reliability innovators need to create at the moment of inspiration. Last year, we focused on speeding up the way Next.js bundles your apps. Each time we moved from a JavaScript-based tool to a Rust-based one, we saw enormous improvements. We migrated away from Babel, which resulted in . We replaced Terser, which resulted in toreduce load times and bandwidth usage.17x faster transpilation6x faster minification There was one hurdle left: webpack. Webp

Vercel acquires Splitbee to expand first-party analytics

The future of web analytics is real-time and privacy-first. Today, we're excited to announce our acquisition of —bringing more analytics capabilities to all Vercel customers. Splitbee Along with the acquisition of Splitbee, we're adding top pages, top referring sites, and demographics to —available now. With Analytics, you can go beyond performance tracking and experience the same journey as your users with powerful insights tied to real metrics.Vercel Analytics Read more

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