--- title: Why Character.ai chose Spanner and AlloyDB for PostgreSQL description: Character.ai chose AlloyDB for PostgreSQL and Spanner to meet their growing needs for scalability and performance. They were able to migrate to AlloyDB... canonical: https://daily.dev/posts/why-character-ai-chose-spanner-and-alloydb-for-postgresql-secccb5co twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why Character.ai chose Spanner and AlloyDB for PostgreSQL | daily.dev og:description: Character.ai chose AlloyDB for PostgreSQL and Spanner to meet their growing needs for scalability and performance. They were able to migrate to AlloyDB... og:url: https://daily.dev/posts/why-character-ai-chose-spanner-and-alloydb-for-postgresql-secccb5co og:image: https://api.daily.dev/og/posts/sECCCB5co.png og:image:alt: Why Character.ai chose Spanner and AlloyDB for PostgreSQL og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why Character.ai chose Spanner and AlloyDB for PostgreSQL **[Google Cloud](https://daily.dev/sources/gcp)** · 4 min read · 0 upvotes · 0 comments ## Summary Character.ai chose AlloyDB for PostgreSQL and Spanner to meet their growing needs for scalability and performance. They were able to migrate to AlloyDB smoothly and achieved a 150% increase in queries processed per second. They also scaled their infrastructure by refactoring parts of their system into standalone microservices powered by AlloyDB and Spanner. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#backend](https://daily.dev/tags/backend), [#gcp](https://daily.dev/tags/gcp), [#alloydb](https://daily.dev/tags/alloydb), [#spanner](https://daily.dev/tags/spanner) [View this post on daily.dev](https://daily.dev/posts/why-character-ai-chose-spanner-and-alloydb-for-postgresql-secccb5co) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why Character.ai chose Spanner and AlloyDB for PostgreSQL","url":"https://daily.dev/posts/why-character-ai-chose-spanner-and-alloydb-for-postgresql-secccb5co","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-character-ai-chose-spanner-and-alloydb-for-postgresql-secccb5co"},"datePublished":"2024-02-12T17:08:48.679Z","dateModified":"2024-05-09T09:28:18.744Z","description":"Character.ai chose AlloyDB for PostgreSQL and Spanner to meet their growing needs for scalability and performance. They were able to migrate to AlloyDB...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f8a83a480da3148e1e0a8cbc94594081?_a=AQAEufR","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f8a83a480da3148e1e0a8cbc94594081?_a=AQAEufR","isAccessibleForFree":true,"articleSection":"Google Cloud","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Google Cloud","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/gcp","url":"https://daily.dev/sources/gcp"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/why-character-ai-chose-spanner-and-alloydb-for-postgresql-secccb5co","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"backend,gcp,alloydb,spanner","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Google Cloud","item":"https://daily.dev/sources/gcp"},{"@type":"ListItem","position":3,"name":"Why Character.ai chose Spanner and AlloyDB for PostgreSQL"}]} ```