1. Architecture: Meteor follows a full-stack architecture, providing both client-side and server-side development under a single framework, whereas Spring is Java-based and follows a modular architecture, enabling developers to choose and integrate different modules as needed.
2. Real-time capabilities: Meteor is known for its reactivity and real-time features out of the box, making it ideal for applications that require live updates, while Spring requires additional configurations and libraries to achieve the same real-time capabilities.
3. Language support: Meteor primarily uses JavaScript with Node.js on the server side, making it easier for JavaScript developers to work across the stack, whereas Spring is focused on Java and supports other JVM languages, providing a broader range of language options for developers.
4. Community and ecosystem: Meteor has a smaller but more tightly-knit community and ecosystem, with limited third-party integrations and libraries compared to the vast Spring ecosystem, which offers extensive support, plugins, and integrations for various enterprise solutions.
5. Scalability and Performance: Spring, with its lightweight and modular approach, is considered more scalable and suitable for large-scale enterprise applications, while Meteor's simplicity can sometimes lead to performance issues when dealing with complex and high-traffic applications.
6. Learning Curve: Meteor provides a more straightforward learning curve for beginners due to its all-in-one nature, while Spring's modular structure and configuration options can make it more challenging for newcomers to grasp initially.

In Summary, Meteor and Spring differ in their architecture, real-time capabilities, language support, community and ecosystem, scalability and performance, as well as in learning curve.