> Database Everywhere. Use the same transparent API to
> access your database from the client or the server.
Is this a good thing? I have been always under impression that separating data management and application logic is a good idea - basically a must.
Meaning lets think about more complex way to look at the database (temporal, stream, event processing, etc.). How this can be then possible?
It's always a good idea to separate business logic from presentation logic. The idea in Meteor is that your business logic can run on either the client or the server as is appropriate in a given situation. For example, if you want to get the most recent 10 posts in the news feed, the exact same line of code works on both the client and server. Why have two APIs for this when you could have one? Of course the server still has to make sure that clients can't read or write to records they shouldn't (cf point 6, "Sensitive code runs in a privileged environment.")
I have questions about the following:
Is this a good thing? I have been always under impression that separating data management and application logic is a good idea - basically a must. Meaning lets think about more complex way to look at the database (temporal, stream, event processing, etc.). How this can be then possible?