Architecture of parse-community/parse-server
parse-community/parse-server is 454 source files holding 1,770 symbols across 9 modules, written mainly in JavaScript, TypeScript, Shell. The largest module is src, with 202 files, and 11 files are entry points into the dependency graph.
How parse-server fits together
Incoming HTTP requests, including REST and SDK calls and GraphQL queries, reach the server that the scripts in bin assemble and launch. The core logic lives in src, which holds most of the code, and it routes requests, checks permissions, and reads or writes objects through internal services and controllers. Server options are defined in src/Options/Definitions.js and src/Options/index.js, and they can be supplied as an options object or a JSON configuration file. The GraphQL side of the API is implemented in src/GraphQL/ParseGraphQLServer.js. Cross-cutting services such as pushes, file uploads and authentication are provided through configurable adapters. The spec directory holds the test files, and the ci directory holds checks such as ci/nodeEngineCheck.js that verify compatibility.
Largest modules
- src: 202 files and 36,827 lines of code
- spec: 160 files and 108,404 lines of code
- types: 9 files and 455 lines of code
- root: 6 files and 447 lines of code
- ci: 5 files and 348 lines of code
- benchmark: 2 files and 753 lines of code
- bin: 2 files and 4 lines of code
- scripts: 2 files and 27 lines of code
Languages
By file count: JavaScript 364 files, TypeScript 12 files, Shell 5 files, Dockerfile 1 file.
Documentation
Repowise documents parse-server in 417 pages generated from the source, 25 of them written explanations of the repository and its modules. Module guides include:
- src/Routers: API Router Map
- src/Adapters: Adapters Overview
- src/Adapters/Auth: Authentication Adapters
More on parse-server: summary and FAQ, codebase overview, code health.
Related guide: Best dependency graph tools for monorepos