FeathersJS - A truly open source, community driven Meteor alternative

@hermanschutte Hey Herman! Thanks for the interest. It's very flexible. Feathers supports more databases than any other real-time framework (15+). You can have multiple in the same app and can swap them out with minimal code changes if the db isn't right for you. The docs explain a lot more http://docs.feathersjs.com/datab....

@nayafia For sure. Apologies in advance for the long winded answer. A few years ago @daffl and I started working on Feathers with the goal of making it easier and faster to build mobile and web applications. To build a framework that can grow with you as your product grows. One that is flexible enough to rapidly adapt to changing business needs but powerful enough to get a modern app up and running quickly. It initially just started as a total experiment. Over our careers we have tried nearly every other framework out there, across multiple languages, and felt that it was either too hard to get up and running, it took too long, or once you started to scale, was painful to step outside of the framework’s comfortable little sandbox. Rails, Meteor and Sails really paved the way but we always hit limitations with those frameworks. We found that many of the apps we built using MVC frameworks quickly became bloated and when all we really care about is our data; setting up REST routes and dealing with the request-response cycle feels tedious. You can read more about our Philosophy here: http://docs.feathersjs.com/why/p.... In regards to being community driven, it is not owned by anyone or any company, we haven't taken outside funding, and we are completely transparent with everything we do. We welcome contributors with open arms and are really doing everything we can to make it easy for people to contribute. As a result we've really seen the number of contributors grow very quickly. Sorry for the length. Hope that answers your question.

@ekryski @daffl so cool- love this :)

@imns81 Hey Nate! Glad you are liking it! We've added a TON of docs the last month so hopefully a lot of the stuff you were missing is now in place. If not and you have some suggestions for missing sections please open an issue, or even a PR ;-), and we'll get to it ASAP. IMHO open source projects and APIs live and die by their docs.

@micahbrich Awesome to hear. Would love to see some of the stuff you've built. Feel free to drop on by the slack room http://slack.feathersjs.com.

@iannaccone15 Hey Eric (nice name btw)! You can deploy them anywhere you would typically deploy a NodeJS or Express app. So Heroku, Modulus, Joyent, AWS and Digital Ocean all work great. We'll have a guide for Heroku soon and have some stuff in the works that will make all that a lot easier ;-)

@omarsar0 Thanks Omar! Really appreciate it.

@gcwelborn Glad you like it! Feel free to hit us up if you have any questions or issues. http://docs.feathersjs.com/help/...

@lanlau We all have to start somewhere :) Over the last couple of days we have however heard from a surprising number of people - besides ourselves and active contributors - that happily use it in production applications, some for almost two years already. So the core of Feathers is pretty stable and "just works" which I consider a good sign. As with any open source project there may be bumps in the road with some of the newer and more cutting edge things but even just this week the community has been doing a fantastic job in helping us iron those out so I'm very excited for the future.

@daffl thanks for your reply! Will continue to read the docs (by the way, you did a really good job on this) and play with it

@neilsatra I totally get that. Thanks for the very valid feedback. Feathers 2 has a very stable core that is well tested but any time you make a switch in technology there is risk, this is compounded when a technology is new and has been even more so in JavaScript lately. We've been working on Feathers for a couple years and plan on many more. Hope to see you around in 6 months!