How gpr-indevelopment/cec-lambda-spring-quarkus-node-benchmark works
Main Components
a) Test Infrastructure Layer:
• JMeter Load Testing Component
• Cloudwatch Monitoring & Metrics
• Log Insights Component
b) Lambda Functions Layer (3 parallel implementations):
• Spring Cloud Function Implementation
• Quarkus Implementation
• NodeJS Implementation
c) External Dependencies Layer:
• CAMARA API (External Service)
[Spring] | [Quarkus] | [NodeJS]
[Load Testing (JMeter)]
• ↓
[Lambda URL Endpoint]
• ↓
[Lambda Runtime]
• ↓
[Framework Implementation]
• ↓
[External API Call]
Important Details
For each Lambda implementation, show:
• Runtime environment (Java 11 Corretto for Spring/Quarkus, NodeJS)
• Handler configurations
• Memory allocation
• Cold start metrics
• Average duration metrics
Metrics Visualization
A separate section showing comparative metrics:
• Cold start times
• Memory usage
• Average execution times
• Maximum duration
• Number of invocations
Technical Details to Note
For Java implementations:
• Spring: Handler: org.springframework.cloud.function.adapter.aws.FunctionInvoker::handleRequest
• Quarkus: Handler: io.quarkus.amazon.lambda.runtime.QuarkusStreamHandler::handleRequest
• Deployment package types (JAR vs ZIP)
Performance Comparison
• Cold start times (Spring: 6.66s, Quarkus: 7.29s, NodeJS: <0.5s)
• Memory usage (Spring: 190.5MB, Quarkus: 157.4MB, NodeJS: significantly less)
Remember to emphasize the performance testing aspect of the architecture, as this is primarily a benchmark comparison project rather than a production system.