惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

H
Heimdal Security Blog
小众软件
小众软件
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
罗磊的独立博客
Google DeepMind News
Google DeepMind News
大猫的无限游戏
大猫的无限游戏
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Hugging Face - Blog
Hugging Face - Blog
阮一峰的网络日志
阮一峰的网络日志
A
About on SuperTechFans
宝玉的分享
宝玉的分享
博客园 - 聂微东
月光博客
月光博客
Cyberwarzone
Cyberwarzone
Microsoft Security Blog
Microsoft Security Blog
V
Visual Studio Blog
Project Zero
Project Zero
T
Tor Project blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
L
LINUX DO - 最新话题
博客园 - 叶小钗
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Attack and Defense Labs
Attack and Defense Labs
Spread Privacy
Spread Privacy
Forbes - Security
Forbes - Security
Simon Willison's Weblog
Simon Willison's Weblog
N
Netflix TechBlog - Medium
P
Proofpoint News Feed
Engineering at Meta
Engineering at Meta
Hacker News: Ask HN
Hacker News: Ask HN
I
InfoQ
M
MIT News - Artificial intelligence
AI
AI
博客园 - 三生石上(FineUI控件)
W
WeLiveSecurity
C
Check Point Blog
The Hacker News
The Hacker News
C
Cyber Attacks, Cyber Crime and Cyber Security
Application and Cybersecurity Blog
Application and Cybersecurity Blog
T
Tenable Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
The Cloudflare Blog
Blog — PlanetScale
Blog — PlanetScale
美团技术团队
D
Darknet – Hacking Tools, Hacker News & Cyber Security
GbyAI
GbyAI
Hacker News - Newest:
Hacker News - Newest: "LLM"
腾讯CDC
K
Kaspersky official blog

Blog — PlanetScale

Keeping a Postgres queue healthy — PlanetScale Patterns for Postgres Traffic Control — PlanetScale Graceful degradation in Postgres — PlanetScale High memory usage in Postgres is good, actually — PlanetScale Stripe Projects partnership: Provision PlanetScale Postgres and MySQL databases from the Stripe CLI — PlanetScale Enhanced tagging in Postgres Query Insights — PlanetScale Behind the scenes: How Database Traffic Control works — PlanetScale Introducing Database Traffic Control — PlanetScale Scaling Postgres connections with PgBouncer — PlanetScale Drizzle joins PlanetScale — PlanetScale Video Conferencing with Postgres — PlanetScale Faster PlanetScale Postgres connections with Cloudflare Hyperdrive — PlanetScale Introducing the PlanetScale MCP server — PlanetScale Database Transactions — PlanetScale Automating our changelog with Cursor commands — PlanetScale Postgres 18 is now available — PlanetScale Using MotherDuck with PlanetScale — PlanetScale $50 PlanetScale Metal is GA for Postgres — PlanetScale AI-Powered Postgres index suggestions — PlanetScale $5 PlanetScale is live — PlanetScale Announcing Vitess 23 — PlanetScale $50 PlanetScale Metal — PlanetScale Report on our investigation of the 2025-10-20 incident in AWS us-east-1 — PlanetScale $5 PlanetScale — PlanetScale Benchmarking Postgres 17 vs 18 — PlanetScale Larger than RAM Vector Indexes for Relational Databases — PlanetScale Partnering with Cloudflare to bring you the fastest globally distributed applications — PlanetScale Processes and Threads — PlanetScale PlanetScale for Postgres is now GA — PlanetScale Postgres High Availability with CDC — PlanetScale Announcing Neki — PlanetScale Caching — PlanetScale The principles of extreme fault tolerance — PlanetScale Announcing PlanetScale for Postgres — PlanetScale Benchmarking Postgres — PlanetScale Announcing Vitess 22 — PlanetScale The Real Failure Rate of EBS — PlanetScale IO devices and latency — PlanetScale Announcing PlanetScale Metal — PlanetScale PlanetScale Metal: There’s no replacement for displacement — PlanetScale Upgrading Query Insights to Metal — PlanetScale Automating cherry-picks between OSS and private forks — PlanetScale Database Sharding — PlanetScale Anatomy of a Throttler, part 3 — PlanetScale Introducing sharding on PlanetScale with workflows — PlanetScale Announcing Vitess 21 — PlanetScale Announcing the PlanetScale vectors public beta — PlanetScale Anatomy of a Throttler, part 2 — PlanetScale Instant deploy requests — PlanetScale Anatomy of a Throttler, part 1 — PlanetScale Increase IOPS and throughput with sharding — PlanetScale Tracking index usage with Insights — PlanetScale Faster backups with sharding — PlanetScale Building data pipelines with Vitess — PlanetScale The State of Online Schema Migrations in MySQL — PlanetScale Optimizing aggregation in the Vitess query planner — PlanetScale Dealing with large tables — PlanetScale Announcing Vitess 20 — PlanetScale Self-managed Vitess vs Managed Vitess with PlanetScale — PlanetScale Achieving data consistency with the consistent lookup Vindex — PlanetScale The MySQL adaptive hash index — PlanetScale Introducing global replica credentials — PlanetScale Profiling memory usage in MySQL — PlanetScale Summer 2023: Fuzzing Vitess at PlanetScale — PlanetScale How PlanetScale makes schema changes — PlanetScale Identifying and profiling problematic MySQL queries — PlanetScale The Problem with Using a UUID Primary Key in MySQL — PlanetScale Announcing Vitess 19 — PlanetScale PlanetScale forever — PlanetScale Introducing schema recommendations — PlanetScale Amazon Aurora Pricing: The many surprising costs of running an Aurora database — PlanetScale Three common MySQL database design mistakes — PlanetScale OAuth applications are now available to everyone — PlanetScale PlanetScale branching vs. Amazon Aurora blue/green deployments — PlanetScale Databases at scale — PlanetScale Considerations for building a database disaster recovery plan — PlanetScale Working with Geospatial Features in MySQL — PlanetScale PlanetScale vs Amazon Aurora replication — PlanetScale Introducing the Vantage and PlanetScale integration — PlanetScale MySQL isolation levels and how they work — PlanetScale Introducing the schemadiff command line tool — PlanetScale $ pscale ping — PlanetScale Announcing foreign key constraints support — PlanetScale The challenges of supporting foreign key constraints — PlanetScale What is HTAP? — PlanetScale Introducing Insights Anomalies — PlanetScale Webhook security: a hands-on guide — PlanetScale MySQL replication: Best practices and considerations — PlanetScale A guide to HTML email with Ruby on Rails and Tailwind CSS — PlanetScale Sharding for cost-effective database management — PlanetScale PlanetScale ranks 188th in Deloitte’s top 500 fastest-growing companies — PlanetScale Announcing the Fivetran integration — PlanetScale Introducing webhooks — PlanetScale What is MySQL replication and when should you use it? — PlanetScale Sync user data between Clerk and a PlanetScale MySQL database — PlanetScale Introducing database reports — PlanetScale Distributed caching systems and MySQL — PlanetScale What is MySQL partitioning? — PlanetScale MySQL High Availability: Connection handling and concurrency — PlanetScale Personalizing your onboarding with Markdoc — PlanetScale
Deprecating the Scaler plan — PlanetScale
Nick Van Wiggeren · 2024-02-05 · via Blog — PlanetScale

Nick Van Wiggeren |

Note

Update: The Scaler plan has now been fully deprecated. All databases that were not migrated have been upgraded to the Scaler Pro plan. Scaler Pro has since been renamed to the Base plan.

Last year, PlanetScale launched the next evolution of our pricing: Scaler Pro. Fast forward to today, our customers have spoken with their data — it’s now our fastest-growing product. Time and time again, we’ve heard that straightforward resource-based pricing just works. It leads to simpler system design and more predictable billing.

Today, we’re giving notice that we are discontinuing our serverless Scaler plan. Scaler will be removed as a product option on February 12th and existing Scaler customers will have 2 months to move to Scaler Pro. This decision is based on thousands of customers’ feedback and a belief that everyone deserves predictable pricing for their database. Everything we said in our Scaler Pro announcement post seven months ago is even more true today.

PlanetScale for serverless

This does not mean we’re not the home of the best database for serverless — it’s the opposite. Our architecture was built from the ground up to scale in all the dimensions important for infinitely scalable edge applications. We can handle millions of connections, distribute data around the globe, and soon, we will be able to automatically route incoming connections to the closest region with our intelligent edge.

Serverless has tenets like "scale to zero" and optimizes for periods of no use. PlanetScale powers websites and applications that need to be on 24/7/365 around the globe, and turning a database off is the last thing that we optimize for. Instead, we focus on horizontal scaling via sharding, change management, and smooth no-downtime upgrades to help databases with real-world usage.

Most importantly, PlanetScale scales. We are the primary database for companies totaling well over $40B in market cap, with individual clusters containing 1000s of nodes and 100s of terabytes of data. We’ve proven that from our smallest PS-10 to our largest enterprise databases, we’re built for the future of software.

Putting the "server" in "serverless"

Looking at the industry, we’ve all collectively learned a lot in the last few years.

We’ve always known that the phrase "serverless" is an oxymoron. Every request and every query from a serverless product is run on a computer somewhere, and the limitless scale and novel pricing methods may provide alternate units and easier orchestration, but we’re still using servers.

The more we’ve seen PlanetScale adopted, the more we are convinced that serverless as a deployment method is extremely useful — it encourages scaling in stateless applications and allows customers to get started faster. It also puts immense strain on legacy databases. The storm of 10,000 connections after being on the front page of Reddit is the opposite of what the creators of PostgreSQL imagined was possible 25 years ago.

That’s why we’ve continued to make sure that we’re the best place to put state for serverless applications — from effortlessly pushing the limits with one million concurrent connections to putting our database connections on the edge with HTTP/3 — we care deeply about giving developers at every stage access to the best database from wherever they deploy their applications.

It’s also why we’re removing serverless pricing and focusing on building the bedrock of the modern database to power the internet. We don’t want to hide the fact that we’re running on servers — we’re proud of it!

Simply put, being the best database for serverless workloads does not require being serverless. Holding the state for massive horizontal applications is a completely different problem, and it’s one we’re laser-focused on solving.

What does this mean for you?

If you’re using a Scaler plan database today, you can seamlessly migrate it over to a Scaler Pro plan by visiting the dashboard and selecting a Scaler Pro cluster size. On Scaler Pro, you’ll get unlimited usage of the cluster size you’ve selected. And your database will be upgraded with two replicas to improve resiliency and scale out your reads.

If you’re new to selecting database cluster sizes, we’ve made it as simple as possible by displaying CPU and memory usage on the PlanetScale dashboard. We recommend sizing up when your workload consistently reaches 70% or above of the available CPU. If you need help selecting a size, our Support team is available to make recommendations.

In the coming weeks, we will email every current Scaler customer with recommendations on which Scaler Pro cluster size will work best for their workload. We’ll also include a snapshot of what their bill would look like under Scaler Pro to make sure that we’re transparent about the impact of these changes.

On April 12th, we will automatically migrate any remaining Scaler plan databases over to Scaler Pro. This will not change the amount of resources or disrupt your database in any way. It will just be a plan change that will impact your bill.

If you’re a happy PlanetScale customer and are interested in discounts, reach out to us to see what options you have. We have flexible options that can help you save on the database you know and use with a discount program that allows you to grow and scale without concerns.

Again, if you have any questions, do not hesitate to reach out to our support team or read our Scaler Pro upgrade FAQ.