2,885 karma · joined March 14, 2012
Co-founder, Kami - kamiapp.com
We actually upgraded to PX dynos recently and the performance is great - just expensive!
The biggest issue is finding a solution which can give similar ease of use and functionality as Heroku. Doing a opsworks/chef setup like this isn't appealing - over time we want to have many microservices which can be scaled independently, and you don't want to be doing a lot of setup for each one. It's also complex to setup the kinds of scaling and rollbacks with git deploys like you can get on Heroku.
Right now Deis or Flynn looks best, giving most of the advantages of Heroku, but they are also pretty immature. Deis only just got the ability to send logs to a syslog instance, and can't be upgraded without either building a new cluster and migrating across (lots of work), or doing a in-place upgrade, which could mean up to 10 mins of downtime.
Flynn has no ability to send logs to an syslog server from what I can see, and seems even more immature than Deis, but looks like it might have a better technical foundation.
I've also been evaluating Amazon's Elastic Container Service, but that is unfortunately also very immature - No load balancing integration yet and also no information on logging, rollbacks, etc.
Elastic beanstalk is also interesting in a way, but we already have one app deployed on it using Docker and it's not great - logging is a kludge using a logger running in each container, and you either use your own docker repository (in which case you can't do rollbacks), or give them a zipfile with a Dockerfile and your app, which allows rollbacks but means the docker image gets built by every server in the cluster. It also doesn't seem to have any way of easily running and scaling multiple processes per app like you can with the Procfile on Heroku.
Anybody else in a similar situation? It seems that there are a bunch of interesting projects that will be very competitive with Heroku soon, but nothing that's really matured yet.
I wish Heroku would just introduce a new range of PX (running on their own EC2 instance) Dynos without the crazy pricing - right now the only PX dyno they have is $500 per month when you can get a substantially faster instance on EC2 for ~170 per month.
Whenever Apple acquires anything that runs on a competing company's platform, that version is immediately killed (see any of their mobile app acquisitions).
Thanks for making things that much harder for every other database startup.
In fact, the bigger issue in the western world, and eventually the whole would will be dealing with it, is what happens when this slowdown in births happens. Just as when you got a huge economic boom from having many young people, you get a economic drag when all those people age and have less young people to support them.
So it's not so much '60 seconds of waiting for the editor in a day', as '2s delay opening that file so my brain switched to thinking about something else, slowing me down for 10+ mins'
So, yes it's possible that this guy is doing something clever or has some advantage that means he will continue to beat the market. It's also possible it's just that he got lucky, and the other 9,999 people who pursued strategies and didn't get lucky are forgotten about.
Yeah, we went with GWDG at the time primarily because it was one of the few good options for a NZ-based company, but it was always a bit strange and I always thought given the lack of maintenance it was likely to get killed. Switched to Stripe and much happier, although I do miss the awesome microtransaction pricing they had...
It would be trivial to tell me what the name of the nil variable was - in this case it's obvious, but it's often not.