3 ms·

Would you agree the $300-500 is easily offset by any 1 production incident/outage that would require manual intervention on the airflow servers (and thus develo

by ttymck 6y ago

Would you agree the $300-500 is easily offset by any 1 production incident/outage that would require manual intervention on the airflow servers (and thus developer salary for however many hours to fix, and lost productivity elsewhere)? I understand that the premium is paid _every month_ -- and you may not otherwise have an incident every month -- but the AWS premium can also be considered an _insurance premium_ against those outages. I used to manage an airflow deployment (of which my team was the primary consumer), and it was not enjoyable in the least.

GordonS 6y ago
(I'm not the OP) For an enterprise, this pricing would work for some projects, for the reasons you suggest. Although this assumes nothing ever goes wrong with the managed offering, which is unlikely. But for everyone else, it's a hard sell, especially in these days of infrastructure-as-code - even if you had to rebuild an Airflow server from scratch, it's not going to take very long.
- mchusma 6y ago
  (am OP) We haven't had a major outage in 3 years of using airflow. Some issues, and it consumes some time, but so would managed airflow in all likelihood. Most issues are related to "airflow configuration type things" that presumably this solution would not fix. I am really just surprised it is not a "no brainier price". It's a tough sell. I am sure it's valuable for some people, I just can't really justify using it. I think value to me is like $100/mo (as random airflow user on the internet).
jozzy-james 6y ago
not OP, nor do we use airflow (not sure there is a fit for us) - but $300-500 for something that could cost our modest company an equivalent half day of human time to mitigate, with possible tens of thousands in lost revenue if it occurs at the worst possible time, seem like a win-win peace of mind proposition.
- mchusma 6y ago
  Sure. The right circumstances this can make sense. But at a high level of your SAAS starts at $500/mo, you are selling to mid market and enterprises, not startups, almost universally. I was hoping for a product that would make sense for smaller companies. The list of business critical software we pay less for is long (GitHub, credit card processor, email, sms, managed redis, managed postgres, etc). They can certainly sell this for what they want, I just won't buy at this price.
  - jozzy-james 6y ago
    i guess i really don't understand what separates a startup from enterprise...i know my particular company is nowhere near enterprise level...at least as far as i know of it, but i also know we're not a startup. edit: in this sense...i know the fundamental differences otherwise edit #2: we're also not a SaaS, but a B2C
    - jozzy-james 6y ago
      and i totally get where you're coming from - i'm the point guy on validating any new integrations for what we do. i was just commenting on the cost/benefit of having someone fix a home rolled version vs their managed and if it'd save money

by ttymck 6y ago

GordonS 6y ago

(I'm not the OP) For an enterprise, this pricing would work for some projects, for the reasons you suggest. Although this assumes nothing ever goes wrong with the managed offering, which is unlikely. But for everyone else, it's a hard sell, especially in these days of infrastructure-as-code - even if you had to rebuild an Airflow server from scratch, it's not going to take very long.

mchusma 6y ago
(am OP) We haven't had a major outage in 3 years of using airflow. Some issues, and it consumes some time, but so would managed airflow in all likelihood. Most issues are related to "airflow configuration type things" that presumably this solution would not fix. I am really just surprised it is not a "no brainier price". It's a tough sell. I am sure it's valuable for some people, I just can't really justify using it. I think value to me is like $100/mo (as random airflow user on the internet).

jozzy-james 6y ago

not OP, nor do we use airflow (not sure there is a fit for us) - but $300-500 for something that could cost our modest company an equivalent half day of human time to mitigate, with possible tens of thousands in lost revenue if it occurs at the worst possible time, seem like a win-win peace of mind proposition.

mchusma 6y ago
Sure. The right circumstances this can make sense. But at a high level of your SAAS starts at $500/mo, you are selling to mid market and enterprises, not startups, almost universally. I was hoping for a product that would make sense for smaller companies. The list of business critical software we pay less for is long (GitHub, credit card processor, email, sms, managed redis, managed postgres, etc). They can certainly sell this for what they want, I just won't buy at this price.
- jozzy-james 6y ago
  i guess i really don't understand what separates a startup from enterprise...i know my particular company is nowhere near enterprise level...at least as far as i know of it, but i also know we're not a startup. edit: in this sense...i know the fundamental differences otherwise edit #2: we're also not a SaaS, but a B2C
  - jozzy-james 6y ago
    and i totally get where you're coming from - i'm the point guy on validating any new integrations for what we do. i was just commenting on the cost/benefit of having someone fix a home rolled version vs their managed and if it'd save money