Not much, but the concepts of how Meteor works under the hood is beneficial in order not to misunderstand how it works under the hood and avoid the traps of all the magic it does.<p>Here&#x27;s a few things you should read more about prior to or when you are writing Meteor:<p>- Architecture of Meteor - Because hype told us you&#x27;re writing one big JS app and throwing away the idea of client-server. NO, you will still end up writing client-only and server-only code, esp validations and API calls (which you don&#x27;t really want to put in client-side code).<p>- Node.js - It&#x27;s handy to know what you can use in server-side code to avoid duplicating work.<p>- AJAX - The concept of server-side methods closely mimics AJAX (call and callback style).<p>- MongoDB - Basic knowledge of CRUD functions in Mongo are nice to have. Especially &quot;upsert&quot; (insert&#x2F;update) which was very handy in place of &quot;check if exists and update or insert&quot; operations.<p>- Basics on reactive programming - Under the hood, everything&#x27;s observed. When things change, it&#x27;s a domino effect afterwards.