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

推荐订阅源

S
Secure Thoughts
Engineering at Meta
Engineering at Meta
Jina AI
Jina AI
Microsoft Security Blog
Microsoft Security Blog
博客园 - 司徒正美
V
V2EX
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
博客园_首页
TaoSecurity Blog
TaoSecurity Blog
PCI Perspectives
PCI Perspectives
T
Tor Project blog
月光博客
月光博客
P
Privacy International News Feed
GbyAI
GbyAI
T
Troy Hunt's Blog
P
Palo Alto Networks Blog
Schneier on Security
Schneier on Security
The Last Watchdog
The Last Watchdog
Forbes - Security
Forbes - Security
S
Security Affairs
Last Week in AI
Last Week in AI
博客园 - 三生石上(FineUI控件)
Google DeepMind News
Google DeepMind News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
C
Cyber Attacks, Cyber Crime and Cyber Security
Y
Y Combinator Blog
Scott Helme
Scott Helme
D
Darknet – Hacking Tools, Hacker News & Cyber Security
A
Arctic Wolf
C
CERT Recently Published Vulnerability Notes
L
LINUX DO - 热门话题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Cyberwarzone
Cyberwarzone
有赞技术团队
有赞技术团队
酷 壳 – CoolShell
酷 壳 – CoolShell
Apple Machine Learning Research
Apple Machine Learning Research
Hacker News - Newest:
Hacker News - Newest: "LLM"
Stack Overflow Blog
Stack Overflow Blog
V
Visual Studio Blog
V2EX - 技术
V2EX - 技术
Google Online Security Blog
Google Online Security Blog
U
Unit 42
Google DeepMind News
Google DeepMind News
W
WeLiveSecurity
Spread Privacy
Spread Privacy
B
Blog
博客园 - 聂微东
C
Cisco Blogs
N
News and Events Feed by Topic

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 Deprecating the Scaler plan — 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 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 PlanetScale vs. Amazon Aurora — PlanetScale PlanetScale vs. Amazon RDS — PlanetScale PlanetScale is bringing vector search and storage to MySQL — PlanetScale
Connect any MySQL client to PlanetScale using Connection Strings — PlanetScale
Taylor Barnett · 2021-08-17 · via Blog — PlanetScale

Taylor Barnett |

Today, we are excited to share that connection strings are available to all PlanetScale users.

As a company that obsesses over making databases more accessible to developers, you might have struggled with why PlanetScale didn’t have a way to connect to your database with connection strings. And we heard you! You can now use the tools you're familiar with to connect to PlanetScale databases, whether that’s with Rails, Python, Prisma, Laravel, or any other MySQL client. Connection strings also enable you to connect to other serverless computing platforms like AWS Lambda or Vercel.

Within PlanetScale, you can generate a new password and automatically get client code for many popular frameworks and languages for you to connect your PlanetScale database.

Strong passwords, never stored in plain text

PlanetScale connection strings are built with security as a priority, so you can spend less time worrying if your database connections are secure. PlanetScale Passwords are created for use with a single database branch. This strong security model allows you to generate passwords tied to a branch, which prevents accessing the data or schema on the given branch from another branch. PlanetScale also only stores hashes and metadata about your database passwords. We do not store any passwords in plain text to add an extra layer of security to your database.

GitHub Secret Scanning out of the box

Leaked secrets happen. We’ve all been there. If one of your PlanetScale Passwords or service tokens are committed in plain text to a public GitHub repository or private repositories owned by organizations where GitHub Advanced Security is enabled, through the GitHub Secret Scanning program we will automatically take corrective action to delete the access tokens and shut down all access from them.

Built for serverless scale

Connection Strings now enable you to connect your serverless functions with PlanetScale databases on serverless platforms such as AWS Lambda and Vercel Serverless Functions. No need to worry about managing your connection count. PlanetScale can handle tens of thousands of simultaneous database connections. Scaling with you as your serverless application grows.

Native MySQL authentication support

PlanetScale supports both MySQL native authentication, which is widely used to provide a secure connection to MySQL servers, and MySQL Caching SHA-2 authentication, which is the most secure authentication mechanism to connect to MySQL. Based on your application needs and platform support, you can switch between the authentication modes with the same password.

You can read more about connecting securely to PlanetScale in our docs.

Try it out

If you haven’t already done so, create a new database in PlanetScale and try connecting with a connection string by generating a new password today. Give it a try and let us know what you think.