<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vikram Sahu on Medium]]></title>
        <description><![CDATA[Stories by Vikram Sahu on Medium]]></description>
        <link>https://medium.com/@ivikramsahu?source=rss-a31ee7494d56------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rLrJ5cqhPG9qjY3UQNarPA.png</url>
            <title>Stories by Vikram Sahu on Medium</title>
            <link>https://medium.com/@ivikramsahu?source=rss-a31ee7494d56------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:06:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ivikramsahu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[REDIS —Lighting fast NoSQL (Part 1)]]></title>
            <link>https://faun.pub/redis-lighting-fast-nosql-part-1-c24d5af4dea5?source=rss-a31ee7494d56------2</link>
            <guid isPermaLink="false">https://medium.com/p/c24d5af4dea5</guid>
            <category><![CDATA[ansi]]></category>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[message-broker]]></category>
            <category><![CDATA[nosql]]></category>
            <category><![CDATA[c]]></category>
            <dc:creator><![CDATA[Vikram Sahu]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 14:26:57 GMT</pubDate>
            <atom:updated>2020-01-08T06:49:19.315Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*eY1p2hHFUz9V8LxqtPVDlg.png" /></figure><p>It’s been quite a while I am using Redis, it is the lighting-fast NoSQL in-memory database among other databases which also supports disk storage for persistence. Since its a personal experience with Redis, I will try to keep things practical and more hands-on so that it is clear, understandable, and interesting.</p><p>Redis being an extensive topic I will divide into chunks which are as follows :</p><h4>Part 1</h4><ol><li>Introduction</li><li>When to use Redis?</li><li>Who are using Redis?</li><li>Installation</li></ol><h4>Part 2</h4><ol><li>Introduction to Data type &amp; abstraction</li><li>Diving deep into data structure<br>a. Strings<br>b. Hashes<br>c. Lists<br>d. Sets<br>e. Sorted sets</li><li>Performance metrics.</li></ol><h4>Part 3</h4><p>Redis modules …</p><h3>Introduction</h3><p><strong>Redis</strong> is an Open Source technology having more than 40,000+ stars on GitHub, used by most known organizations like Twitter, GitHub, Snap chat, Flickr and many more. Due to speed and data-structure stores, it has become the most loved NoSQL database among developers.</p><p>It has a wide range of data-structure in its store including strings, hashes, sets, sorted sets, etc and capabilities can be extended to implement many more advance data structures also.</p><h4>If you Ask me how It feel to have Redis ?</h4><p>i would be like …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*_d-1mnYUGcq7IgYAl9LopA.gif" /></figure><p><strong>Why?</strong> here are some facts about Redis.</p><ol><li><strong>High Performance: </strong>Its in-memory nature gives great stability, performance. The Commitment from REDIS maintainers are to keep the source code optimized with minimized complexities.</li><li><strong>Lightweight without any external dependencies:</strong> Written in ANSI C and no external dependencies. Works great with POSIX environment ie. Linux, Mac OS, *BSD. For windows, there are less support but yes you can get <strong>.exe</strong> which is for an experimental purpose.</li><li><strong>High Availability</strong> — It has asynchronous, non-blocking, master/slave replication to ensure high availability of data these are provided built-in by Redis.</li></ol><h3>When to use Redis ?</h3><p>It is always confusing to choose stack, every technology has its advantages and limitations but choosing the right stack at the right time is what we can say having a cherry on the cake.</p><blockquote>REDIS is a master of reading and writing cache.</blockquote><p>REDIS fits as the best option if you looking for one of the things mentioned below :</p><ol><li>Caching system which can handle millions of transaction at a single instance.</li><li>Planning for building pub/sub mechanism.</li><li>Queues.</li><li>Counters (these can be any real-time increment data that changes on every action. This is atomic that means if there are 2 increment command triggered at the same time it will be executed sequentially. for example, if there is a key name:: burgers with value:: 1; if two increment updates are given at the same time the value will be 3 not 2).</li></ol><h3>Who are using Redis ?</h3><p>We will consider 3 different and famous organization who are using REDIS with scale for 3 different scenarios. Everyone has there own use case and implementation where REDIS is playing an vital role.</p><p>🐦 <strong>Twitter</strong> : when someone likes, retweet or tag you on twitter how fast is that maybe some milliseconds. By deploying a massive Redis cluster twitter as been scaling its user’s timelines about 800 recent timelines are stored using Redis’s list data structure.<br>You can listen to the <a href="https://www.infoq.com/presentations/Twitter-Timeline-Scalability/">presentation here</a>.</p><p>🐙 <strong>GitHub </strong>:It was among the earlier adopters, using REDIS GitHub developed and open-sourced Resque which helps for the execution of backend jobs using queues. Not only this but Github has used made faster using Redis.</p><p>you can find out <a href="https://github.blog/2009-10-20-how-we-made-github-fast/">here</a>.</p><p>📚 <strong>Stack overflow </strong>: Whether its a StackExchange, StackOverflow or their sister companies. These guys are open to sharing each and everything about their tech stack similarly when it comes to caching, They cache everything and that to aggressively.</p><p>you can check <a href="http://highscalability.com/blog/2014/7/21/stackoverflow-update-560m-pageviews-a-month-25-servers-and-i.html">here</a> how StackOverflow manages 560M page views a month.</p><p>and with more depth <a href="https://meta.stackexchange.com/questions/69164/does-stack-exchange-use-caching-and-if-so-how/69172#69172">here</a></p><blockquote>There are list of such use cases with <a href="https://redis.io/topics/whos-using-redis">different scenarios</a>.</blockquote><h3>Installation</h3><p>Since, it is primary developed for POSIX environment we can installed directly from their official repositories.</p><h4><strong>1. Installing REDIS on Ubuntu (18.04)</strong></h4><pre>sudo apt update<br>sudo apt install redis-server</pre><p>Since, we are running Redis on Ubuntu and Ubuntu uses supervised directive as <strong>systemd init system</strong> we need to make changes in Redis config file. Open below file with your favourite editor( i am using vim here)</p><pre>sudo vim /etc/redis/redis.conf</pre><p>Check for <strong>supervised</strong> option which will be by default “<strong>no</strong>” change it <strong>systemd</strong></p><pre># If you run Redis from upstart or systemd, Redis can interact with your<br># supervision tree. Options:<br>#   supervised no      - no supervision interaction<br>#   supervised upstart - signal upstart by putting Redis into SIGSTOP mode<br>#   supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET<br>#   supervised auto    - detect upstart or systemd method based on<br>#                        UPSTART_JOB or NOTIFY_SOCKET environment variables<br># Note: these supervision methods only signal &quot;process is ready.&quot;<br>#       They do not enable continuous liveness pings back to your supervisor.<br>supervised systemd</pre><p>Save and close the file. Restart the service and check for status.</p><pre>sudo systemctl restart redis.service &amp;&amp; systemctl status redis</pre><p>output should be :</p><pre>[root@localhost ~]# sudo systemctl restart redis.service &amp;&amp; systemctl status redis<br>● redis.service - Redis persistent key-value database<br>   Loaded: loaded (/usr/lib/systemd/system/redis.service; disabled; vendor preset: disabled)<br>  Drop-In: /etc/systemd/system/redis.service.d<br>           └─limit.conf<br>   Active: active (running) since Mon 2020-01-06 17:52:26 IST; 20ms ago<br>  Process: 9426 ExecStop=/usr/libexec/redis-shutdown (code=exited, status=0/SUCCESS)<br> Main PID: 9441 (redis-server)<br>    Tasks: 4 (limit: 26213)<br>   Memory: 6.6M<br>   CGroup: /system.slice/redis.service<br>           └─9441 /usr/bin/redis-server 127.0.0.1:6379</pre><pre>Jan 06 17:52:26 localhost.localdomain systemd[1]: Starting Redis persistent key-value database...<br>Jan 06 17:52:26 localhost.localdomain systemd[1]: Started Redis persistent key-value database.</pre><h4><strong>2. Installing REDIS on CentOS</strong></h4><p>Add EPEL repository and update YUM to confirm the changes</p><pre>sudo yum install epel-release<br>sudo yum update</pre><p>Install REDIS from yum</p><pre>sudo yum install redis</pre><p>Start redis</p><pre>sudo systemctl start redis &amp;&amp; &amp;&amp; systemctl status redis</pre><p>output should be :</p><pre>[root@localhost ~]# sudo systemctl restart redis.service &amp;&amp; systemctl status redis<br>● redis.service - Redis persistent key-value database<br>   Loaded: loaded (/usr/lib/systemd/system/redis.service; disabled; vendor preset: disabled)<br>  Drop-In: /etc/systemd/system/redis.service.d<br>           └─limit.conf<br>   Active: active (running) since Mon 2020-01-06 17:52:26 IST; 20ms ago<br>  Process: 9426 ExecStop=/usr/libexec/redis-shutdown (code=exited, status=0/SUCCESS)<br> Main PID: 9441 (redis-server)<br>    Tasks: 4 (limit: 26213)<br>   Memory: 6.6M<br>   CGroup: /system.slice/redis.service<br>           └─9441 /usr/bin/redis-server 127.0.0.1:6379</pre><pre>Jan 06 17:52:26 localhost.localdomain systemd[1]: Starting Redis persistent key-value database...<br>Jan 06 17:52:26 localhost.localdomain systemd[1]: Started Redis persistent key-value database.</pre><h4><strong>3. Installing REDIS on Fedora</strong></h4><pre>sudo dnf -y install redis</pre><pre>sudo systemctl start redis &amp;&amp; systemctl status redis</pre><p>Output will be same as CentOS and Ubuntu.</p><h4><strong>4. Mac OS</strong></h4><p>You can find this cool posts for <a href="https://medium.com/@petehouston/install-and-config-redis-on-mac-os-x-via-homebrew-eb8df9a4f298">installation on Mac</a> by <a href="https://medium.com/u/a941a33b8427">Pete Houston</a></p><p><strong>OR</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/87f0dc67d4b1434784e9c3945a4d58a6/href">https://medium.com/media/87f0dc67d4b1434784e9c3945a4d58a6/href</a></iframe><h4><strong>5. Windows</strong></h4><p>You can find the MSI and ZIP version of Redis on its official <a href="https://github.com/microsoftarchive/redis/releases/tag/win-3.0.504"><strong><em>GitHub</em></strong></a><strong> </strong>release.</p><p>Also there are step by step instruction for running <a href="https://redislabs.com/blog/redis-on-windows-8-1-and-previous-versions/"><strong><em>Redis on windows</em></strong></a></p><h3>Conclusion</h3><p>REDIS has been one of the fastest and stable NoSQL database, it has been used overall type of organization. No matter what kind of business it can be used with easy on platforms like eCommerce, Social Media, Developer platforms and many more.</p><p>Hope this post helped you understand the concept of Redis and use cases where it can be used. Stay tuned for PART 2 which will emphasis the inbuilt data structure of REDIS.</p><p>Thank You 😃</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/0*Piks8Tu6xUYpF4DU" /></figure><p><strong>Follow us on </strong><a href="https://twitter.com/joinfaun"><strong>Twitter</strong></a><strong> </strong>🐦<strong> and </strong><a href="https://www.facebook.com/faun.dev/"><strong>Facebook</strong></a><strong> </strong>👥<strong> and </strong><a href="https://instagram.com/fauncommunity/"><strong>Instagram</strong></a><strong> </strong>📷 <strong>and join our </strong><a href="https://www.facebook.com/groups/364904580892967/"><strong>Facebook</strong></a><strong> and </strong><a href="https://www.linkedin.com/company/faundev"><strong>Linkedin</strong></a><strong> Groups </strong>💬<strong>.</strong></p><p><strong>To join our community Slack team chat </strong>🗣️ <strong>read our weekly Faun topics </strong>🗞️,<strong> and connect with the community </strong>📣<strong> click here⬇</strong></p><figure><a href="https://www.faun.dev/join/?utm_source=medium.com%2Ffaun&amp;utm_medium=medium&amp;utm_campaign=faunmediumbanner"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6P3WpLjGv5v1ucm5dgkucg.png" /></a></figure><h4>If this post was helpful, please click the clap 👏 button below a few times to show your support for the author! ⬇</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c24d5af4dea5" width="1" height="1" alt=""><hr><p><a href="https://faun.pub/redis-lighting-fast-nosql-part-1-c24d5af4dea5">REDIS —Lighting fast NoSQL (Part 1)</a> was originally published in <a href="https://faun.pub/">FAUN.dev() 🐾</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jenkins: Dev-Ops Saviour]]></title>
            <link>https://faun.pub/jenkins-dev-ops-saviour-d5e32d5f352?source=rss-a31ee7494d56------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5e32d5f352</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Vikram Sahu]]></dc:creator>
            <pubDate>Thu, 29 Nov 2018 07:34:17 GMT</pubDate>
            <atom:updated>2019-07-17T16:00:43.338Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oepEy8UlfmQM6a2iCHMVQA.png" /><figcaption>Jenkins</figcaption></figure><blockquote>Jenkins a mighty sword for Dev-Ops Engineer.</blockquote><p>We all know <a href="https://aws.amazon.com/devops/what-is-devops/">Dev-Ops</a> is evolving very fast and making it powerful yet vital slots for all Linux lovers who not only love to code but like to automate things in a unique way. Similarly, in this cruel world of AI, the Automation is must due to which developers can seamlessly deploy their code without any worry of making it live on production.</p><p>Dev-Ops without tools is helpless for automation. In order to make these things seamless and smooth tools such as Jenkins, Docker, Git, Nagios (&amp; Icinga), etc. are introduced.</p><h3>All about Jenkins</h3><blockquote><strong>defination</strong> : Jenkins is automation tool written Java programming language which helps you to set an environment of continuous integration or delivery for almost all type of combination of languages and source code repositories by using the pipeline, as well as you can also automate other routine development tasks.</blockquote><blockquote><strong>Simplified</strong>: Handy automation tool use for continuous deployment of your project which supports muliple testing and deployment plugins/technologies.</blockquote><p><strong>Usage</strong>:<br>1. To build and test software projects with multiple test cases without any manual intervention. <br>2. This makes easier for developers to integrate new changes and obtain a fresh build of the project. <br>3. It also has the functionality of integrating a large number of testing and deployment technologies.</p><p>The software development process has taken apace in many organizations due to Jenkins. All kind of development life-cycle processes can be integrated using Jenkins such as creating build, document, test, package, stage, static analysis and much more.</p><h3>What makes Jenkins better than any other automation tool?</h3><p>1. <strong>Adoption</strong>: Jenkins as over 1 million users around the world with 1,50,000 active installations. <br>2.<strong> Plugins</strong>: As 1000+ plugins and allows integrating with most of the development, testing and deployment tools.</p><h3>Advantages</h3><ol><li>It is very <a href="https://jenkins.io/doc/book/installing">easy to install and start with service</a>.</li><li>It is an open source tool means you can avail totally free of cost with great community support.</li><li>It has 1000+ plugins which make easy to work.</li><li>Build in Java so easily portable to any major platform.</li></ol><h3>Playing with Continuous Integration</h3><p>Whenever a new project use to be assigned I had two question in my mind</p><ol><li>How will I deploy the project once it is done? 🙍</li><li>Will I be able to spend enough time to make my code bug free what if bugs start popping out, will I be debugging complete codebase? 😕</li></ol><p>After spending ample time I came to a resolution which comes out to great for me that is Continuous Integration.</p><p>There was a scenario where we all developer use to start with a project and deploy on the test server for testing. which is the perfect way of software development, but what about the imperfections in the project?</p><p>For example(let&#39;s give this list of bug a name as a <strong><em>caterpillar 🐛</em></strong>)</p><ol><li>we use to wait unless the test result is ready by QA.</li><li>Possibilities of bugs in the project, which might turn out to be tough because we don’t know the exact commit where actual bug is so we use to debug the complete codebase to find out the single bug. ridiculous 😠 isn’t it?</li><li>Project delivery process was delayed.</li><li>Recursive feedback regarding code quality, build, an architecture of the project was missed.</li><li>Due to Manual procedure risk of project failure was increased.</li></ol><p>So we implement the generic flow of Jenkins which was simple yet powerful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/1*QB5DWQgbENiKqgA1iWXsDg.gif" /><figcaption>Jenkins - generic flow</figcaption></figure><p>How did this work for us?</p><ol><li>Once we have committed the code to the source code repository. Meanwhile, the Jenkins server checks the repository at regular intervals for changes.</li><li>Jenkins pulls the changes which have been made in the source code repository and start preparing fresh build.</li><li>If the build is successful it will start deploying on the test server.</li><li>If the build fails it will be notified by various ways either by mail or ping on slack, etc.</li><li>Once testing is done, Jenkins generates reports which can be given to developers about their build and result.</li></ol><p><strong>Are we successful in removing caterpillar from our project?</strong></p><blockquote>of course “<strong>YES..</strong>”</blockquote><ol><li>Waiting time for the result was totally discarded: now we know the better result for every commit and failure no need to wait for the QA to point out bugs.</li><li>Debugging complete source code was discarded: On every commit, build is made if it fails we were notified at that point in time.</li><li>Development process accelerated due to the reduction of waiting and debugging time.</li></ol><p><strong>What&#39;s next?</strong></p><blockquote>Will be coming soon with the next blog on getting notified for build status ✔️</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/0*Piks8Tu6xUYpF4DU" /></figure><p><strong>Join our community Slack and read our weekly Faun topics ⬇</strong></p><figure><a href="https://www.faun.dev/join/?utm_source=medium.com%2Ffaun&amp;utm_medium=medium&amp;utm_campaign=faunmediumbanner"><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oSdFkACJxs5iy1oR" /></a></figure><h4>If this post was helpful, please click the clap 👏 button below a few times to show your support for the author! ⬇</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5e32d5f352" width="1" height="1" alt=""><hr><p><a href="https://faun.pub/jenkins-dev-ops-saviour-d5e32d5f352">Jenkins: Dev-Ops Saviour</a> was originally published in <a href="https://faun.pub/">FAUN.dev() 🐾</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>