Redis
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Redis

on

  • 127 views

This presentation is not related with any company or individual.

This presentation is not related with any company or individual.

Statistics

Views

Total Views
127
Views on SlideShare
127
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Remote Dictionary Service
  • All Stats are theoretically.

Redis Presentation Transcript

  • 1. Mr. Kishor B. Parkhe M. Tech. (Mathematics)
  • 2. Feature Of Redis  Read – fast  Write – faster  Number Of Set operation – 100000 per seconds  Bulk Insertion  Use REST API  Atomicity  Transaction like Rollback  Able to process 32k-40k requests per second
  • 3. Data Structure  Hash – different than MongoDB, CouchBase  List – Queues, Stack  Set – All set Operation  Blocking Queues  Expiry Mechanism for Cache
  • 4. Redis Cluster Managements  Simple to Configured  Durability  Snapshots  Priority to store  Master Slave Relation
  • 5. Redis Cache Service Master Request Response Application Server 1 Slave 1 Application Server 3 Application Server 2 Application Server 4 Slave 2 Redis Distributed Cluster Cache Service Users
  • 6. Weakness of Redis  Loss of data  Redis does not Support larger datasets than RAM
  • 7. Conclusion  Suitable for cache if RAM is not issue.  Distributed and Centralizes as service.  Better than Mem-cache.  Infrastructure will not commodity hardware.  Near Real Time Cache.
  • 8. Stats  Number inquiry in Minute= 900  Recall size= 4000 per inquiry (worse case)  Inquiries per second= 15  Number of request for Redis= 15 * 4000 (worse case)  Number of request for Redis= 60k  Time Ratio= 3:2
  • 9. Thanks