2 ms·
Oh definitely, we have a huge credibility grind to get through. We have the benefit of a successful exit doing hosted DBs at scale, at least, and I'm not sure I
by mrkurt 9y ago
Oh definitely, we have a huge credibility grind to get through. We have the benefit of a successful exit doing hosted DBs at scale, at least, and I'm not sure I ever would have jumped into something like this otherwise. It's big hairy infrastructure, and really expensive to even get started.
For bigger companies, one of my pet theories is that they're going to want to run private edges. Shared infrastructure at every other level is passé, the trend is really to "own" the OS on up. This is part of why our runtime is open source, it's a reasonably good way to get into bigger companies thinking about these problems that don't want to be exposed in the next "bleed" event.
We're running in 15 datacenters at the moment which is (a) way more than most companies can manage and (b) not nearly as many as Fastly/Akamai/CloudFlare/*CDN. So I think we're in a good spot to win devs and startups over. And again, open source. We all love our OSS runtimes. :D
(note: I was a tremendous Etherpad fanboy)
- dgreensp 9y agoInteresting to hear! Thanks for the EtherPad love. (I'm finally working on my next app!) There's something a bit AppJet-like about Fly. I also really think this model could be the future; do you even need an "application server" if you have Fly and a datastore? I'm really looking forward to what you come up with for persistence. At AppJet, we had something called "magic storage" where you could access the "database" via proxy objects, with no explicit database calls. I wouldn't do it quite the same way now, but I can imagine some really neat JS persistence APIs that strip away the usual impedance mismatches between application logic and database, especially if the data is "right there" at the edge.