Jumpstarter launches “next-gen hosting”, promising sub-second server spin-up
gigaom.com
gigaom.com
I want something in between DigitalOcean (barebones) and Heroku (configures everything but doesn't let you customize anything either) - this seems like a perfect fit.
We don't support Rails and PostgreSQL quite yet, but they are both in our future plans, so we should have support for them soon.
You can also make requests on our wiki for frameworks you would like us to support: https://github.com/jumpstarter-io/help/issues
Where could I find more details/inspiration for your filesystem? It's great to see innovation in that area!
You can take a look at our technical tour page which has some information on it: http://jumpstarter.io/technical
We have also got a brand new wiki with lots of information, and we'll be continuing to add a lot more to it over the next few weeks: https://github.com/jumpstarter-io/help/wiki
What counts as a request? A hit to any asset? A connection/
It's interesting that they focus on WordPress. A custom WordPress install could potentially have several requests that make up a given page. Wordpress isn't really designed with reducing the requests in mind.
Wordpress is getting increasingly better at keeping requests lower. And it's all up to a user how they optimise; they can get it down to just a couple of requests if they wish.
You may want to rethink that.
You also assume nothing is cached, whereas only if those were all uniques would that be likely. Which is generally unlikely.
Our price is based around quality. Both the fact that we grow with you, and the fact that we strive to make every task you need to do, ridiculously easy.
So with 300,000 I get something like 10,000-15,000 pageviews which is pretty much nothing.
We have git automated deployment being released this week. And if your database is 2TBs, you want an Enterprise Solution.
You can currently snapshot your projects, in the same manner we do for failovers.
But we'll definitely keep your opinion in mind, thank you.
"Pricing Tour Support Sign up Login"
No links. View source code shows html though.
This is on ffox latest and safari latest.
You never have to worry about if other people are being resource intensive for one major reason. And if you got Hacker News'd, rather than punishing you and everyone else – we'd instead give you more resources to deal with it :)
It's like you guys don't know anything about normal website traffic volumes, which isn't a good sign for a host.
Thanks for your feedback.
on a sidenote, you have entered pretty much competitive market with tons of 'major players'. Deep down in our hearts we all know, what 'quality hosting mean'. They are all the same. some of them suck much other less. They all have down time. It's only up to you pay more or less for having almost same service from any of them. You are only good for them as long as, you have steady traffic than spikey ;)
Our tech was completely written from the ground up to combat this. As said in the marketing materials; if you have a spike, we handle it fine. We've done intensive testing to make sure that being linked to from Hacker News, or anywhere else that gives you a big influx of traffic, won't make your server go down.
We wrote this because we too were tired of the landscape, and we wanted people like ourselves not to have to suffer with this anymore.
As far as I can see, your architecture is explicitly limited to a single instance of each app at a time, so there is almost no scope for scaling at all in the first place. The only reason it would probably not be an issue in practice is that the request limits are absurdly low. The story is further weakened by no mention anywhere of what happens when the paid for quota is exceeded -- this seems like a key detail that's completely glossed over.
I can see the point of selling a system like this to less technical users based on an ease of use or the conceptual simplicity of an application as a filesystem. Even if the suggested advantages, such as no need for deploying code and easy copy-paste for starting new projects, make me shudder a bit. But selling on scalability just makes no sense, it almost comes across as snake oil.
The largest instance we can put you on is equivalent to 100 Heroku dynamos for instance. And we plan on growing that farther.
I have a blog on a popular host, and when I got hit by Hacker News my server fell over. Doing so caused me to lose a lot of the reads and garner plenty of complaints from here. It can be a total pain, and every time my posts appear on HN, I get scared inside if the project isn't on HN.
As for simplicity; it's not just the filesystem. The panel itself is easy to use, and we're continually adding more relevant features to help people just focus on staying in flow and working on their code.
If we can save devs any time, we've won. And I think we save them a lot of time.