The API consumers will thank you for using them...
Thank you for mentioning our article Saurabh, appreciate it
Glad to share!
- Use HTTP 2 could increase a lot of performance.
- Warm up, sometimes services are slow starting.
- Payload compression
Thanks for the additional tips
People mostly implement read aside cache where the application is responsible for managing the state of
the caching layer. Is this correct ?
Yes...I've also seen the same thing.
Thanks for the shoutout, Saurabh!
Something I like about engineering is that you can optimize the end result for the customer in many different places of the system. That's why we need engineers who evaluate where to pay attention to!
Thanks🙌🏻, Connection pooling was something I wasn’t familiar with.
Thank you for mentioning our article Saurabh, appreciate it
Glad to share!
- Use HTTP 2 could increase a lot of performance.
- Warm up, sometimes services are slow starting.
- Payload compression
Thanks for the additional tips
People mostly implement read aside cache where the application is responsible for managing the state of
the caching layer. Is this correct ?
Yes...I've also seen the same thing.
Thanks for the shoutout, Saurabh!
Something I like about engineering is that you can optimize the end result for the customer in many different places of the system. That's why we need engineers who evaluate where to pay attention to!
Thanks🙌🏻, Connection pooling was something I wasn’t familiar with.