I’m developing a pretty simple web application, it imports data and spits it out into the UI and allows the user to update the status of the data. But the developer I am talking to wants to use Meteor and I’m not familiar with it. I have concerns with the frontend and backend being too integrated. Any other concerns I should be aware of?
I don’t see an issue with using Meteor for the type of application you described. After all, it’s built on top of NodeJS – so if you know anything about Node, then you know it’s very scalable and can handle large amounts of concurrent connections. Meteor performs well, and from your web app description you should have an app ready very quickly (Meteor is very easy to prototype with). The front and back-end are definitely coupled, but that shouldn’t matter in your case. Meteor also has a pretty decent library to fall back on, so you probably wouldn’t be reinventing the wheel at all by using it.
– Fast to develop real-time, single-page, cross-platform applications. You can develop a prototype including web app, iOS, Android app during your free time.
– Easy to scale using Galaxy or Meteor UP. You can also architect your apps into micro-services.
– Although it is easy to learn and develop, you need to deeply understand NodeJS in order fully customize your apps. Sometimes easy things can be difficult in Meteor if you do not really understand how it works.
– It only works well with MongoDB.
– You’ll need to keep track of all NPM modules and their versions being used in the application. Sometimes versions conflict or are unsupported when used in conjunction with certain modules and their versions (all of which are contained in package.json).
In conclusion: Meteor changes very oftent, this is both pro and con. So you really need to follow and up to date frequently.