JSON Server vs Mirage: What are the differences?

1. Data Persistence: One key difference between JSON Server and Mirage is that JSON Server utilizes a JSON file as a database, meaning data persists even after server restarts, while Mirage stores data only in-memory during the current session.

2. Server Dependency: JSON Server requires running a separate server to serve requests, while Mirage operates within the application itself, eliminating the need for an external server dependency.

3. Realism in Data: Mirage allows developers to create more realistic data scenarios by defining dynamic responses, whereas JSON Server sticks to static data responses stored in the JSON file.

4. Network Delay Simulation: Mirage enables simulation of network delays and failures for testing purposes, which is not a feature offered by JSON Server.

5. Programming Language Support: JSON Server is a standalone tool that works with any programming language, while Mirage is specifically designed for use with Ember.js, making it more tailored to that framework.

6. Custom Routes Configuration: Mirage provides more flexibility in configuring custom routes and responses compared to JSON Server, allowing developers to mimic various API endpoints and responses for testing or development purposes.

In Summary, JSON Server and Mirage differ in data persistence, server dependency, realism in data, network delay simulation, programming language support, and custom routes configuration.