Engineering Insights

Consensus algorithms at scale: Part 7 - Propagating requests

If you’re still catching up, you can find links to each article in the series at the bottom of this article. We have saved the most difficult part for last. This is where we put it all together. Let us start with a restatement of the requirements for propagation of requests during a leadership change: Propagate previously completed requests to satisfy the new leader’s durability requirements. Recap of parts 1-6 We have redefined the problem of consensus with the primary goal of solving durabilit

Vue 2.7 "Naruto" Released

Today we are happy to announce that Vue 2.7 "Naruto" has been released!

Policy Gradient with PyTorch

Identifying slow Rails queries with sqlcommenter

In a large Rails application, it can be tricky to track down where a slow query is coming from in the app. Solutions to this problem have been steadily improving. First, we had the Marginalia gem, which adds comments to all your queries. This allows you to see which controller or job a query came from by reading your logs. As of Rails 7, Marginalia has become a native feature to Rails. No more gem needed. While this is a great improvement, we can still take our Rails query comments one step furt

Liftoff! How to get started with your first ML project 🚀

Next.js 12.2

Next.js 12.2 introduces stable Middleware and On-Demand ISR, experimental Edge SSR and API Routes, and more!

Announcing Vitess 14

We are pleased to announce the general availability of Vitess 14. In this new release, major improvements have been made in several areas of Vitess, including usability and reliability: Online DDL is now GA Gen4 planner is the new default planner VTAdmin and VTOrc are officially in beta with Vitess 14 Usability Command-line syntax deprecation This release marks the beginning of Vitess standardizing its command-line and flags syntax. Some former syntaxes have been deprecated and will break in the

Vercel Edge Functions are now in public beta

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 are now in public beta. Edge API Routes, which use Edge Functions, enable you to create high-performance APIs for use with any frontend framework. These functions use the same standard Web APIs as Routing Middleware, like , , and .Edge FunctionsRequestResponsefetch