This repository contains a brief overview of (http://meteor.com)[Meteor] and an list of its major packages.
The following features distinguish Meteor from other web-platforms:
- data over the wire
- In Meteor client and server exchange data, not HTML.
- single page app (SPA)
- This means that the client is loaded as a whole at start-up and then manages the user interaction without unnecessary calls to the server. This makes for a smooth user-experience.
- no REST
- As you can access data from the client just as you would from the server, data over the wire also means that there is not need for REST interfaces.
- full-stack
- In Meteor the functionality on both the server (through node.js) and the client (through the browser) is implemented in Javascript (ES2015+ to be exact). This saves the developer from continuously having to switch between languages.
- multi-platform
- With Meteor you can build apps for web, iOS, and Android from the samen code base. Nou mar nerd Cordova for platform-specific features.
- no SQL
- Meteor uses Mongodb as its data backend. Mongodb is document-based and does not use SQL.
- reactivity
- Data in Meteor is updated everywhere once it changes. This includes all active clients, which adds to the smooth user-experience.
The mindmap below shows how I understand Meteor:
The client handles routing and rendering. Routing is taken care of by Flow router, which uses Blaze as template engine (Angular and React are also supported). Templates are divided in three layers:
- layouts define the general structure of your site, using pages
- pages are smart, which means they collect data and feed them to components
- components do not interact with anything except though parameters, which makes them highly reusable
Templates can be controlled through helpers and event handlers (including onCreated).
The server uses Mongodb as a datastore. Data is stored in collections, which are basically persistent JSON documents. A schema language is used to define the datastructures, so data can be validated. Schema also drive the autoform package. Collections can be controlled through helpers and hooks.
The client and server communicate through a publish/subscribe mechanism and through methods. The server controls data access by selectively publishing data to the client. The client (pages) collect data through subscriptions. Methods are Meteor's remote procedure calls (RPCs) and can use schema for data validation.
Some final tips & tricks:
- waitOn (package Iron Router) lets you defer execution untill a subscription has finished
- Meteor methods can be called synchronously on the server, but must be called asynchronously on the client
- Global variables aren't available from templates. Access them with template helper.
- add c:\Windows\System32 to path on tasklist.exe error
- The autorun function lets you define a function that is run automatically when a reactive data source changes.
Just like all other modern frameworks, Meteor relies heavily on third party packages from its thriving eco-system. The Meteor Guide gives an opinionated overview of which packages to use. The table below shows these packages in the middle column, along with some additional packages I prefer in the final column. For more packages visit Atmosphere js. You can import all these package definitions by importing the file packages from this repository into the file packages of your project and the remove any package you don't need.
| subject | guide | extra |
|---|---|---|
| Out of the box | ||
| Collections | ||
| Data-loading | ||
| Methods | ||
| User accounts | ||
| Routing | ||
| UI-UX | ||
| Other | ||
| Testing |
| |
| Deployment |