85 karma · joined October 12, 2011
I don't see the value for Starbucks customers either.
Personally I like the Chrome download bar, but I get why it might get in the way of some uses.
In my experience the computer failures are relatively easy to manage. Power will be your primary issue, and to a lesser degree, internet. When we ran a lot of servers on UPSs, the UPSs start to become a major pain. UPSs fail much more often than hard-drives. And when the battery dies it cuts off power to the computer. You're using low-end desktop machines, so you probably don't have dual PSUs in each machine (if you did you could run each PSU to a different UPS). UPSs are also much more likely to fail when the grid power fails. So the power goes out, your UPSs will kick in, then 30 seconds later one or TWO fail. Can your power distribution can handle that? I'm no UPS expert, but this seemed pretty common across a variety of UPS products.
As for internet, multiple links is a good start. Load-balancing outbound traffic is fairly straight-forward. Inbound traffic is much harder. Really you need BGP. A BGP-based set of links isn't cheap, and doing the configuration yourself is hard if you don't have experience with it. The alternatives that aren't IP routing based are usually based on DNS, which is better than nothing. But the effectiveness of it is dependent on how your users servers/clients/browsers implement DNS caching. It will work OK for some users but some will cache the stale link IP for 24 hours -- not cool.
You certainly can work this way, and probably get three nines of uptime. But I can say now that we switched to a decent colo I sleep a lot better. We can focus more on building product, adding value for our customers, than screwing around with the utilities.
FWIW I'm basing this off of my experience in the United States.
But every time I see something this I have to ask myself again why I'm just not using CVS (or SVN, i.e. a simpler tool).
Thanks for replying!
I assume you've tried Pivotal Tracker at some point too? I'd be interested to know what you like/dislike about your new workflow compared to Pivotal.
I like this, or it at least validates some of my thinking. All of my startup ideas are small and modest, something that will help me and maybe some people like me. But I have no idea where the idea will take me...
Last night I added Compass (http://compass-style.org/) to a Rails project I'm working on. It's a CSS pre-processor that takes care of generating browser specific style for you.
"@include border-radius(10px)" and you're done. All of the -webkit, -moz, -ms and -khtml prefixes are automatically generated. (Who knew there was a KDE prefix?) Same with gradients, inline-block, etc.
Recently I've started to do this on a small scale in my own .emacs file. Shortcuts I use every few minutes were hidden but too many multi-step keyboard shortcuts. Especially when I really don't need to duplicate the arrow and page-up/down keys with single-step shortcuts.
It's too bad it sounds like there won't be a Linux version.
Furthermore, sorting large data sets is a huge performance challenge. I think that's the main reason why you don't see it in Gmail. Not because sorting is not desired.
20% more expensive but it seems like the easiest way to fix the problem if you're already on Amazon.
That said, I totally agree that Cloud-based IaaS is not a good fit for every situation.
- Like pie asked, is this a remote proxy?
- What happens if I start a transaction and then the storage engine detects a deadlock and rolls back the transaction?
- What DBs does it work with? I think you say any DB but I have a hard time believing that.
- What is performance like?
- Zero downtime? That sounds like snake oil.
- Can I have an internally hosted solution?
- Shouldn't this be implemented at the storage engine level?
Anyway it sounds very interesting but the devil is in the details.
"Programs must be written for people to read, and only incidentally for machines to execute." - http://mitpress.mit.edu/sicp/front/node3.html