Skip to main content

REDIS

When somebody asks us to create a web application, the software requirements will be Apache, Mysql, PhP(LAMP where L stands for Linux). Imagine an application which stores data in main memory instead of disk, this will increase your application performance tremendously. One such application is Redis. Redis stores data on memory instead of disk and will periodically sync with the disks(if necessary).
Why Redis?:
  • Redis will be faster as it keeps data on memory. I read somewhere Memory is like disk and disk is like tape for redis.
  • Redis allows lot of data structures. Basically its a NOSQL database(http://en.wikipedia.org/wiki/NoSQL) . They dont support table or database schema we use traditionally. For them everything is key value pair as in hashmap. Redis allows a key to have values of types- string, set, sorted set, list, hashmap. To understand each data structure and the command they support, have a look at http://simonwillison.net/static/2010/redis-tutorial/
  • Lot of  web apps will be easier to code, as complex operations like sorting, union, aggregation can be done by redis itself
Do Redis follow ACID?
  • As of now, if redis server is crashed and data is not synced with the disk then consistency of data will be an issue
  • Redis server is a single threaded program, so no concurrency issues.
  • If you want a client to make a transaction, multi and exec commands in redis will take care of that. Unlike other databases there is no locking mechanisms involved during transaction. When a client performs exec, server wont get commands from other clients till all command queued for this transaction are done.
  • Single thread can reduce scalability of Redis. Redis supports slaves where a client can read from master and slaves but writes should first affect the master and then synced across the clients. So time consuming operations like sort can be moved to the slaves.
Some Cool Commands to Try Out:
  • BLPOP and BRPOP are some good operations that one always do on queues. Say I am waiting on a queue for a representative to pick up my call. So once a representative comes available, BLPOP will return the representative to the guy who waits for a longer time. No application logic is actually needed
  • Multi and Exec, they support transactions
Where To start?:
  • Install redis (apt-get or yum) or get a free redis instance at http://redis4you.com
  • Almost all languages support redis client coding(for Java download Jedis jar, for Ruby try redis-rb gem). For complete list check at http://redis.io
Start developing web apps without database if your data will fit in memory

Comments

Popular posts from this blog

How we have systematically improved the roads our packets travel to help data imports and exports flourish

This blog post is an account of how we have toiled over the years to improve the throughput of our interDC tunnels. I joined this company around 2012. We were scaling aggressively then. We quickly expanded to 4 DCs with a mixture of AWS and colocation. Our primary DC is connected to all these new DCs via IPSEC tunnels established from SRX. The SRX model we had, had an IPSEC throughput of 350Mbps. Around December 2015 we saturated the SRX. Buying SRX was an option on the table. Buying one with 2Gbps throughput would have cut the story short. The tech team didn't see it happening. I don't have an answer to the question, "Is it worth spending time in solving a problem if a solution is already available out of box?" This project helped us in improving our critical thinking and in experiencing the theoretical network fundamentals on live traffic, but also caused us quite a bit of fatigue due to management overhead. Cutting short the philosophy, lets jump to the story. ...

LXC and Host Crashes

 We had set up a bunch of lxc containers on two servers each with 16 core CPUs and 64 GB RAM(for reliability and loadbalancing). Both the servers are on same vlan. The servers need to have atleast one of their network interface in promiscuous mode so that it forwards all packets on vlan to the bridge( http://blogs.eskratch.com/2012/10/create-your-own-vms-i.html ) which takes care of the routing to containers. If the packets are not addressed to the containers, the bridge drops the packet. Having this setup, we moved all our platform maintenance services to these containers. They are fault tolerant as we used two host machines where each host machine has a replica of the containers on the other. The probability to crash for both the servers at the same time due to some hardware/software failure is less. But to my surprise both the servers are crashing exactly the same time with a mean life time 20 days. We had to wake up late nights(early mornings) to fix stuffs that go...

The FB outage

 This outage has caused considerable noise everywhere. It was quite discomforting for me because during the whole conversation nobody bothered to understand the gravity of the issue. I don't expect end users to understand the issue. But this is going to be a blogpost for all of those in the tech field, Such an event can happen how much ever chaos engineering, best of the tech jargon we implement in the stack To all my Site Reliability Engineer friends, Site Up is our first priority. I myself said many a times outage is news and SREs should prevent outage. But I'm afraid this is leading to a cult in the industry who despises outages and takes no learnings from it. I don't know what has happened in Facebook. I can explain a scenario which may or may not be right but that can definitely show the gravity of the issue. Let's draw a probable Facebook architecture Disclaimer I don't work at Facebook. So this might not be how facebook routes traffic. This is based on my exp...