Duration 6:5
Top 7 Ways to 10x Your API Performance
Published 27 Jul 2023
Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter: https://bytebytego.ck.page/subscribe Animation tools: Adobe Illustrator and After Effects. Checkout our bestselling System Design Interview books: Volume 1: https://amzn.to/3Ou7gkd Volume 2: https://amzn.to/3HqGozy The digital version of System Design Interview books: https://bit.ly/3mlDSk9 ABOUT US: Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.
Category
Show more
Related videos for Top 7 Ways to 10x Your API Performance:
2. Connection Pool
3. Avoid N+1 Query pattern
4. Pagination
5. JSON Serialization
6. Compression
7. Asynchronous logging .. ...Expand 74
who does the video animation work for you? Kudos to the designer whoever he/she is. 24
to avoid waiting your frontend to parse the payload then query the comments, the use of 103 earlyhint can eliminate that waiting time.
using http/2 as it is using binary frames, multiplexing and solves hol blocking.
using http/3 as it speed up establishing the connecion api.
formats like protobuff also reduces the size of the payload.
to circumvent pipelining problems using http/1. 1, sometimes batch http request can be a solution (prefer standard specification) but please stay stateless as much as possible.
of course the infamous domain sharding
2. Putting the index 3. Adding load balance also helps to improve the performance.
4. Payload compression also can be helpful to fetch large size data like image/videos
1. Caching
2. Connection pool
3. Avoid 4. Pagination
5. Json serializers
6. Payload compression
7. Asynchronous logging
the lesson is, if production is reliant on secondary systems it communicates with, and youre going to be running production hot for hours, you must have secondary systems attached to your test suite! Wed 4 dozen attached but missed the mirror that was instrumental for reporting
- use http keep alive or http2 - if you do separate http call for each api call, speed will be slow. If you do http keep alive, - optimize sql queries:
- optimize sql queries:
- optimize sql queries:
- database replication
this allows things like of course we are using php not something like nodejs where processing after an api response is much easier
video is great. Thank you so much!
btw, could you tell me the software to create presentation slides like in the video? 2
thank you for the video.
1. Tuning the database connection pool size based on the application behaviour. Large number doesn' t always mean more performance) 2. Optimizing the sql query. Ensuring your most frequent queries end up using index scan instead of full table scan)
3. Not hopping between multiple microservices for a single user request. While a single user request can hit multiple services but those services should not in turn hit another set of services and so on)
4. Authorization data should be always cached.
5. As much as possible, do the most computation on the database layer. There' s a huge difference between doing the computation at application layer vs doing it at database layer
rest -gt; graphql. 2
eg. My program has more than 1. 5 lakh employees records in database and this data won' t get so is it good idea to publish json of individual employee on azure blob/s3 and than from api we can read from here and display in front-end.
i would like to know whether it will impact read performance for 1. 5 lakh json on azure blob
i am considering
5. Json serialization
which json library should been used?
does json libraries has really large difference in performance?
7. Asynchronous logging
dose logging method can improve api performance?
2- connection pool-
3- avoid n+1 query problem
4- pagination 5- lightweight json
6- compression.
7- asynchronous logging
does it mean - instead of sending the json / xml it is better to send as string?
reuse objects;
avoid unnecessary calculations;
question: why do people want to do pagination? " user interface has limited place to display data, so we only fetch what we needed. " is one explanation. Anything else?
1. Key pool for oauth operations:
- when you want to reduce the waste of individual overhead, that comes from the whole - by letting a dedicated component manage those pool for you, keep an eye that are always enough valid entries available. Based on the need the component can request a bigger amount of keys
- the life-cycle of that keys and be easily managed by storing them in a redis database with expire set, so it will get deleted when it' s expired also in the according api
contrary to last year i optimized a specificaway by moving its(nearly nothing really useful) to the client. Decreased latency of the whole feature by 80% and decreased total loc.
always try to localize operations or data if your goal is speed and efficiency