We’re using ElasticBeanstalk Blue/Green deployment by swapping DNS, and in front of the deployed services, there’s a company level Nginx to forward requests to different services. The TTL of DNS entry set to 1 minute, and Nginx will cache the resolved name entries until it expired. Each time after we deploy, all the requests hit the new environment after the DNS cache expired in Nginx.
React Server Render time without warming up
The response time increases a lot in the following a couple of minutes and becomes stable after 5 minutes. Because the response time impacted by upstream services, it’s better to analyze and improve react server render time which is a sync method call and not involve IO operations.
Here’s the initial reactServerRender time for Home Page and Search Result Page:
For the Home page, it took 2-3 minutes for the reactRender time reduced from 450 – 550 ms to 120 ms
From the documentation, AWS Lambda will retry failed function on stream-based events sources.
By using Node.js, we can fail the function by many different ways, e.g. using callback to return error, throw exception directly, throw exception inside Promise, using Promise.reject. Then the questions is, what’s the proper way to let AWS Lambda know it needs a retry?
I did an quick test on following scenarios by setting up DynamoDB Stream and event mappings. It’s fun to have a guess which one will be retried and which one won’t.
For convenience, options.stdio may be one of the following strings:
‘pipe’ – equivalent to [‘pipe’, ‘pipe’, ‘pipe’] (the default) ‘ignore’ – equivalent to [‘ignore’, ‘ignore’, ‘ignore’] ‘inherit’ – equivalent to [process.stdin, process.stdout, process.stderr] or [0,1,2]