Playlist · 5 videos · 33 min
Performance: caching, indexes and Rust
Fast by default: automatic caching in Redis, Index Maker and automatic indexes for slow queries, API Maker measured live on a five dollar server, and more servers behind one address when one is not enough.
The videos of this playlist
4:511. CachingAutomatic API Caching with Redis: One Setting, Under a Millisecond
Some reads make the database do the same work again and again. One setting keeps their answers in Redis, a write drops them on its own, and a read of a table of a million rows answers in under a millisecond. See the cache key, resets from code and headers, and caching for custom APIs.
8:492. Index MakerIndex Maker: Find Slow Queries and Create the Right Index, 6 Databases
Index Maker watches the database queries of your APIs, tells you which ones read a whole table, and gives them the right index, on six database engines. Follow one slow API on a table of a million order events: one run of its custom API in API Testing, a scanning period, query shapes, one verdict on six engines, suggestions ranked by cost, the index form, and the same call fast again.
8:143. Automatic indexesAutomatic Indexes: Index Maker Indexes Your Database on Its Own
Indexes that find themselves: recorded, decided, written down with a reason, and created in every environment. Turn on the automatic mode of Index Maker, watch its first decision with a reason for every query, then carry its decisions to every environment with the am_index_maker migration script and the index system APIs.
4:574. Why RustWhy Rust: API Maker Load-Tested Live on a $5 Server
API Maker is written in Rust. Put it on the smallest server Linode sells, five dollars a month, and load it live: 1,900 requests a second from MongoDB, 9,100 from the cache, memory flat at about 51 MB, and a restart in about a tenth of a second.
6:265. Scale outScale Out a Backend: Many API Maker Servers Behind One Load Balancer
Two API Maker servers on the same MongoDB and Redis, behind Caddy: any server answers any call, a save is live on every server at once, WebSocket clients are told whichever server holds them, each scheduler runs once, and a server which stops hands over its clients and schedulers. Shown live, with two servers.