サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
GPT-4o
planetscale.com
Engineering team velocity is one of our top priorities at PlanetScale, both for our own teams and for all developers using the tools we build. One of our early goals when building PlanetScale was to make the absolute best schema change process for engineering teams. We've been iterating on this for the past 3 years and are increasingly happy with how easy it is to change our application's schema.
Universally Unique Identifiers, also known as UUIDs, are designed to allow developers to generate unique IDs in a way that guarantees uniqueness without knowledge of other systems. These are especially useful in a distributed architecture, where you have a number of systems and databases responsible for creating records. You might think that using UUIDs as a primary key in a database is a great id
PlanetScale is an infrastructure company. Our service is mission critical, and we value reliability above all else. Reliability isn’t just an uptime percentage on your status page. It means your business is self-sustaining. Every unprofitable company has a date in the future where it could disappear. With an ever changing world and economy, this is a situation fraught with risk. We’ve chosen to bu
Today, PlanetScale announced support for foreign key constraints. This has been in the making for quite a while — around a year in fact. So, what was the problem? Why did it take so long? It’s something that any and every database supports, right? Yes and no. To support foreign key constraints is one thing. To do so while still delivering Online DDL, gated deployments, online imports, and eventual
Any good DBA will tell you to "select only what you need." It's one of the most common aphorisms, and for good reason! We don't ever want to select data that we're just going to throw away. One way this advice manifests itself is to not use SELECT * if you don't need all the columns. By limiting the columns returned, you're selecting only what you need. Pagination is another way to "select only wh
Connection pooling is a commonly used technique in modern applications to manage database connections efficiently. It involves creating a cache of database connections that the application can use as needed. Instead of creating a new connection for each request to the database, the application retrieves a connection from the pool. After the application finishes using the connection, it is returned
Welcome to the MySQL for Developers course! This first video will give you an overview of what we’re going to cover, what you’ll see on the screen, and an introduction to your instructor. 3:25 Next: Schema → A comprehensive course on MySQL for developersWelcome! MySQL for Developers is PlanetScale’s free MySQL course that teaches you schema basics, indexing, querying, and beyond. This intermediate
When we were first building PlanetScale’s API, we needed to figure out what type of identifier we’d be using. We knew that we wanted to avoid using integer IDs so that we wouldn’t reveal the count of records in all our tables. The common solution to this problem is using a UUID (Universally Unique Identifier) instead. UUIDs are great because it’s nearly impossible to generate a duplicate and they
Most of what I will be discussing is not publicly documented and is entirely experimental. The background# As a part of some of our infrastructure initiatives, we demanded new APIs and connectivity features for our database. To support features that weren’t available over the MySQL protocol, we decided to start bolting on a publicly accessible HTTP API. This API is not documented for public consum
Up to 1,000× faster queries with just a few clicksPlanetScale Boost is now in a public beta. Try our groundbreaking caching technology today.
And yes, I know what you’re thinking. “This query is bananas, man. I would never run this in production!”. I know! I agree. The query is not particularly hard to understand, but if you try running it in a standard relational database, you’ll see that as soon as you have a few thousand star rows, the execution time of the query balloons out of control. Although this query uses the relational model
I am excited to reveal our latest product, PlanetScale Boost, which makes your application’s queries up to 1,000× faster in just a few clicks. Building responsive, modern software often requires painful, tedious, error-prone caching logic to hide the latency of an expensive SQL query. Instead, PlanetScale Boost makes the queries you choose faster, with no additional logic and no infrastructure to
MySQL gave us the JSON data type back in mid-2015 with the release of MySQL 5.7.8. Since then, it has been used as a way to escape rigid column definitions and store JSON documents of all shapes and sizes: audit logs, configuration settings, 3rd party payloads, user-defined fields, and more. Although MySQL gives us functions for reading and writing JSON data, you’ll quickly discover something that
Knowing your database can scale provides great peace of mind. We built PlanetScale on top of Vitess so that we could harness its ability to massively scale. One of the core strengths in our ability to scale is horizontal sharding. To demonstrate the power of horizontal sharding, we decided to run some benchmarking. We set up a PlanetScale database and started running some benchmarks with a common
We put together a demo application and GitHub repository that demonstrates how to implement this with Cloudflare Workers, Vercel Edge Functions, and Netlify Edge Functions. Until today, you could not use PlanetScale in these environments because they require external connections to be made over HTTP and not other networking protocols. Connections with other MySQL drivers speak the MySQL binary pro
We’d like to introduce FastPage, a new gem for ActiveRecord that applies the MySQL “deferred join” optimization to your offset/limit queries. Here is a slow pagination query in Rails:
One of the earliest realizations we made at PlanetScale is that the world of databases had been practically untouched by DevOps practices. The benefits of DevOps are numerous, including faster product delivery and continuous integration, so why wouldn’t we want this for our database? When you see a description of DevOps, it is usually accompanied by the cycle shown in the above graphic. However, i
It is a common database pattern to increment an INT column when an event happens, such as a download or page view. You can go far with this pattern until bursts of these types of events happen in parallel and you experience contention on a single row. When multiple transactions are trying to update the counter, you are essentially forcing these transactions to run serially, which is bad for concur
There are many reasons you may need to move and/or transform your application data: to improve database performance, consolidate data, provide access to other teams in your organization to safely query data, and other reasons specific to your use case. This may seem straightforward to set up yourself, but this can be tedious and difficult to get right without impacting your production database. Wi
If you deploy your applications in regions around the globe and need to keep database read latency low, you will want to physically have a database nearby. With PlanetScale Portals, you can now create read-only regions to support your globally distributed applications and better serve your users worldwide. Put your data where your users and applications arePortals allow you to read data from regio
At PlanetScale, we’re committed to building the best database. As a company made up of some of the foremost experts in databases, we have a clear vision for how to do that. “The Future Database” is the set of principles we believe will chart the course for how databases are built in the future. These are the fundamental frameworks that guide our product vision and roadmap. The most exciting advanc
Go 1.18 is here, and with it, the first release of the long-awaited implementation of Generics is finally ready for production usage. Generics are a frequently requested feature that has been highly contentious throughout the Go community. On the one side, vocal detractors worry about the added complexity. They fear the inescapable evolution of Go towards either a verbose and Enterprisey Java-lite
Bad migrations happen every day and data loss can be devastating. PlanetScale’s new schema revert feature gives you the power to revert changes after a schema migration with no downtime and zero data loss. What is it?Have you ever made a schema change, like changing a column’s data type or dropping a table, that broke your production application causing unplanned downtime, or even worse, a full-sc
How to manage your relational data without formal foreign key constraints in your schema. OverviewA foreign key is a logical association of rows between two tables, in a parent-child relationship. A row in a "parent" table may be referenced by one or more rows in a "child" table. A foreign key typically suggests how you should JOIN tables in most queries. A table can also refer to itself, as a spe
Our plans scale with you. All plans include: Daily backups Automatic failover Enterprise-grade security
Several of us at PlanetScale used to work at GitHub where we had a culture of building internal tools for our specific needs. One of the more important of these was an app called Team. For over a decade, this simple tool has helped the highly distributed GitHub workforce stay connected. Anyone in the company could post an update to Team to announce something they’ve shipped, to share a new company
It has been an incredible six months since we released our product in beta. From the outset, we focused on creating a platform that would delight developers, built on top of the only open source database proven at hyper scale, Vitess. For years, our technology has allowed companies like Square, GitHub, and YouTube to scale their database and, in turn, their businesses. Our mission is to bring this
PlanetScale documentationLearn how to use PlanetScale to power your application. New to PlanetScale?Follow this step-by-step guide to quickly get up and running with PlanetScale. You’ll learn the following: Account setupCreating your first databaseBranching and deploymentsConnecting to your databaseGet started with PlanetScale
Every one of us at PlanetScale is deeply unsatisfied by the current state of “modern” databases. We’ve worked at companies like YouTube, Amazon, Facebook, DigitalOcean, and GitHub, always focused on solving the same problem — database scaling. We’ve seen the same sad pattern repeat year after year. Companies pick a stack on day 1 that optimizes for developer velocity to get that MVP out the door.
次のページ
このページを最初にブックマークしてみませんか?
『The ultimate MySQL database platform』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く