Parse-Server VS JsonAPI

Parse-Server Reviews

JsonAPI Reviews

Parse-Server mentions (5)

• What to choose for backend

  If you like headless CMS / Backend As A Service you should consider https://directus.io/ or https://github.com/parse-community/parse-server. Both nodejs and open source. Source: almost 2 years ago

• Any general purpose visualisation "just add the data" framework

  There's numerous standard backends which frontenders could use in simplistic cases to start, say https://github.com/PostgREST/postgrest or https://github.com/parse-community/parse-server. Source: over 2 years ago

• Show HN: Caffeine, minimum viable back end for prototyping

  Parse is still around and supported: https://github.com/parse-community/parse-server. - Source: Hacker News / over 2 years ago

• Ask HN: What Back End Framework with User Management Is Your Favorite?

  I am curious what backend framework you would choose to run with for prototyping an application with run of the mill user management requirements. That is functionality along the lines of: session management, password policies, password reset, user verifications, etc. Sadly it seems there really aren't any frameworks that have user management natively supported. The only one I am aware of is [Parse... - Source: Hacker News / almost 3 years ago

• [Open Source] I made my first app. Its a fully functional social media app. And I decided to open source it.

  I believe you are referring to main.js file. The answer is no. I used parse server for backend. And by default all classes are public which means everyone can read every data. There is a preferred way to prevent this. You disable all class level permissions for every class. Then you put your app logic to cloud code which is main.js file you were looking at. Here is an article about this... Source: about 3 years ago

JsonAPI mentions (44)

• Path To A Clean(er) React Architecture - API Layer & Data Transformations

  Note: You think the response data structure with the data field and the included field with mixed data types looks weird? You might not have encountered the popular JSON:API standard yet. - Source: dev.to / 5 days ago

• Hatchify: The Fastest Way to Build JSON: APIs

  In addition to saving you time on boilerplate, the API provided by Hatchify fully implements the JSON: API specification, which stipulates solid standards to define the peculiarities of CRUD REST APIs. Get back all the time spent bike-shedding how to implement standard API features like filtering, pagination, including related data, etc. JSON: API offers consistent practices for frontend and backend developers to... - Source: dev.to / about 2 months ago

• Show HN: Sunnybox – An Email API for Effortless IMAP Integration

  -JSON:API format responses (https://jsonapi.org) for better standardization. Built using Ruby on Rails, Sunnybox is designed to offer a powerful yet easy-to-use solution for developers managing email systems. I'd really appreciate your feedback on: - The API's user-friendliness and efficiency. - Source: Hacker News / 5 months ago

• Custom Fields: Give Your Customers the Fields They Need

  As we’re building a RESTful API that’s formatted by the JSON:API specification and store our data in a MySQL8 relational database, a few things were pretty straightforward – we need a new model and we’ll name it Custom Field (naming wasn’t an issue here 🥲). - Source: dev.to / 6 months ago

• How to (and how not to) design REST APIs

  I found json api spec[1] recently. This kind of is better standard for REST APIs. It is bit rough to handle client side but once you get the hang of it, it is breeze to use [1] https://jsonapi.org/. - Source: Hacker News / 6 months ago