3 ms·

Pardon my ignorance as I'm not aware of these recent developments, but what is a valid use case for this? Why would I put my database into an ephemeral serverle

• gmac 3y ago
  Well, the data is absolutely not ephemeral: it's safely tucked away in S3. But to crib from https://neon.tech https://neon.tech, you might choose Neon because it's scalable, cost-effective, and easy to deploy and manage. Or you might choose it for its copy-on-write branching and point-in-time recovery, all open-source, and all on top of the solid, performant, feature-rich foundation that is Postgres. :)
• raoufchebri 3y ago
  Neon separates storage and compute. The compute part is serverless and can scale up and down on demand. The storage has multiple layers: Safekeepers for durability and Pageservers to reconstruct pages from WAL. The data is also offloaded to S3. Here is a diagram that describes the architecture: https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dreamhosters.com%2Fwp-content%2Fuploads%2F2023%2F07%2Fimage-8.png&w=3840&q=85 https://neon.tech/_next/image?url=https%3A%2F%2Fneon-hwp.dre...
• tristan957 3y ago
  To follow up on Raouf's comment, here is a blog post[0] that describes Neon's architecture in more detail. [0]: https://neon.tech/blog/architecture-decisions-in-neon https://neon.tech/blog/architecture-decisions-in-neon