|
|
|
|
|
by nickpsecurity
3810 days ago
|
|
You don't get an engineer in my model: you usually share one with others. Someone who throws together this stuff all the time usually has premade images, scripts, checklists, etc that make it very efficient. You become one of their many customers. This might be a person or a firm. It's just one that focuses on great cost-benefit as differentiator. So, one $30-50k engineer gets split 5-10 ways on infrastructure. Most maintenance is automated with setup and occasionally fixing something using up most time. You usually negotiate 1 day to a week of dedicated time out of the month w/ split being flexible. Heroku and Redis might still come out a better deal. It's just not going to be nearly as different as people think because one doesn't have to load-up on IT people to deploy or maintain common configurations. All kinds of consultants and smaller fish that will do it way cheaper [than you mentioned] with cost spread across multiple, small businesses. |
|
- The time and money it takes to find said $30-50k engineer
- The risk (and therefore potential cost) if the engineer doesn't do the job correctly
- The unknown cost of "occasionally fixing" could be $50 or $50,000. Given how nebolus the DevOps position is, you also can't be sure the stuff this individual is doing is considered best practice.
- There is overhead time spent on managing such a resource (teleconferencing, IM's, etc)
- There is potential that the resource is unavailable and therefore a potential downtime that could cause your business loss
There's a reason Heroku exists and has been successful, and these are just a few of them.