Your SlideShare is downloading. ×
0
Redis
Redis
Redis
Redis
Redis
Redis
Redis
Redis
Redis
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Redis

101

Published on

This presentation is not related with any company or individual.

This presentation is not related with any company or individual.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
101
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Remote Dictionary Service
  • All Stats are theoretically.
  • 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

    ×