141–150 of 366 posts
Earlier quoted context omitted.
What is there to be studied? Once a company is acquired you bounce. There is usually a two year grace period before you start feeling the pain as a customer, which should give you the time to migrate.
Salesforce acquired Heroku 15 years ago.
The seeds of this outcome were planted years ago when sales comp plans changed. When a sales rep can hit their target by simply converting the way an existing customer gets billed, none of them look for new business. Don't need new leads. Don't need to win competitive deals. But finding new customers and losing opportunities are the only things that signal/drive innovation. But from a budgeting perspective, why increase investment in a product that already hits/exceeds their sales targets?
Over time sales targets get met, but the product doesn't advance. By the time all existing customers that can convert have converted, the product is no longer competitive. Like bankruptcy, it comes gradually, then suddenly.
"transitioning to a sustaining engineering model". I don't care what anyone says, it takes real talent to come up with lines like this.
From a business perspective, this means they will not be investing in innovation on the platform anymore. Instead, they will focus their efforts on maintaining the current operations and keeping the lights on.
sustaining == maintanence mode
This literally says nothing - are we supposed to infer that they are putting the product into maintenance mode and will no longer be developing new features for it? This is a masterpiece of corporate nullspeech.
it sounds pretty clear that it's in maintenance mode
The downfall of Heroku should be studied, they had lightning in a bottle and blew it. Salesforce acquired them and just let it die, baffling.
Earlier quoted context omitted.
hey! northflank supports the same buildpacks that you run on Heroku, so it should be fairly straightforward. we have these docs for a more detailed walkthrough: 1/ https://northflank.com/docs/v1/application/migrate-from-hero... 2/ https://northflank.com/blog/how-to-migrate-from-heroku-a-ste...
Looks like that still has downtime for a Postgres migration- you're suggesting going into maintenance mode and just doing a dump/restore. I've seen that take hours once you hit the terabyte scale, depending on hardware. I've had pretty good luck setting up logical replication from Heroku to the new provider and having a 10-15 minute maintenance window to catch up once it's in sync. Might be worth considering. You mig…