Benchmark: 2-tier vs 3-tier Object.assign vs 3-tier spread vs 3-tier constructor

2-tier vs 3-tier Object.assign vs 3-tier spread vs 3-tier constructor (version: 0)

This demonstrates the difference in performance between 2-tier architectures, which simply return database objects through controllers from the repositories vs 3-tier architectures which run some sort of service layer mapping to obfuscate unnecessary db information from both the controller layer and, subsequently, the front-end. Such mapping logic will ideally use Object.assign, the spread operator, or perhaps an explicit constructor mapping.

Comparing performance of: 2-tier vs 3-tier Object.assign vs 3-tier spread vs 3-tier constructor

Created: 6 years ago by: Guest

Jump to the latest result

Tests:

2-tier
var dbData = { databaseIdName: "5d493b95-6255-4662-8de5-875370997a7c", a: 1, b:"hello", c: true, d:7, e: "test", f: "getting", g: "longer", h: false, i: "but more realistic for enterprise development" }; return dbData;
3-tier Object.assign
var dbData = { databaseIdName: "5d493b95-6255-4662-8de5-875370997a7c", a: 1, b:"hello", c: true, d:7, e: "test", f: "getting", g: "longer", h: false, i: "but more realistic for enterprise development" }; var appData = Object.assign({ id: dbData.databaseIdName }, dbData); delete appData.databaseIdName; return appData;
3-tier spread
var dbData = { databaseIdName: "5d493b95-6255-4662-8de5-875370997a7c", a: 1, b:"hello", c: true, d:7, e: "test", f: "getting", g: "longer", h: false, i: "but more realistic for enterprise development" }; var { databaseIdName, ...appData } = dbData; appData.id = databaseIdName; return appData;
3-tier constructor
var dbData = { databaseIdName: "5d493b95-6255-4662-8de5-875370997a7c", a: 1, b:"hello", c: true, d:7, e: "test", f: "getting", g: "longer", h: false, i: "but more realistic for enterprise development" }; class AppData { constructor(databaseIdName, a, b, c, d, e, f, g, h, i){ this.id = databaseIdName; this.serviceA = a; this.serviceB = b; this.serviceC = c; this.serviceD = d; this.serviceE = e; this.serviceF = f; this.serviceG = g; this.serviceH = h; this.serviceI = i; } } var appData = new AppData( dbData.databaseIdName, dbData.a, dbData.b, dbData.c, dbData.d, dbData.e, dbData.f, dbData.g, dbData.h, dbData.i ) return appData;

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
2-tier
3-tier Object.assign
3-tier spread
3-tier constructor

Fastest: N/A

Slowest: N/A

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

Run details: (Test run date: 6 years ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Browser/OS: Chrome 68 on Mac OS X 10.13.4

View result in a separate tab

Test name	Executions per second
2-tier	663661600.0 Ops/sec
3-tier Object.assign	555777.8 Ops/sec
3-tier spread	432168.4 Ops/sec
3-tier constructor	46808.9 Ops/sec

2-tier vs 3-tier Object.assign vs 3-tier spread vs 3-tier constructor (version: 0)

Comparing performance of: 2-tier vs 3-tier Object.assign vs 3-tier spread vs 3-tier constructor

Created: 6 years ago by: Guest

Jump to the latest result

2-tier

3-tier Object.assign

3-tier spread

3-tier constructor

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A