![]() Otherwise cost is not a driving factor in the decision.Įven if you decide Postgres is a core capability for your organization, you may wish buy Postgres as a service for an initial ramp-up period, planning to move away later. If the cost of buying Postgres as a service is a significant expenditure, then necessarily it is a core part of business - and clearly we need to develop the requisite in-house capability to support it. ![]() Pricing can actually make this decision easy. Obviously you pay extra to get much more than just the virtualized resources: you get expertise, much of the ops, easier backup and clustering, sometimes even some features.įor pricing I believe we should prefer to buy what is not a core part of our business. The most common objection to buying a database as a service is sheer price: a DB instance from your cloud provider can cost more than twice the cost of the virtual machine instance that it runs on. If your organization already runs Postgres instances, they may well be the best choice: there can be extensive in-house experience and expertise already present. I’ll explain the factors why we decided, and how you might decide to whether or not to follow us. At Treeverse we decided for now to buy Postgres as a service. LakeFS is yet another Postgres application, so it requires a Postgres database. How do you pick the right Postgres for your application? There are a bewildering variety of possible ways to acquire a database running on a Postgres instance, but the biggest choice is “build or buy”: whether to install a Postgres version on your own or to purchase it as a service. ![]() Before you can install them, you will need a Postgres database. Lots of applications require a Postgres database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |