As a vision statement to me it resonates, now curious to give it a try and see if it fulfills on that vision.
32,068 karma · joined September 20, 2008
You can find more thoughts from me: https://www.craigkerstiens.com
As a vision statement to me it resonates, now curious to give it a try and see if it fulfills on that vision.
Been up and down on cadence over the years, but a few posts that have shown up here.
- Give me back my monolith - https://www.craigkerstiens.com/2019/03/13/give-me-back-my-mo...
- Why Postgres - https://www.craigkerstiens.com/2012/04/30/why-postgres/
- Unfinished business with Postgres - https://www.craigkerstiens.com/2022/05/18/unfinished-busines...
- A guide to PR for startups - https://www.craigkerstiens.com/2015/07/21/a-guide-to-pr-for-...
Their managed Postgres got an unfair advantage early on by being the default. With a new rails app you were just given a Heroku Postgres database. Heroku's Postgres offering was over 5 years ahead of RDS Postgres and a large part of the reason Amazon added support for Postgres for years they fought it, but eventually had to give into the constant customer request. Unfortunately that innovation of Postgres has stalled out a bit over time due to Salesforce starvation.
I do admit for what people think of as PaaS the Postgres revenue is significant, the part people would probably be surprised about is how much revenue the add-ons marketplace constitutes.
Interestingly New Relic got the same privileged experience in the early days and it resulted in the same type of revenue and mass adoption for New Relic.
Personal favorites on the list include:
- load_balance_hosts, which is an improvement to libpq so you can load balance across multiple Postgres instances.
- Logical replication on standbys
- pg_stat_io which is a new view that shows IO details.
1. It's solid as a really reach data platform (more than just a relational database). It's extension framework is quite unique compared to others. It's JSONB support was the first among other relational databases and is feature rich and performant. Multiple index types. Transactional DDL. The list goes on.
2. No central owner. A lot of open source is source code is open, but it's maintained by a central company.
3. I mentioned extensions, but really that is understated. It can do really advanced geospatial, full text search, time series, the list goes on.
Having explained this a ton of times first 10 years ago - https://www.craigkerstiens.com/2012/04/30/why-postgres/ and then again 5 years later with and updated version, most recently tried to capture more of this in an updated form on the Crunchy Data blog - https://www.crunchydata.com/why-postgres
But also your point of students and developers in low income countries completely understand that side. It's a shameless plug but we built our Postgres playground with tutorials on a number of topics which are completely free aiming to help target some of that audience - https://www.crunchydata.com/developers/tutorials
We've had a number of customers that use us for the database and fly for the app. We had a user benchmark a number of heroku alternatives with various database providers and we were actually better response time than the unmanaged instances on fly themselves in addition to all other providers they tested - https://webstack.dancroak.com/
I won't speak for Fly, but we're big fans of them and think we pair quite well together.
Dataclips equivalent is coming, we're hoping to release sometime in March.
You could easily block all incoming connections to the database. For a free database of 10k rows there were no SLAs, and you would still technically be hosting the database.
Even taking a dump and emailing it to me feels like a safer option here.
There were better answers here for sure. If the honest answer is we just didn't feel the effort was worth it for this class of users at least own that.
That said there are some bumpy things about how Salesforce seems to have handled this. In several cases managers and skip levels got no advance notice and were left scrambling in slack to see which team members no longer had active accounts. At the mass of a level it can be hard to be coordinated, but still a few hrs after there is a lot of unclarity internally to teams and what that means.
Within Heroku there are folks currently on call for production systems that were impacted. I feel for those impacted as well as those still there scrambling to ensure things continue to operate for customers. Seems that within the broader Salesforce org some pieces of it were done in a better fashion than some others we've recently seen, but also some pretty missteps still.
1. https://webstack.dancroak.com/
2. https://github.com/croaky/webstack
*Disclaimer I work at one of those fully managed database providers.
The biggest advice I can give is 1. keep trying and grabbing capacity continuously, then run with more than what you need. 2. Explore migrating to another Azure region that runs less constrained. You mention a new region would be complicated, but it is likely much easier than another cloud.
1. https://www.zdnet.com/article/azures-capacity-limitations-ar...
Even now if you emulate that it's one thing, but Heroku has been frozen in time for at least the last 5 years, maybe closer to 7-8 years. There was more to do and more to improve and advance, and it stalled out for reasons. Now just being a clone wouldn't be enough you need to continue advancing the experience.