hey! I think it would be better to start with a DBaaS like Firebase and learn React and friends before diving into the whole node.js ecosystem. It's a lot to take in on its own.. If you need a starting point take a look at my boilerplate or mern for a isomorphic approach. If you need a complete back-end solution I would recommend https://horizon.io/ [s]

Hello, Yes, I'm using Enzyme in several projects. It's way better than the plain react-addons-test-utils and the React team is recommending it in their page . You can check the implementation for Jest or Karma/Mocha/Expect .

I'm using keymetrics with pm2 to monitor the process, but it doesn't check for the socket health.

I like Trello too. Simple and direct.

Hello! 1. Why Flux? Flux is way to pass your data around in a simple unidirectional flow: an action is dispatched the store handle those actions (and its respective data) the store emits a change event your views responds for the change event and update themselves if needed In a MVC (or two-way-binding) system: the Controller1 receives an action from View1 and do something then Controller1 triggers an event that Controller2 listen and change View2 Add a little complexity and things get out of hand really fast with events triggering changes that you don't know where it comes. With Flux you can remove a lot of this complexity by having one source of true. 2. Why Redux vs vanilla flux? Flux isn't a library, it's an idea (and a Dispatcher) so you have to create your own version. As you app grows you'll end up with a few different stores. Ex: ComponentA needs UserStore, CommentStore, FavoriteStore and so on. A lot of listeners and unsubscribes. With plain Flux you'll have multiple flows, one for each store. Redux came to help with this. It's a state container with a "single" store with multiple branches representing different parts (flux stores) of your app. an action is dispatched the reducer handle the action and feed it to the store the store emits a change event your views responds for the change event and update themselves if needed It's a similar sequence but you don't need to worry about which store your components are subscribed or which actions you can dispatch. -- I think this course it's a good introduction to Redux: https://egghead.io/courses/getting-started-with-redux - from the creator, Dan Abramov Also, this is a good post about Flux: http://blog.andrewray.me/flux-for-stupid-people/ [s]