New Pricing with replication slot, seems expensive?
So saw the new pricing page today and it seems very expensive to use logical replication. Since the db does not become inactive, you have to pay for the entire compute even when there really isn’t any activity. Is there any ways to mitigate this in a development or testing environment?
For the launch plane that’s a minimum of about $26 (744 hours in month * .25CU * .14)
and about $48 for the scale plan ($744 hours in month * .25 CU * .26).
For production, seems fine, but rather expensive for small workloads or a dev/test instance.
3 Replies
fair-rose•4w ago
As long as there's an active subscriber, you won't be able to have a dev/test env scale to zero, and will need to pay for the constant compute. You could disable the subscriptions by default, and enable them only when needed, which would allow your compute to scale to zero.
Neon
Logical replication commands - Neon Docs
This topic provides commands for managing publications, subscriptions, and replication slots. For step by step setup instructions, refer to our logical replication guides. Publications. This section o...
conscious-sapphire•4w ago
Do you really need replication for dev/test?
national-goldOP•3w ago
If you have a service that reacts to events in your db, then yes. Can certainly get away with it if required, but would be nice to have that when developing so you don’t go to a higher environment and realize your schema broke something or changes to the service that reacts to the db didn’t break