1 / 9

Keepin it real (time) Cassandra in a real time bidding infrastructure

Keepin it real (time) Cassandra in a real time bidding infrastructure. What is real time bidding (RTB)?. a dynamic auction process where each impression is bid for in (near) real time Advantages are cost efficiency, higher performance and greater granularity with targeting and measurement.

ilya
Download Presentation

Keepin it real (time) Cassandra in a real time bidding infrastructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Keepin it real (time) Cassandra in a real time bidding infrastructure

  2. What is real time bidding (RTB)? • a dynamic auction process where each impression is bid for in (near) real time • Advantages are cost efficiency, higher performance and greater granularity with targeting and measurement. • http://www.advertisingperspectives.com/adblog/media-technology/are-ad-exchanges-and-real-time-bidding-the-next-big-thing/

  3. I'm more of a visual person...

  4. Where Cassandra lives • True 2-tier • Cassandra does caching • Cassandra does storage • AdServers talk to any node

  5. Requirements Low latency reads (exchanges have max request time) Low latency writes (record win for frequency capping) Other Information (bulk/back loaded) Large volumes of data ~ 10 TB (RF=3) NOT having 1 to 1 Disk/RAM Ratio Uptime (surviving node failures) :) Manageability/Usability

  6. Cassandra and writes Writes to sorted memtable (in memory) + commit Memtables flush periodically to Sstables (thresholds) Compacts SStables (thresholds) Results in 1-3 ms writes typical !Sweet! So all good right? Bulk load can pollute caches Model requires compaction (vs write in place)

  7. Cassandra and Reads SSTables are sorted by key (>1SStables Bloom filters) Two Cassandra caches KeyCache and RowCache VFS Cache + mmap (efficient for non cached items) Results in 3-10ms(avg) Reads !!That's nice!! (Borat voice) So its all good right ? more data = more ram | faster disk | more nodes Cache tuning for multiple Column Families is a moving problem

  8. Cassandra and Uptime Cassandra handles replication for you Multiple active nodes to serve reads and writes! Nodes get themselves back into sync HH and Read Repair Results in Minor failures may not even be visible on the client Restart without dealing with replication logs etc. So its all good right? Do see the occasional OOM Gossip protocol has turned into tabloid protocol

  9. NoSQL Adventure time

More Related