Alternatives to JSON Server logo

Alternatives to JSON Server

MongoDB, JSON, Firebase, Mirage, and Postman are the most popular alternatives and competitors to JSON Server.
97
136
+ 1
7

What is JSON Server and what are its top alternatives?

Created with <3 for front-end developers who need a quick back-end for prototyping and mocking.
JSON Server is a tool in the API Tools category of a tech stack.
JSON Server is an open source tool with 54.7K GitHub stars and 5.2K GitHub forks. Here’s a link to JSON Server's open source repository on GitHub

Top Alternatives to JSON Server

  • MongoDB

    MongoDB

    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding. ...

  • JSON

    JSON

    JavaScript Object Notation is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language. ...

  • Firebase

    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Mirage

    Mirage

    The Elasticsearch query DSL supports 100+ query APIs ranging from full-text search, numeric range filters, geolocation queries to nested and span queries. Mirage is a modern, open-source web based query explorer for Elasticsearch. ...

  • Postman

    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Amazon API Gateway

    Amazon API Gateway

    Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management. ...

  • Insomnia REST Client

    Insomnia REST Client

    Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux. ...

  • OpenAPI

    OpenAPI

    It is a publicly available application programming interface that provides developers with programmatic access to a proprietary software application or web service. ...

JSON Server alternatives & related posts

MongoDB logo

MongoDB

56.6K
46.2K
4.1K
The database for giant ideas
56.6K
46.2K
+ 1
4.1K
PROS OF MONGODB
  • 823
    Document-oriented storage
  • 589
    No sql
  • 545
    Ease of use
  • 463
    Fast
  • 405
    High performance
  • 253
    Free
  • 214
    Open source
  • 178
    Flexible
  • 140
    Replication & high availability
  • 108
    Easy to maintain
  • 40
    Querying
  • 36
    Easy scalability
  • 35
    Auto-sharding
  • 34
    High availability
  • 30
    Map/reduce
  • 26
    Document database
  • 24
    Easy setup
  • 24
    Full index support
  • 15
    Reliable
  • 14
    Fast in-place updates
  • 13
    Agile programming, flexible, fast
  • 11
    No database migrations
  • 7
    Enterprise
  • 7
    Easy integration with Node.Js
  • 5
    Enterprise Support
  • 4
    Great NoSQL DB
  • 3
    Aggregation Framework
  • 3
    Support for many languages through different drivers
  • 3
    Drivers support is good
  • 2
    Schemaless
  • 2
    Fast
  • 2
    Awesome
  • 2
    Managed service
  • 2
    Easy to Scale
  • 1
    Consistent
CONS OF MONGODB
  • 5
    Very slowly for connected models that require joins
  • 3
    Not acid compliant
  • 1
    Proprietary query language

related MongoDB posts

Jeyabalaji Subramanian

Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

Based on the above criteria, we selected the following tools to perform the end to end data replication:

We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

See more
Robert Zuber

We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

See more
JSON logo

JSON

1.3K
1.1K
8
A lightweight data-interchange format
1.3K
1.1K
+ 1
8
PROS OF JSON
  • 4
    Simple
  • 4
    Widely supported
CONS OF JSON
    Be the first to leave a con

    related JSON posts

    Ali Soueidan
    Creative Web Developer at Ali Soueidan · | 18 upvotes · 743.3K views

    Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

    For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

    To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

    DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

    Side note: I used npm for package management. 🎉

    *Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

    See more

    I use Visual Studio Code because at this time is a mature software and I can do practically everything using it.

    • It's free and open source: The project is hosted on GitHub and it’s free to download, fork, modify and contribute to the project.

    • Multi-platform: You can download binaries for different platforms, included Windows (x64), MacOS and Linux (.rpm and .deb packages)

    • LightWeight: It runs smoothly in different devices. It has an average memory and CPU usage. Starts almost immediately and it’s very stable.

    • Extended language support: Supports by default the majority of the most used languages and syntax like JavaScript, HTML, C#, Swift, Java, PHP, Python and others. Also, VS Code supports different file types associated to projects like .ini, .properties, XML and JSON files.

    • Integrated tools: Includes an integrated terminal, debugger, problem list and console output inspector. The project navigator sidebar is simple and powerful: you can manage your files and folders with ease. The command palette helps you find commands by text. The search widget has a powerful auto-complete feature to search and find your files.

    • Extensible and configurable: There are many extensions available for every language supported, including syntax highlighters, IntelliSense and code completion, and debuggers. There are also extension to manage application configuration and architecture like Docker and Jenkins.

    • Integrated with Git: You can visually manage your project repositories, pull, commit and push your changes, and easy conflict resolution.( there is support for SVN (Subversion) users by plugin)

    See more
    Firebase logo

    Firebase

    24.7K
    20.7K
    1.9K
    The Realtime App Platform
    24.7K
    20.7K
    + 1
    1.9K
    PROS OF FIREBASE
    • 361
      Realtime backend made easy
    • 263
      Fast and responsive
    • 234
      Easy setup
    • 207
      Real-time
    • 186
      JSON
    • 127
      Free
    • 121
      Backed by google
    • 81
      Angular adaptor
    • 63
      Reliable
    • 36
      Great customer support
    • 26
      Great documentation
    • 23
      Real-time synchronization
    • 20
      Mobile friendly
    • 17
      Rapid prototyping
    • 12
      Great security
    • 11
      Automatic scaling
    • 10
      Freakingly awesome
    • 8
      Chat
    • 8
      Angularfire is an amazing addition!
    • 8
      Super fast development
    • 6
      Awesome next-gen backend
    • 6
      Ios adaptor
    • 5
      Built in user auth/oauth
    • 5
      Firebase hosting
    • 4
      Speed of light
    • 4
      Very easy to use
    • 3
      It's made development super fast
    • 3
      Great
    • 3
      Brilliant for startups
    • 2
      Great all-round functionality
    • 2
      Low battery consumption
    • 2
      I can quickly create static web apps with no backend
    • 2
      The concurrent updates create a great experience
    • 2
      JS Offline and Sync suport
    • 1
      Faster workflow
    • 1
      Large
    • 1
      Serverless
    • 1
      .net
    • 1
      Free SSL
    • 1
      Good Free Limits
    • 1
      Push notification
    • 1
      Easy to use
    • 1
      Easy Reactjs integration
    CONS OF FIREBASE
    • 28
      Can become expensive
    • 15
      Scalability is not infinite
    • 14
      No open source, you depend on external company
    • 9
      Not Flexible Enough
    • 5
      Cant filter queries
    • 3
      Very unstable server
    • 2
      Too many errors
    • 2
      No Relational Data

    related Firebase posts

    Stephen Gheysens
    Senior Solutions Engineer at Twilio · | 12 upvotes · 120.4K views

    Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

    My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

    See more
    Tassanai Singprom

    This is my stack in Application & Data

    JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

    My Utilities Tools

    Google Analytics Postman Elasticsearch

    My Devops Tools

    Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

    My Business Tools

    Slack

    See more
    Mirage logo

    Mirage

    14
    35
    1
    GUI for writing Elasticsearch queries
    14
    35
    + 1
    1
    PROS OF MIRAGE
    • 1
      Clean GUI
    CONS OF MIRAGE
      Be the first to leave a con

      related Mirage posts

      Postman logo

      Postman

      56.1K
      44.4K
      1.7K
      Only complete API development environment
      56.1K
      44.4K
      + 1
      1.7K
      PROS OF POSTMAN
      • 481
        Easy to use
      • 366
        Great tool
      • 274
        Makes developing rest api's easy peasy
      • 154
        Easy setup, looks good
      • 142
        The best api workflow out there
      • 53
        History feature
      • 53
        It's the best
      • 43
        Adds real value to my workflow
      • 41
        Great interface that magically predicts your needs
      • 34
        The best in class app
      • 10
        Can save and share script
      • 9
        Fully featured without looking cluttered
      • 7
        Collections
      • 6
        Global/Environment Variables
      • 6
        Shareable Collections
      • 6
        Dead simple and useful. Excellent
      • 6
        Dark theme easy on the eyes
      • 6
        Option to run scrips
      • 5
        Awesome customer support
      • 5
        Great integration with newman
      • 4
        The test script is useful
      • 3
        This has simplified my testing significantly
      • 3
        Easy as pie
      • 3
        Simple
      • 3
        Documentation
      • 3
        Makes testing API's as easy as 1,2,3
      • 3
        Saves responses
      • 2
        API-network
      • 2
        Mocking API calls with predefined response
      • 2
        I'd recommend it to everyone who works with apis
      • 1
        Pre-request Script and Test attributes are invaluable
      • 1
        Postman Runner CI Integration
      • 1
        Now supports GraphQL
      • 1
        Continuous integration using newman
      • 1
        Easy to setup, test and provides test storage
      • 1
        Graph
      • 0
        <a href="http://fixbit.com/">useful tool</a>
      • 0
        Runner
      CONS OF POSTMAN
      • 8
        Stores credentials in HTTP
      • 7
        Poor GraphQL support
      • 6
        Bloated features and UI
      • 5
        Cumbersome to switch authentication tokens
      • 1
        Expensive
      • 1
        Can't prompt for per-request variables

      related Postman posts

      Noah Zoschke
      Engineering Manager at Segment · | 30 upvotes · 1.9M views

      We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

      Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

      Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

      This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

      Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

      Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

      Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 24 upvotes · 1.7M views

      Our whole Node.js backend stack consists of the following tools:

      • Lerna as a tool for multi package and multi repository management
      • npm as package manager
      • NestJS as Node.js framework
      • TypeScript as programming language
      • ExpressJS as web server
      • Swagger UI for visualizing and interacting with the API’s resources
      • Postman as a tool for API development
      • TypeORM as object relational mapping layer
      • JSON Web Token for access token management

      The main reason we have chosen Node.js over PHP is related to the following artifacts:

      • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
      • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
      • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
      • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
      See more
      Amazon API Gateway logo

      Amazon API Gateway

      1.1K
      800
      39
      Create, publish, maintain, monitor, and secure APIs at any scale
      1.1K
      800
      + 1
      39
      PROS OF AMAZON API GATEWAY
      • 35
        AWS Integration
      • 4
        Websockets
      CONS OF AMAZON API GATEWAY
      • 1
        No websocket broadcast
      • 1
        Less expensive

      related Amazon API Gateway posts

      A Luthra
      VP Software Engrg at Reliant · | 2 upvotes · 293K views
      Shared insights
      on
      Apigee
      Amazon API Gateway

      Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

      See more
      Insomnia REST Client logo

      Insomnia REST Client

      509
      422
      34
      The most intuitive cross-platform REST API Client 😴
      509
      422
      + 1
      34
      PROS OF INSOMNIA REST CLIENT
      • 14
        Easy to work with
      • 9
        Great user interface
      • 5
        Works with GraphQL
      • 2
        Preserves request templates
      • 2
        Opensource
      • 2
        Cross platform, available for Mac, Windows, and Linux
      • 0
        Does not have history feature
      • 0
        Vim and Emacs key map
      CONS OF INSOMNIA REST CLIENT
      • 1
        Do not have team sharing options
      • 1
        Do not store credentials in HTTP

      related Insomnia REST Client posts

      Jason Barry
      Cofounder at FeaturePeek · | 4 upvotes · 1.8M views

      We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

      • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
      • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
      • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

      Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

      See more
      OpenAPI logo

      OpenAPI

      255
      224
      0
      Allows the owner of a network-accessible service to give universal access
      255
      224
      + 1
      0
      PROS OF OPENAPI
        Be the first to leave a pro
        CONS OF OPENAPI
          Be the first to leave a con

          related OpenAPI posts

          Joshua Dean Küpper
          CEO at Scrayos UG (haftungsbeschränkt) · | 4 upvotes · 186K views

          We use Swagger Inspector in conjunction with our universal REST-API "Charon". Swagger Inspector makes testing edge-cases hassle-free and lets testing look easy. Swagger Inspector was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.

          We previously used Postman but decided to switch over to Swagger Inspector because it also integrated seamlessly into Swagger UI, which we use for displaying our OpenAPI specification of said REST-API.

          See more