I really think any help the community could offer - and also receive - would be welcome news for those still on Fauna service right now. Especially open source. People could move quickly – with multiple options – to help themselves, which after all is the only thing Fauna the co is able to offer anyway. Like the other commenter said, if you do release it open source please post on Hacker News and maybe Reddit and we'll all try to help boost it.
This is a very tough announcement for any customers relying on the Fauna service. The announcement itself hides the all key details, clicking into the FAQ reveals the date is not several months away but in fact 2 months 11 days away, and there is no FaunaDB open source release to start saving your own ass today.
> we have made the hard decision to sunset the Fauna service over the next several months. clicks into the FAQ
vs
> Fauna service will be ending on May 30, 2025.
Nick from DigitalOcean here; yes! It's in the bottom of the blog post
>>> Our engineering team is working hard to bring you even more functionality for your databases in 2019. We plan to have additional engines such as Redis and MySQL, private networking with enhanced VPC, metrics, and alerting through Insights.
The headline figure includes his benefits in order to seem worse in some way. Wages were around $230K.
Reality is 114 hours of work every week makes for a dismal sort of life for most people. Perhaps this is a case of Chinese work ethic plus pension spiking?
Something I totally forgot to mention, which was remiss of me, is that the platform I'm talking about is also where developers who have their own product - SaaS or otherwise - can also distribute free integrations to our products. Loads of them do that and successfully bolster their own value within any joint customers we share a bit more too.
I guess it's relative. Our market isn't the number of users of a consumer market like the Apple App Store or Google Play. But then again there's millions of apps in each and getting yours noticed is extremely hard.
Part of what we're trying to do for our devs is grow it steadily year by year, and small developers are able to grow along with us (often faster as they first gain new customers). You may not know this but there's more than 60,000 organizations with anywhere from 10 to thousands of users in our customer base. There's a whole lot more startups with 1 to 9 folks too. They've collectively bought a few hundred thousand licenses of our ecosystem developers products so far since we launched.
I'd also counter that we're fairly open about what you can build. We work hard to have supported, public, documented APIs and patterns, but within that you can pretty much build anything you want. Candidly you probably don't want to build something directly in competition with Atlassian but there's lot of value to add around what we do. Last thing we released publicly on this was a while ago - I'm working on another release because our devs are much further along at this point but here you go https://techcrunch.com/2015/12/15/atlassians-marketplace-for...
Thanks for the reply mentioning us! There’s quite a few independent developers selling their add-ons in our Atlassian Marketplace with yearly bookings of anywhere from a few thousand $$ to over $1,000,000 in some cases. Some have even been acquired by larger partners who double down on investment and now what started as a solo thing is effectively a big startup. We think it really makes sense and is a great option for developers to consider.
Here’s a couple of examples we wrote up: Atlassian Marketplace developer Wittified, a successful solo dev business, acquired recently by AppFire https://www.atlassian.com/customers/wittified. Atlassian customer Twilio, who use several add-ons from such developers and they talk about how it really makes their Atlassian products more valuable https://www.atlassian.com/customers/twilio-case-study.
There’s Bob Swift Software, a long-standing solo independent developer who started with us years ago and who has tens of thousands of customers, also acquired by AppFire. Theres’s our Marketplace developer eazyBI, a reporting tool started as a side-project by one person and now a profitable company with 7 employees. There’s even agile planning features now part of JIRA Software itself, which started as an add-on known as Greenhopper from an independent developer that we ourselves acquired some years ago. And these are just some of the smaller, solo and indie devs. The larger business that emerged on our platform are something to behold (one recently just took a $31M VC round!).
As the person at Atlassian who helped manage and grow this developer platform, I’m really proud of what the developers around us in our ecosystem have built - both their products and their businesses. The successful growth of sales and customers they’ve made in a few short years is extraordinary to watch and to be a small part of. If anything this post I wrote in 2013 is more true now than ever http://blogs.atlassian.com/2013/04/the-future-is-bright-for-.... If you’re interested in talking with some of these developers in our ecosystem, let me know and I’ll get you introduced.
Yes, I agree with your premise here. Personal anecdote, I lived in San Francisco in the city 8 years. It was by far more economical for me to have both Zipcar and taxis (later UberX and Lyft) combined per month than to have a vehicle lease + parking costs + insurance/maintenance/gas. By far. In both $ and time.
I'm not certain that other elements of your vision work in non-metro areas.
> Instead, they subscribe for access to a fleet–such as Uber or Tesla's. (Note: people already do this in cities like New York, where car ownership is relatively scarce.)
Parsing this took me a moment - what they already do is subscribe to a fleet, and for years it has been the taxi fleet. That's shifting shape and I guess we'd both predict it will be Uber- and Tesla-like in the future (I don't know what mix of public / private ownership might look like).
Your strawman implies that his team would save time in Slack versus HipChat, but you ignored the justification he already gave about the integrations that are more useful to them edit and that the whole company was happy to go to HipChat. It's possible those integrations help them save the time that makes the difference, but having every user there would surely help.