Last week I spent a couple of days understanding and trying Meteor. And… it has an incredible amount of documentation on different levels.
- Meteor uses data on the wire, meaning the server sends data, not HTML, and the client renders it.
- Meteor provides full stack reactivity, allowing your UI to seamlessly reflect the true state of the world with minimal development effort.
From the architecture point of view it covers almost all the topics that you can think of:
- separation of client and server, but the developer is not noticing the difference between them if the ‘autopublish’ package is added.
- the communication between client and server is done using publish subscribe
- the application structure is easy to use and offers flexibility. the only real constrain is: to the new module system code must be placed inside the imports/ directory in your application.
- it follows a coding style and you can enforce it in your project tool
- supports different UI templating engines: Blaze, Angular, React.
- it has an incredible amount of packages build buy the team or by community and you can get them from npm and Atmosphere.
- they cover a lot of topics regarding security and offer best practices
- the deployment and monitoring is easy and fast and we can use different settings for dev, staging, live.
- it uses MongoDB but there are different packages that make possible building an App using Meteor with Oracle or with Postgres.
Other cool stuff: