4 ms·

You keep mentioning six figures contracts as it's something big. Most of fortune 500 companies have their own data center and still read database manuals someho

by aprdm 8y ago

You keep mentioning six figures contracts as it's something big. Most of fortune 500 companies have their own data center and still read database manuals somehow...

scarface74 8y ago
No I’m mentioning our six figure customers because too often small companies are seen as being low margin B2C customers where you control for cost and you don’t have to be reliable, compliant, redundant or scalable from day one. One “customer” can equate to thousands of users. We are a B2B company with a sales team that ensures we charge more than enough to cover our infrastructure. Yes infrastructure cost scale with volume, but with a much lower slope. But it’s kind of the point, we save money by not having a dedicated infrastructure team, and save time and move faster because it’s not a month long process to provision resources and we don’t request more than we need like in large corporations because the turn around time is long. At most I send a message to my manager if it is going to cost more than I feel comfortable with and create resources using either a Python script or CloudFormation. How long do you think it would take for me to spin up a different combination of processing servers and database resources to see which one best meets our cost/performance tradeoff on prem?
- aprdm 8y ago
  Depends on how you architecture it, theoretically spinning on prems or in baremetal or vsphere should be an ansible script with its roles and some docker file regardless. Just for reference we ""devops"" around 2 thousand VMs and 120 baremetal servers and a little of cloud stuff through same scripts and workflows. We don't really leverage locked in cloud things because we need the flexibility of on prems. In my business hardware is essentially a drop in the bucket of our costs. P.s: I totally think there are legit use cases for cloud, is just another tool you can leverage depending on the situation
  - scarface74 8y ago
    Spinning up on prem means you have to already the servers in your colo ready and have to pay for spare capacity. Depending on your tolerance for latency (production vs non-production environments or asynchronous batch processing), you can operate at almost 100% capacity all of the time: Lambda vs VMs (yes you can deploy standard web apps to Lambda using a lambda proxy) Serverless Aurora vs Regular Aurora. Tx instances vs regular instances Autoscaling VMs. Autoscaling DynomoDB Etc.

by aprdm 8y ago

You keep mentioning six figures contracts as it's something big. Most of fortune 500 companies have their own data center and still read database manuals somehow...

scarface74 8y ago

No I’m mentioning our six figure customers because too often small companies are seen as being low margin B2C customers where you control for cost and you don’t have to be reliable, compliant, redundant or scalable from day one. One “customer” can equate to thousands of users. We are a B2B company with a sales team that ensures we charge more than enough to cover our infrastructure. Yes infrastructure cost scale with volume, but with a much lower slope. But it’s kind of the point, we save money by not having a dedicated infrastructure team, and save time and move faster because it’s not a month long process to provision resources and we don’t request more than we need like in large corporations because the turn around time is long. At most I send a message to my manager if it is going to cost more than I feel comfortable with and create resources using either a Python script or CloudFormation. How long do you think it would take for me to spin up a different combination of processing servers and database resources to see which one best meets our cost/performance tradeoff on prem?

aprdm 8y ago
Depends on how you architecture it, theoretically spinning on prems or in baremetal or vsphere should be an ansible script with its roles and some docker file regardless. Just for reference we ""devops"" around 2 thousand VMs and 120 baremetal servers and a little of cloud stuff through same scripts and workflows. We don't really leverage locked in cloud things because we need the flexibility of on prems. In my business hardware is essentially a drop in the bucket of our costs. P.s: I totally think there are legit use cases for cloud, is just another tool you can leverage depending on the situation
- scarface74 8y ago
  Spinning up on prem means you have to already the servers in your colo ready and have to pay for spare capacity. Depending on your tolerance for latency (production vs non-production environments or asynchronous batch processing), you can operate at almost 100% capacity all of the time: Lambda vs VMs (yes you can deploy standard web apps to Lambda using a lambda proxy) Serverless Aurora vs Regular Aurora. Tx instances vs regular instances Autoscaling VMs. Autoscaling DynomoDB Etc.