Very interesting! Haven't experimented too much yet, but looking forward to getting something started soon.
How flexible is Feathers when using an API as backend instead of a DB? For example, in my experience Meteor makes it extremely difficult to use anything but MongoDB when trying to retrieve / persist objects.
@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....
Report
Do you have a solution for hosting applications built with FeathersJS? I've had a ton of trouble in the past trying to deploy Meteor anywhere.
@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 ;-)
@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.
I've adopted FeathersJS and haven't looked back. It plays well with React and allows you to build universal JS apps. The ability to modularize your code with before and after hooks and the ability to easily break services out into their own microservice is huge.
I would love to see more documentation, right now a lot of the pages aren't finished, but I'm sure they are working hard on fixing that.
@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.
The project looks very promising! One question I have is how many simultaneous connections can Feathers serve since it is using SocketIO as its real - time base?
SiteSpeakAI
FeathersJS
FeathersJS
Substack
FeathersJS
Substack
Laser Kitten
FeathersJS
Flow Lines
Culture Colors
FeathersJS
Readable Technologies
FeathersJS