I've been saying this for a while. If you are spending less than $25k/mo on Heroku or equivalent, you're not ready to move off it yet. A lot of times when I talk to people with a high Heroku bill looking to move to bare metal, I end up being able to optimize it by 1/3rd or more just by picking dyno types, scaling appropriately, and consolidating workers. You can't really do that when you're hiring headcount.
You can't really do that when you're hiring headcount. I'm curious, why not? Can't you do it on a regular basis, like refactoring?
The Best DevOps Is NoOps
61–66 of 66 posts
Re: The Best DevOps Is NoOps
#62I've been saying this for a while. If you are spending less than $25k/mo on Heroku or equivalent, you're not ready to move off it yet. A lot of times when I talk to people with a high Heroku bill looking to move to bare metal, I end up being able to optimize it by 1/3rd or more just by picking dyno types, scaling appropriately, and consolidating workers. You can't really do that when you're hiring headcount.
How can you compare the monthly price versus VM types/capabilities? What does my bill say about the performance of my app in an e.g. Amazon environment?
B) Nothing in particular
It's not about the application or any technical concerns. It's purely a business decision - above $25k a month you have room to hire people and still save money, below that you really strictly do not.
Re: The Best DevOps Is NoOps
#63So basically the exact opposite of DevOps?
Re: The Best DevOps Is NoOps
#64Maybe I'm old school, but I really hope developers give a serious thought before jumping into this vendor lock-in trap. This is specially concerning if not scary, when you start to "outsource" the backend business rules to something like Firebase or other BaaS systems. Using these as PoC or for an MVP, I'm 100% behind it, but using it on production ready products, it's a disaster waiting to happen, as it basically pu…
I learned this lesson very early on in my dev experience. My app's database was Parse. Parse no longer exists as a service. Before that it was based on StackMob, from which I moved to Parse because StackMob was shutting down. Parse gave a hell of a lot more notice, but I was done with this project at that point. Now a feature of the app just doesn't work. I won't be rewriting it for another backend. Guess who doesn't…
Re: The Best DevOps Is NoOps
#65Earlier quoted context omitted.
I learned this lesson very early on in my dev experience. My app's database was Parse. Parse no longer exists as a service. Before that it was based on StackMob, from which I moved to Parse because StackMob was shutting down. Parse gave a hell of a lot more notice, but I was done with this project at that point. Now a feature of the app just doesn't work. I won't be rewriting it for another backend. Guess who doesn't…
I've seen a tutorial for "make your own self hosted firebase with feathersjs", have you considered just finding a self hosted alternative to parse and altering your application or writing a wrapper?
Re: The Best DevOps Is NoOps
#66Earlier quoted context omitted.
I learned this lesson very early on in my dev experience. My app's database was Parse. Parse no longer exists as a service. Before that it was based on StackMob, from which I moved to Parse because StackMob was shutting down. Parse gave a hell of a lot more notice, but I was done with this project at that point. Now a feature of the app just doesn't work. I won't be rewriting it for another backend. Guess who doesn't…
I've seen a tutorial for "make your own self hosted firebase with feathersjs", have you considered just finding a self hosted alternative to parse and altering your application or writing a wrapper?