Skip to main content

EzBackend Performance

EzBackend utilises fastify, instead of express.js, under the hood to reduce request latency. Furthermore, for the most common CRUD operations EzBackend is designed to minimise the latency of these operations.

Benchmarks: Express/Postgres vs EzBackend

caution

These benchmarks are not an apples-to-apples comparison. There may be minor functionality differences.

When performance is a concern, make sure that benchmarks are performed on the relevant 'expensive' operation, and that benchmarks are conducted on the machine that will be used in production for accurate results

Take note that benchmarks performed are for the most basic reads and writes. Performance will vary depending on the complexity of the actual operation

To compare performance, we developed two backends

  1. Express + Postgres
  2. EzBackend

With the following criteria:

  1. Postgres Database
  2. Two DB Tables
    1. Users Table
    2. Posts Table
  3. Google Auth
  4. CRUD Endpoints

You can view the sample apps here

Read Operations

FrameworkRequests/sLatencyThroughput/Mb
read-ezbackend-postgres-sample25002.970.73
read-express-postgres-sample1428.66.260.54
read-express-mongo-sample1250.07.440.42

Write Operations

FrameworkRequests/sLatencyThroughput/Mb
write-ezbackend-postgres-sample1667.24.520.55
write-express-postgres-sample1111.17.680.46
write-express-mongo-sample909.110.080.33
info

Benchmark Machine:

Processor Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz 2.59 GHz

Installed RAM 24.0 GB (23.8 GB usable)