I'll jump on when they have first-class support for a DB that isn't Mongo.

If you don't mind spinning up your own server instances, our open source mobile JSON stack handles application level concerns like access control and data routing. Might be worth taking a look, as it gives you access to a whole open source ecosystem with support from multiple vendors and for most platforms. http://developer.couchbase.com/mobile

[edit] Here's a little hello world tutorial I wrote a few months ago with Couchbase Lite and React Native. https://gist.github.com/jchris/3c32524577deff3d69aa

Why on Earth was this downvoted? Seems relevant and useful to me.

wow that seems pretty easy to get a local database going in a Native React app.

Give me postgres support and I'll definitely consider switching what I have in the short term.

I'm happy to wait until then!

try including this package https://github.com/numtel/meteor-pg

It's coming! MDG is focusing 100% on their Heroku-like platform called Galaxy and once that's done they may push on to relational database support.

Graph DBs support is ok too :)

There is already graph db (Neo4j) support available using the "ccorcos:anydb" package.

https://github.com/ccorcos/meteor-any-db

there are third party developers working on SQL support, this one for example adds reactive queries for Postgres: https://github.com/numtel/meteor-pg

Microservices to the rescue?

Meteor+React is surprisingly good at what it does.

I'd highly recommend this new project for Meteor+React+Webpack:

https://github.com/thereactivestack/meteor-webpack-react-kic...

The only thing that I really disliked in Meteor was the reload/refresh for larger projects. This is typically a problem with anything Node related and refresh/reload times were around 10 seconds at its worst.

With the Webpack+React+Webpack, you get hot loading of only the module that has changed. Since much of the logic is on the client, your server code stays slim. Refresh times went from around 10 seconds to faster-than-I-can-notice.

Now if only there was a way to get hot module reloading working on the server...

Are you seeing 10 second rebuilds with incremental builds? Or is this 10 seconds for a complete rebuild?

With incremental builds. I have forked this project: https://github.com/wekan/wekan (~ medium size). On a 2014 macbook pro, reloading after a change in a template takes 10s. Not a dealbreaker, but this is frustrating. And this is with meteor 1.2. The slow build times may be due to the wierd frontend preprocessors (jade and stylus), but still.

Wekan author here. On my computer hot reload takes roughly 5s [Thinkpad T440s, ubuntu, 12go of RAM]. I'm not sure if the jade and stylus compilers add some time in the case I only modify JavaScript files, but anyway I plan to migrate these two package to support the new compiler API.

Still 5s is far from ideal considering the development experience with webpack and React hot loader.

This was my worst case and I did get it down to around 5-6 seconds by removing some Meteor packages (Meteor Toys in particular added a lot to build times but I also removed Velocity testing).

I believe they were incremental builds. Whatever happens by default when you make a change to a file.

Are there any good guides/videos on getting started with Meteor+React?

They have a pretty "getting started" on their site: https://www.meteor.com/tutorials/blaze/creating-an-app

There is an official guide: https://www.meteor.com/tutorials/react/creating-an-app

Thanks for the link.

On first glance seems like writing in React is way more verbose and cumbersome than the Blaze equivalent. What are the benefits of going the React route?

how is it compared to relay+graphql?