Here are a few reasons why I use meteor and why you should. Still wondering at the end of the article? Write a quick comment and I can help out.

What once took weeks/months now only takes hours/days with meteor.

It’s fast

If you want to quickly prototype an app idea it’s super easy to get started with meteor and prototype. Meteor comes with a few default packages that make this easy so you don’t have to worry about a whole lot of things. All the accounts- packages help with setting up user login/register/invite systems so you don’t have to build them from the ground up.

Insecure and auto publish let you access any collection in your database so you can focus on basic functionality before setting up the user accounts and permission for collections. Though, it’s safe to say you should probably remove this when you are ready to publish your app or let someone test it.

Lastly. Meteor doesn’t render HTML on the server side. It does all of that on the client side with Blaze.

It’s Reactive

Creating a simple chat application that’s real-time doesn’t take much at all. That’s because of Meteor’s Blaze templating engine. Blaze is the brains behind the reactiveness in meteor and it decides what to update in the DOM. Remember, meteor doesn’t render HTML on the server side, Blaze does this on the client side when it receives data from the server.

When you perform database operations, it will update on the client side before the database is even updated. This happens because it simulates what the database is doing on the client. You can even access the Mongo database from the console in your browser, meteors MiniMongo allows this database clone to take place.

Package Management

Meteor has a built-in package management system to install various things into your project and use them right away. Atmosphere helps by letting you search through the library of awesome packages.

File Structure

You can define your own file structure with meteor. Meteor takes all of the html files and compiles them into one file technically. So you don’t even need to organize files in folders or remember where they are(you should to be a sane developer), but the point is Meteor knows where everything is. Same goes for the Javascript files.

There are certain folders you can use such as server, client, public, and private. These folders are for specific uses. Server folder runs only on the server, client runs on the client, public is for images/etc, and private is assets that are only accessible on the server via the Assets API.

You can even have files that are accessible to both the server and the client. This is useful for databases, helper methods, and configuration for different things.

There are many templates/boilerplates for building meteor apps and I have one that I use on almost every project I work on with meteor.

Easy to Deploy

There are about 5 different ways that I know about to deploy a meteor app and that’s awesome. Giving you the flexibility to deploy an app however you want is great.

First off there is Meteor Up which is probably best with a fresh server or existing server if you know what you’re doing. There are 3 commands to get you started and deployed with this setup. I will post an article on how to deploy a meteor app to DigitalOcean using Meteor Up.

There is also Heroku, Modulus, and a few others I can’t quite remember right now.


You should definitely checkout meteor if you have or haven’t heard of it. It’s a great tool to build apps quickly that are small or big. Let me know what you think and also checkout the Discover Meteor Book by Sacha Grief and Tom Coleman. That’s a great place to start if you want to learn all about it. There is also the Meteor Docs which is probably the most helpful once you get familiar with the basics.