<?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 Vishnu ks on Medium]]></title>
        <description><![CDATA[Stories by Vishnu ks on Medium]]></description>
        <link>https://medium.com/@iamvishnuks?source=rss-6d9a2cd85ded------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*0aEiDh6lKG4Y9w0VVj_GvQ.jpeg</url>
            <title>Stories by Vishnu ks on Medium</title>
            <link>https://medium.com/@iamvishnuks?source=rss-6d9a2cd85ded------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:04:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iamvishnuks/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[Xmigrate beta_v0.3.0 released]]></title>
            <link>https://medium.com/xmigrateoss/xmigrate-release-bb244075a011?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb244075a011</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Sat, 26 Mar 2022 19:08:50 GMT</pubDate>
            <atom:updated>2022-03-26T19:08:50.729Z</atom:updated>
            <content:encoded><![CDATA[<h4>xmigrate beta_v0.3.0 released with UI/UX enhancements and removal external mongodb dependency</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hL3bUSgpvem4_Tl1nt9OHw.png" /></figure><p>We are happy to announce the release of xmigrate beta_v0.3.0. This release is now available for all the Cloud and DevOps engineers to try out.</p><blockquote>Also please note that we are still in beta and if you wish to migrate your production workloads then please take a full backup and create a new server out of it. Then try to migrate that server.</blockquote><h3>Removing public mongodb dependency</h3><p>We needed a public/private mongodb for updating metadata and disk cloning status directly from the source server to the database. We are now changing this approach by passing a call back URL to the source server. The source server then use the call back URL to update the status and source server metadata.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HBQR6jO4LeJTWbTM" /></figure><h3>UIUX Enhancement</h3><p>We improved a lot with respect to UI and UX in this release,</p><ul><li>Fixed some of the UX glitches like user being able to press clone, convert, build buttons from the console even they have pressed that button already.</li><li>We are now showing a loader while an action(clone, convert, build) is progressing</li><li>Added toasts when an action is completed for a server</li><li>Re-enable the action button when it fails. For eg, convert button will get enabled when disk conversion fails</li></ul><h3>Support for more OS</h3><p>We added support for Ubuntu 18.04, CentOS7, CentOS8 and Red hat 7 in this release. Now the OS compatibility matrix looks like this,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*PaFwlHOwZ9v347UAGKBvLw.png" /></figure><p>Yes, we are getting there, from MVP to enterprise opensource software. We welcome you to be part of this adventure.</p><p>Thank you!!</p><p><a href="https://github.com/xmigrate/xmigrate/tree/main">GitHub - xmigrate/xmigrate: Cloud migration tool for migrating on premise data and infrastructure to cloud</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb244075a011" width="1" height="1" alt=""><hr><p><a href="https://medium.com/xmigrateoss/xmigrate-release-bb244075a011">Xmigrate beta_v0.3.0 released</a> was originally published in <a href="https://medium.com/xmigrateoss">xmigrate</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrate your VM’s from AWS to Azure using xmigrate]]></title>
            <link>https://medium.com/xmigrateoss/migrate-your-vms-from-aws-to-azure-using-xmigrate-6e9ab5ce8114?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e9ab5ce8114</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Mon, 11 Jan 2021 15:45:09 GMT</pubDate>
            <atom:updated>2021-01-11T15:45:09.831Z</atom:updated>
            <content:encoded><![CDATA[<p>Migrating a server from AWS to Azure is not difficult or costly anymore. Let me tell you how.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ptAzubJED5rV3YQebE6LgA.png" /></figure><h4>Let’s start by setting up xmigrate in our laptop</h4><p><strong>Pre-requisites</strong></p><ul><li>You should create a free account in <a href="https://cloud.mongodb.com/">https://cloud.mongodb.com/</a></li><li>Next step is to create a database named migration with user and password from Mongo atlas console</li><li>You should have installed docker in your laptop</li><li>There should be connectivity between the server you want to migrate and your laptop</li><li>One user should be created/available with sudo privileges in the server which needs to be migrated</li><li>Currently, xmigrate only supports servers with OS Ubuntu 18.04 to moved to azure</li></ul><p><strong>Setting up</strong></p><ol><li>Let&#39;s start the xmigrate application by running below command, make sure to replace the database URL with your connection URL</li></ol><pre>docker run -p 8080:80 --name xmigrate -e MONGO_DB=&quot;mongodb+srv://username:<a href="/service/mailto:mygratyon123@xmigrate.ao93h.mongodb.net">password@xmigrate.ao93h.mongodb.net</a>/migration?retryWrites=true&amp;w=majority&quot; xmigrate</pre><p>2. Open the browser and go to <a href="http://localhost:8080/">http://localhost:8080</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NL1gW6LCWuIPEX8ozrk1Qg.png" /></figure><p>3. Click on signup and create an account by entering username and password</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3UCsCPrSI8xQzC2c5njBYw.png" /></figure><p>4. Now you will be redirected to the login page. Use the credentials of username and password created in the previous step to login</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5cuj0-6cVSodgQhieEidDA.png" /></figure><p>5. Next step is to create a project. Give a project name and select the cloud provider which you want to migrate your infrastructure, in our case it’s azure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y9NzrWE6vTiyu2eKmVsLKg.png" /></figure><p>6. After clicking on the Azure cloud logo, you have to enter the service principal credentials for your cloud account</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wH_7I7BY4WC9rQl1JOy5vQ.png" /></figure><p>7. If the credentials are correct, xmigrate will ask to select the location(azure region) and a resource group name(which is not present in your azure account). Click on create project button after giving the details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*18WhfME2Sp4pbt8GSp0tpw.png" /></figure><p>8. Enter the storage account, container name and access key and click on save. This is to copy and store your VM image temporarily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oSq88O_Jy3W6kv7FxuJMZA.png" /></figure><p>9. Then select `azuretestmigration` which you just created from project navigation dropdown at the top left side of the portal and click on Discovery from the left sidebar menu</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UQyB4AzYE6CyMvDzrjibKg.png" /></figure><p>10. Now you will be in discovery dashboard. Enter the IP, username and password for the Linux server you want to migrate and click on submit button and wait till Go to Blueprint button enables</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CTqBUY7u6UgS1wAnuW7inA.png" /></figure><p>11. Now navigate to Blueprint dashboard by clicking on Go to Blueprint button</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pGo94oozjqFrUQQar8NS4Q.png" /></figure><p>12. Here you can see some pieces of information regarding the server. Scroll down and create the network, here Azure Vnet by giving a name and valid CIDR and then clicking on Create Network button</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sB1QuVxGy2SKooa-gStTfw.png" /></figure><p>13. Click on the row with the network details to create a subnet by providing a name, a valid CIDR within Vnet CIDR range and the type, either public or private and click on Create Subnet</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CuXE0pZBfqqD8wwDvGqwBg.png" /></figure><p>14. Once you created the subnet, the server details will be automatically populated inside the subnet table. Now you have to choose a VM type from the dropdown and then save the blueprint by pressing the save button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elQiUWUu8BZLtS8RRKPdTQ.png" /></figure><p>15. Finally, you can click on the build button to start the migration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_q0CRUpAuqY768ppC9Jlw.png" /></figure><p>Once you have completed the above steps wait until the status becomes 100.</p><p>When it becomes 100, login to your Azure account and look for the VM inside the resource group with name xmigrate. Copy the public IP address and try to ssh into it using the default username and password, xmigrate and Xmigrate@13.</p><blockquote>Note: There will be a provision to add a custom username and password for VM’s in future release</blockquote><p>Thanks for reading and happy migrate!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e9ab5ce8114" width="1" height="1" alt=""><hr><p><a href="https://medium.com/xmigrateoss/migrate-your-vms-from-aws-to-azure-using-xmigrate-6e9ab5ce8114">Migrate your VM’s from AWS to Azure using xmigrate</a> was originally published in <a href="https://medium.com/xmigrateoss">xmigrate</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Xmigrate Explained]]></title>
            <link>https://medium.com/xmigrateoss/xmigrate-explained-cf019418df1b?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf019418df1b</guid>
            <category><![CDATA[xmigrate]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Fri, 01 Jan 2021 17:59:23 GMT</pubDate>
            <atom:updated>2021-01-06T13:57:11.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nVf-7T668cEuuhvDTj0DbQ.png" /></figure><p>Xmigrate is an opensource cloud migration project. Xmigrate aims to achieve the portability of VM’s across any public cloud. If you look at the case of containers, it’s famous for its portability. Once a container image is built, it can run on any K8s cluster, EKS, AKS, GKE, Openshift etc. No matter who is the vendor.</p><h4>What problem we are solving?</h4><p>A VM which you create in the public cloud will have tight integrations to the underlying hardware. And all the vendors use different virtualization technology. They have their own tools for doing the assessment and migration. None of them comes for free and supports migration to all clouds, each vendor’s tool only supports migration/assessment of servers or applications which needs to be migrated to their cloud.</p><blockquote>Xmigrate aims to help you to move your server, which is deployed in any X environment to Y public cloud platform. Here X can be on-prem or public cloud vendors like AWS, Azure, GCP etc and Y can be a public cloud platform.</blockquote><h4>How does it work?</h4><p>All the public cloud providers provide functionalities to import the image of a server, either in RAW, VMDK or in VHD format. Also, each vendor has some pre-requisites, to install some packages, update the kernel etc before creating the server image. Xmigrate does everything for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bzds1wiYW05Rlqa07NVC_Q.png" /></figure><ol><li>Run xmigrate application on your laptop or a server which has connectivity to the VM which needs to be migrated and to the cloud environment which the VM is getting migrated</li><li>Xmigrate stores all the metadata and other information to MongoDB</li><li>Xmigrate connects to the VM which needs to be migrated and prepare it with the required pre-requisites</li><li>Once the pre-requisites are met, xmigrate push the image in RAW format to AWS S3 bucket directly from the VM</li><li>Xmigrate triggers AMI creation by calling AWS import-image API after the image is fully uploaded</li><li>Then xmigrate will make AWS API calls to build the network components</li><li>And finally, xmigrate call AWS API’s to create an instance from the AMI created in the 5th step</li></ol><h4>The tech stack</h4><p>Things are easier if we look at a problem as a group of many small problems. That’s how we made this solution. We didn’t make any inventions but stitched together multiple technologies/tools to work together to solve the problem holistically. Below are the underlying tools and technologies we used,</p><ol><li>Ansible: To prepare and create RAW image of the server which needs to be migrated</li><li>Python: All the REST API’s are written in python3.7 with Quart framework and async support</li><li>MongoDB: It stores all the metadata about servers, details of users, projects etc</li><li>ReactJS: xmigrate dashboard is built with ReactJS</li></ol><h4>Things need to be done</h4><p>There are many more things to be completed and tested to call xmigrate a production-ready software.</p><ol><li>Multiple OS flavours need to be supported</li><li>Migration of VM’s with multiple disks</li><li>Migration of VM’s to GCP</li><li>Management of cloud resources created with xmigrate</li><li>Bandwidth control during the migration process</li></ol><p>Even though there are many things to be completed to make it a finished product, we have done the public announcement. It’s not for you to start using xmigrate, but to start contributing to xmigrate.</p><h4>How you can contribute to xmigrate?</h4><p>If you are a <strong>DevOps</strong> specialist who is really good at writing Ansible playbooks, you can contribute to xmigrate by writing playbooks to prepare and migrate the server by installing the packages and making other pre-requisites.</p><p>If you are a <strong>Python developer</strong>, if you find any bugs or issues either by yourself or reported by someone, please be happy to fix it and make a PR.</p><p>If you are <strong>Frontend Developer</strong> skilled in ReactJS, please create a PR which improves the UI/UX of xmigrate.</p><p>So let’s start contributing to xmigrate and make it a wonderful OSS.</p><p>Once again thanks to everyone for reading and supporting us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf019418df1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/xmigrateoss/xmigrate-explained-cf019418df1b">Xmigrate Explained</a> was originally published in <a href="https://medium.com/xmigrateoss">xmigrate</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How and Why to load test your logging environment???]]></title>
            <link>https://medium.com/techietalks/how-and-why-to-load-test-your-logging-environment-fe1c3131254b?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe1c3131254b</guid>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[logstash]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Tue, 24 Nov 2020 16:54:50 GMT</pubDate>
            <atom:updated>2020-11-24T16:54:50.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kEa432gXOdiKMXkFc6sE3Q.png" /></figure><p>Are you looking for a perfect solution to load test or performance test your logging environment with/without any 3rd party tools? This article is especially for you and you only!!</p><p>In my logging environment, I have Logstash installed on our application servers to send logs to Kafka. From Kafka, we have several Logstash servers consuming logs and do some sort of filtering and then, logstash write logs to multiple indexes on Elasticsearch depending on the tags present in the logs.</p><p>Before onboarding the application logs to our freshly created logging environment, I wanted to perform/simulate a load test with actual log data. My objectives for this experiments is to understand below factors,</p><ul><li>Maximum index rate which can be achieved in Elasticsearch</li><li>How well the Logstash events receive rate and events emit rate can be tuned by adjusting JVM options, pipeline workers, batch size and by optimising nested parsing steps in Logstash pipeline configuration</li><li>To understand how well our Kafka handle log spikes and tweak the number of partitions</li><li>To understand the network throughput and bandwidth consumption by each component</li></ul><h3>Let’s begin!</h3><p>To perform this load test, you should have created and tested connectivity between Kafka, Logstash, Elasticsearch and Kibana. This load test consists of below steps</p><ul><li>Data preparation</li><li>Creating a Kafka topic with <strong>n</strong> number of partitions</li><li>Creating Elasticsearch index with <strong>n</strong> number of shards</li><li>Start generating load in Kafka</li><li>Tweak the parameters and repeat from step 2</li></ul><p>The <strong>n</strong> number which mentioned above can be tweaked along with the experiment. You can start with small numbers and can find the optimum <strong>n</strong> value. Beware! <strong>n</strong> values are always smaller in most of the cases and as the value increase, complexity also increases. So be cautious while playing with it. You should also have enabled the logstash monitoring option with elasticsearch and kibana.</p><h4>Step1: Data preparation</h4><blockquote>TL;DR: If you have already created the payload file somehow. Skip to the next step.</blockquote><p>For preparing the payload for the load testing, I logged into our application server and downloaded all application log files to my test Linux server.</p><p>After that, I copied the logstash configuration from that application server, which is used to send logs to our test logging environment. Then I changed all the input file path patterns to match with the file path of log files I downloaded locally. Also, I edited the output configuration to use file output plugin to write the formatted logs to a file, named <em>payload.json</em>.</p><h4>Step2: Creating Kafka topic with <strong>n</strong> number of partitions</h4><p>Create the Kafka topic by executing the following command</p><pre>/opt/kafka/current/bin/kafka-topics.sh --bootstrap-server yourkafkabtoker:9092 --create --topic loadtest --partitions 10 --replication-factor 1</pre><p>After creating the topic you can verify whether the topic is created or not by executing below command</p><pre>/opt/kafka/current/bin/kafka-topics.sh --bootstrap-server yourkafkabroker:9092 --describe --topic loadtest</pre><h4>Step3: Creating Elasticsearch index with <strong>n</strong> number of shards</h4><p>Create the index in elasticsearch by executing below PUT request in Kibana dev console,</p><pre>PUT /loadtest<br>{<br> “settings”: {<br> “index”: {<br> “number_of_shards”: 3,<br> “number_of_replicas”: 0 <br> }<br> }<br>}</pre><h4>Step4: Start generating load in Kafka</h4><p>Here we will be using native performance tool from Kafka. SSH into a Kafka broker and execute below command,</p><pre>/opt/kafka/current/bin/kafka-producer-perf-test.sh --topic loadtest --throughput 1000000 --num-records 90000000 --producer-props bootstrap.servers=youranotherbroker:9092 --payload-file payload.json</pre><p>Make sure to replace youranotherbroker with you Kafka broker FQDN.<br>You can try adjusting the throughput and number of records parameter.</p><h4>Lastly…</h4><p>Now you have generated sufficient load to Kafka. Keep an eye on all the components. Adjust the configurations one by one, not altogether.</p><h4>My observations</h4><ul><li>For Logstash, I adjusted the number of pipeline workers and batch size in each experiment. By default, pipeline worker number is same as the number of CPU cores. For me doubling that number was enough to attain 60% of CPU saturation at times of load. By default batch size is 125, I doubled it in each experiment and found sweet-spot at 2000.</li><li>For Elasticsearch, I had to increase the bulk queue value from 500 to 2000 to accept the batches of logs send from logstash. I also observed improvement in indexing rate when I changed the number of primary shards from 1 to 10. Managing a cluster with a large number of shards is very difficult. You should create proper ILM policies to keep the total number of shards in your cluster optimum.</li><li>For Kafka, I tried increasing the number of partitions and found drastic improvement in event consumption rate. Tweak the number of partition based on your requirement.</li><li>I observed the network traffic in each server by running nethogs and I found it stable. Nethogs is a CLI utility which helps to understand the bandwidth consumption of each process running in that server.</li></ul><p>I have tried to generalize the idea of testing a logging environment at my best in this article. Hope you have enjoyed. Thank you!! 🙏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe1c3131254b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techietalks/how-and-why-to-load-test-your-logging-environment-fe1c3131254b">How and Why to load test your logging environment???</a> was originally published in <a href="https://medium.com/techietalks">techietalks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservices or Macroservices | Part: 1]]></title>
            <link>https://medium.com/adfolks/microservices-or-macroservices-part-a38079c24c84?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/a38079c24c84</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[macroservices]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Tue, 26 May 2020 14:07:56 GMT</pubDate>
            <atom:updated>2020-05-26T14:07:56.079Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZlJOw__IpcfLBqFqAqrzcQ.png" /></figure><p>Let’s talk about Microservices and Macroservices in this series. Rest is history now(Monolithic).</p><p>I will first walk you through Microservice application design complexities and how to make a decision on architecture design, whether to go with Microservice or not.</p><h4>More Microservices is equal to more complexity?</h4><h4>- Complexity in management</h4><p>If you look around there are multiple people working in the same organization under different groups. For example, there can be an HR section, Accounts sections etc. These departments run independently to not to fail the organization. For materializing the same there are more people working in each section and at the top will be an exclusive board of directors team to manage and maintain all sections. Each of the functional sections can be compared to a microservice. And the director’s board can be compared to a group of System Engineers, SRE’s, DevOps etc. The infrastructure of the organization can be compared to your cloud environment.</p><p>So if you want to reduce the complexity you should have a big Director board.</p><h4>- Does the size of your team really matters??</h4><p>Of course, it matters; Microservices are only meant for larger teams working on bigger applications. If you have a big team of engineers and developers, you can probably divide them to a number of teams, and this could probably be as same as the number of Microservices you are planning to build. Thus they can work independently, with their comfortable tech-stack and finally containerize the app and deploy it on Kubernetes, without breaking any dependencies on each other.</p><p>Thus, you eventually decrease the time for the overall development of the application.</p><h4>From where the complexity starts in Microservice environment?</h4><p>From where does it not? From code? From K8&#39;s? From automation tools? Or from your cloud environment? This is a pretty big topic to discuss. For now, we will only discuss about a Microservice app which has already been deployed to production. Below are some pain points.</p><ul><li>It is going to be difficult to troubleshoot an application failure if there is no proper logging implemented at the<strong> code</strong> level</li><li>Storing <strong>logs</strong> are also equally important as the first point</li><li>Management of that <strong>logging infra</strong> is the next pain</li><li>If your services talk to each other, you need to monitor the requests and responses made by each Microservice. This helps you in identifying bottlenecks for each Microservice. To counter this, you have to introduce more tools.</li><li>Increase in east-west traffic or service to service communication will increase the complexity</li><li>Logs from your K8s nodes are to be collected and monitored with another set of tools</li><li>K8s cluster should be secured with proper RBAC, network controls, pod security policies and a pod disruption budget. You may have to bring in tools for conformance checks.</li><li>Next is your cloud environment. Make a separate subscription/account for your production environment. And access to that environment should be limited and restricted.</li><li>You have to implement WAF and necessary security measures to protect your north-south application traffic.</li></ul><p>Out of these pain points, point number 5–7 are the only additional pains introduced by Microservice design. For solving all these pains we had to bring in additional tools with Kubernetes.</p><h4>How to reduce these complexities?</h4><ul><li>There’s a need for more highly skilled Engineers to manage a Microservice environment on Kubernetes in order to make it less complex</li><li>Also, usage of multiple tools to achieve the same purpose as log monitoring of cluster nodes and application pods increases the complexity, rather use the same tools to do both, so the skills required in your engineering team can be minimized.</li><li>Environment optimization is another exercise which has to be done while architecting your application.</li><li>Consider writing server-less microservices, which can be deployed on any cloud environment of your choice. This can minimize cost and management complexities.</li></ul><blockquote>According to me, Microservices are meant to be developed and deployed on server-less platforms, and thus you can reduce a lot of costs.</blockquote><h4>How to decide your application design has to be Microservice or not?</h4><p>We do know that the Microservice application design pattern has lot of advantages. Think it to be as similar to a car, a costly model with some advanced features, like Tesla. Purpose of a car is to commute, however, with Tesla you get good comfort and some advanced features. Nevertheless, it is highly costly compared to a regular model car. And the cost of maintenance is pretty high for this type of cars. The only significant difference is that of travel comfort which certainly varies with price.</p><p>Now let’s say your application is the traveller who wants to commute. If it is Tesla, the passenger will be more comfortable, if it is a regular model, the passenger will be less comfortable. Similarly, if the application is shipped on K8s in Microservices, it will be more comfortable while running. And if it’s going to be a regular 3 tier deployment, it will still run. The purpose will be achieved in both cases.</p><p>So what I meant is, your decision should purely depend on the application you’re going to ship. If we take the example of Netflix, it serves millions of customers every second. For them, scalability is a concern. Breaking monolithic to Microservices will surely increase their customer experience. If they want to release a new feature they can do it without even telling that to customers. They even test out new features to customers by using the well-known Canary deployment model.</p><p>So for an application like Netflix which serves millions of customer requests in seconds, there might be a need to follow the Microservice design pattern. It helps them to manage scalability, improve customer experience and ship new features faster and safer without even notifying the customers.</p><p>However, if you have a small team and still wants to go with the Microservice design, you should consider server-less rather than containers. In case you don’t want to get locked with a vendor by going server-less, consider Macro-service design patterns.</p><p>Wait for part 2 of this series on Macro-services. Catch you soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a38079c24c84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adfolks/microservices-or-macroservices-part-a38079c24c84">Microservices or Macroservices | Part: 1</a> was originally published in <a href="https://medium.com/adfolks">Adfolks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do we have to migrate our application running on VM’s/Physical server/Ec2 instances to Kubernetes??]]></title>
            <link>https://medium.com/adfolks/do-we-have-to-migrate-our-application-running-on-vms-physical-server-ec2-instances-to-kubernetes-6e8a56cdb1dd?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e8a56cdb1dd</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Thu, 20 Feb 2020 18:22:01 GMT</pubDate>
            <atom:updated>2020-02-20T18:22:07.995Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*cAMnuvCdZOMXV4BxtHB6xg.png" /><figcaption>Image source: Internet</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplay.ht%2Fembed%2F%3Farticle_url%3Dhttps%3A%2F%2Fmedium.com%2F_p%2Fdo-we-have-to-migrate-our-application-running-on-vms-physical-server-ec2-instances-to-kubernetes-6e8a56cdb1dd&amp;display_name=Play&amp;url=https%3A%2F%2Fplay.ht%2Farticles%2F6e8a56cdb1dd&amp;image=https%3A%2F%2F0%2A9eRFn04SNNz5iIDq.&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=play" width="700" height="185" frameborder="0" scrolling="no"><a href="https://medium.com/media/16c20004851787a7fbe02cacc46b5e34/href">https://medium.com/media/16c20004851787a7fbe02cacc46b5e34/href</a></iframe><p>This is one of the most common questions that I encountered while interacting with most of the developers/customers. Here, I am gonna draw a picture to help you to make a decision by yourself whether to go with Kubernetes or not.</p><p>Below are some advantages of applications deployed in Kubernetes platform:</p><ul><li>Scalability</li><li>Immutability</li><li>Cloudnative, can be moved from one cloud to another cloud easily</li><li>Observability</li><li>Easy rollout and rollback options</li><li>Infrastructure usage can be optimized and thus save cost</li></ul><p>There are many types of applications and can be classified the way you want them to — Monolithic/Microservice, Stateful/Stateless, Closed source/Open source. Now the question is how to decide whether an application can be run on Kubernetes?? Well continue reading 🙂</p><blockquote>Spoiler alert: Any application which can be containerized can run on Kubernetes</blockquote><h3>Monolithic or Microservice?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdh4UqaYITr4bwIgPjXa6g.png" /><figcaption>Image source: Atlassian</figcaption></figure><p>Whether your application is monolithic or microservice architecture, you can certainly leverage the advantages of Kubernetes platform. If your application is in monolithic and working great then you might not need to think about re-engineering the application to make it microservices and deploy on Kubernetes.</p><blockquote>It’s really a misconception that only microservice application can be run on Kubernetes.</blockquote><p>You can just containerize the monolithic application and run it on top of Kubernetes.</p><h3>When to use microservice?</h3><p>You may not need to design your application in microservice when your application is developed by a single team with few members or if your application only has a limited number of functionalities.</p><p>If you are developing an application with more functionalities, with a big team with a variety of skillsets then you can go with Divide and Conquer strategy, which is essentially microservices.</p><p>You can divide your big team to many small teams and give each micro app to each team. Each team will be using a different tech stack of their choice. In the end, they will build a container image of the application and they test run it on their test Kubernetes cluster.</p><p>Make sure that there are proper guidelines and architecture to follow by each team because at the end each micro app makes up the actual application. This approach can increase the pace of the application development life cycle.</p><p>If Kubernetes and containerization technology were never been invented, this approach might not be even possible. Because this approach can lead issues like package dependency, each team can come up with their application with different versions of a package of nodejs or python or golang … Even if we still think like each micro app can be deployed on VM’s.. guys think about it 😂..</p><h3>We can run databases on containers but do we have to?</h3><p>If you go to CNCF landscape you can see n number of databases there. That itself means a large number of companies are adopting Kubernetes way of running applications.</p><p>You can definitely run a DB on Kubernetes and get all the benefits of Kubernetes platform. It will make your life easier when you want to scale up your DB. Kubernetes make you DB workload more resilient to failures.</p><p>Apart from the advantages, I still like to mention one point, there will be a performance degradation if the storage is not on the same node, where the DB workload pod is running. In most of the cases, people consider using a storage service like ceph if the Kubernetes cluster is on edge location or any storage service if it is on cloud. This draws a trade-off between performance and management. This is still negligible according to the storage hardware choice you make.</p><h3><strong>How to choose a database?</strong></h3><p>Choose a database which is Kubernetes friendly, you can find a lot of operators for database engines like MySQL and PostgreSQL. You can simply goto CNCF landscape and select a database of choice from there. One important thing to consider is the community support of the database which you choose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aXMiO5pqLg9bWiMCyljKVg.png" /><figcaption>List of databases from CNCF landscape</figcaption></figure><h3>What about other tools?</h3><p>Tools which we commonly used for message streaming and queuing, message parsing etc are commonly seen deployed in containers, for eg Kafka, NATS, logstash, fluentd etc.</p><blockquote>If you can put it on container, run it on kubernetes</blockquote><h3>Will there be more skills required than knowing kubernetes?</h3><p>When you have your application running on Kubernetes, you should also need some tools along with it, for eg. Prometheus+Grafana+Alert manager for observability and alerting. And Helm is also a nice-to-have tool for application deployment. This can get growing as you may need to have more control over the cluster itself.</p><p>If you are thinking, you still need to have skillsets on a handful of tools to manage an application deployed in Kubernetes and the Kubernetes platform itself, and find yourself in dilemma, whether to go with Kubernetes or not. Let me remind you that thousands of architects have already embraced Kubernetes. And this is the right time for you to adopt Kubernetes in your ecosystem and contribute to the community.</p><p>Hope you are not confused!!🙂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e8a56cdb1dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adfolks/do-we-have-to-migrate-our-application-running-on-vms-physical-server-ec2-instances-to-kubernetes-6e8a56cdb1dd">Do we have to migrate our application running on VM’s/Physical server/Ec2 instances to Kubernetes??</a> was originally published in <a href="https://medium.com/adfolks">Adfolks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a Helm chart for your application deployment in Kubernetes??]]></title>
            <link>https://medium.com/adfolks/how-to-create-a-helm-chart-for-your-application-deployment-in-kubernetes-9cf16ddfcb45?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cf16ddfcb45</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[chart-museum]]></category>
            <category><![CDATA[helm]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Sat, 15 Feb 2020 16:57:47 GMT</pubDate>
            <atom:updated>2020-02-15T17:01:10.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HbbZMuo5JIFRNJ4t0GU5_Q.png" /><figcaption>Image source: Internet</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplay.ht%2Fembed%2F%3Farticle_url%3Dhttps%3A%2F%2Fmedium.com%2F_p%2Fhow-to-create-a-helm-chart-for-your-application-deployment-in-kubernetes-9cf16ddfcb45&amp;display_name=Play&amp;url=https%3A%2F%2Fplay.ht%2Farticles%2F9cf16ddfcb45&amp;image=https%3A%2F%2F0%2A9eRFn04SNNz5iIDq.&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=play" width="700" height="185" frameborder="0" scrolling="no"><a href="https://medium.com/media/c3173059fe9ca2256a52cd32d9711c1d/href">https://medium.com/media/c3173059fe9ca2256a52cd32d9711c1d/href</a></iframe><p>Helm is the popular package manager for Kubernetes deployments. In this article, I will describe step by step, how to package your Kubernetes deployment and create a Helm chart.</p><h3>Here is the recipe 🥘</h3><p>Before you begin to create a Helm chart for your application deployment, you should test the application deployment and docker image.</p><p>You can try deploying your application by writing the deployment, service, config-map and secret manifests and execute it against the test Kubernetes cluster. Once you have done that follow the below steps to create the Helm chart,</p><ul><li>Run below command to create sample helm chart structure</li></ul><p>helm create package-name</p><p>Here package-name can be your application name, which you want to write a helm chart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*1N4nRYtRAP8dCZDQOZ30MA.gif" /></figure><ul><li>Once the chart template is created, change below keys in values.yaml:</li></ul><ol><li>repository: Your container image repo URL</li><li>imagePullSecrets: Image pull secret if image repository is a private one</li><li>service: You may have to change target port, protocol and name in ports specification</li></ol><ul><li>Make sure ingress enabled is false in values.yaml</li><li>Now open deployment.yaml file from templates folder and see whether there is any additional or missing field in your actual deployment file.</li><li>Tweak the deployment file in templates folder with missing pieces of information from the actual deployment file</li><li>Now do the same with configmap, services, secrets files in the templates folder</li><li>Test the chart by running below command</li></ul><p>helm install --dry-run --debug ./component-name --generate-name</p><ul><li>Once the dry run is a success, package the chart using below command</li></ul><p>helm package component-name</p><h4>Run Chart museum locally to serve charts</h4><p>Now we can use Chart museum to serve our charts, run below command to start Chart museum locally in docker</p><p>docker run --rm -it -p 8080:8080 -v $(pwd)/charts:/charts -e DEBUG=true -e STORAGE=local -e STORAGE_LOCAL_ROOTDIR=/charts chartmuseum/chartmuseum:latest</p><p>Now run below command to push the chart which you just created</p><p>curl --data-binary &quot;@componentname-0.1.0.tgz&quot; <a href="http://localhost:8080/api/charts">http://localhost:8080/api/charts</a></p><p>Once you run the above command add the repo to the list by running below command,</p><p>helm repo add repo-name <a href="http://192.168.0.109:8080/">http://192.168.0.109:8080/</a></p><p>Once the repo is added run the below command to update the repo,</p><p>helm repo update</p><p>Now you can deploy the application by running helm install command as below,</p><p>helm install release-name repo-name/component-name</p><p>Great, now you completed learning how to create a basic helm chart, deploy chart museum locally for serving your charts and using that chart museum for helm chart installations. Happy helming!! 🍾😎</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cf16ddfcb45" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adfolks/how-to-create-a-helm-chart-for-your-application-deployment-in-kubernetes-9cf16ddfcb45">How to create a Helm chart for your application deployment in Kubernetes??</a> was originally published in <a href="https://medium.com/adfolks">Adfolks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to give permission to AWS Code build to access EKS cluster using a role]]></title>
            <link>https://medium.com/adfolks/how-to-give-permission-to-aws-code-build-to-access-eks-cluster-using-a-role-25ca7be73993?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/25ca7be73993</guid>
            <category><![CDATA[ek]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[aws-codebuild]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Wed, 05 Feb 2020 16:00:19 GMT</pubDate>
            <atom:updated>2020-02-05T16:00:25.321Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplay.ht%2Fembed%2F%3Farticle_url%3Dhttps%3A%2F%2Fmedium.com%2F_p%2Fhow-to-give-permission-to-aws-code-build-to-access-eks-cluster-using-a-role-25ca7be73993&amp;display_name=Play&amp;url=https%3A%2F%2Fplay.ht%2Farticles%2F25ca7be73993&amp;image=https%3A%2F%2F0%2A9eRFn04SNNz5iIDq.&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=play" width="700" height="185" frameborder="0" scrolling="no"><a href="https://medium.com/media/c010d23c4d2e2f3491cddc9f0f9e82cd/href">https://medium.com/media/c010d23c4d2e2f3491cddc9f0f9e82cd/href</a></iframe><p><em>TL;DR — This is for DevOps who have working knowledge on AWS Codebuild, IAM roles, EKS cluster and AWS CLI</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JKd7QbuS-g1HE1f0RF6Zg.jpeg" /></figure><p>It is very common practice to use roles for making AWS services talk to each other. It’s the best practice rather than sharing credentials with developers. Credentials can be leaked out and get your environment compromised.</p><p>Here I am gonna explain how we can give permission to AWS CodeBuild service to access AWS EKS environment securely without storing kubeconfig file anywhere. I have seen many people storing there EKS cluster kubeconfig file in S3 bucket or in their git repo, which is very frightening 😱.</p><h3>Here is the recipe 🤗</h3><p>The Workflow consists of 4 steps,</p><p>1 — Create IAM Role with trust relationship from CodeBuild Service Role</p><pre>TRUST=”{ \”Version\”: \”2012–10–17\”, \”Statement\”: [ { \”Effect\”: \”Allow\”, \”Principal\”: { \”AWS\”: \”arn:aws:iam::44755xxxxxxx:role/YOUR-CODEBUILD-ROLE\” }, \”Action\”: \”sts:AssumeRole\” } ] }”</pre><pre>aws iam create-role — role-name EksCodeBuildkubectlRole — assume-role-policy-document “$TRUST” — output text — query ‘Role.Arn’</pre><p>In my example, the CODEBUILD role is service-role/codebuild-BUILD222-service-role, this is auto-generated when you create a CodeBuild.</p><pre>TRUST=”{ \”Version\”: \”2012–10–17\”, \”Statement\”: [ { \”Effect\”: \”Allow\”, \”Principal\”: { \”AWS\”: \”arn:aws:iam::44755xxxxxxx:role/service-role/codebuild-BUILD222-service-role\” }, \”Action\”: \”sts:AssumeRole\” } ] }”<br>aws iam create-role — role-name EksCodeBuildkubectlRole — assume-role-policy-document “$TRUST” — output text — query ‘Role.Arn&#39;</pre><p>2 — Configure aws-auth configmap to authenticate in the cluster using the role created in step1</p><pre>ROLE=&quot;    - rolearn: arn:aws:iam::44755xxxxxxx:role/EksCodeBuildkubectlRole\n      username: build\n      groups:\n        - system:masters&quot;</pre><pre>kubectl get -n kube-system configmap/aws-auth -o yaml | awk &quot;/mapRoles: \|/{print;print \&quot;$ROLE\&quot;;next}1&quot; &gt; /tmp/aws-auth-patch.yml</pre><pre>kubectl patch configmap/aws-auth -n kube-system --patch &quot;$(cat /tmp/aws-auth-patch.yml)&quot;</pre><p>3 — Create a Policy and attach to CodeBuild Service Role, to perform STS:assumerole and permission to READ in EKS:* to the role created in step 1</p><pre>{<br>    &quot;Version&quot;: &quot;2012-10-17&quot;,<br>    &quot;Statement&quot;: [<br>        {<br>            &quot;Sid&quot;: &quot;EKSREADONLY&quot;,<br>            &quot;Effect&quot;: &quot;Allow&quot;,<br>            &quot;Action&quot;: [<br>                &quot;eks:DescribeNodegroup&quot;,<br>                &quot;eks:DescribeUpdate&quot;,<br>                &quot;eks:DescribeCluster&quot;<br>            ],<br>            &quot;Resource&quot;: &quot;*&quot;<br>        },<br>        {<br>            &quot;Sid&quot;: &quot;STSASSUME&quot;,<br>            &quot;Effect&quot;: &quot;Allow&quot;,<br>            &quot;Action&quot;: &quot;sts:AssumeRole&quot;,<br>            &quot;Resource&quot;: &quot;arn:aws:iam::44755xxxxxxx:role/EksCodeBuildkubectlRole&quot;<br>        }<br>    ]<br>}</pre><p>4 — Using aws eks update-kubeconfig with the argument — role-arn &lt;Role created in step1&gt;, you will be able to authenticate in the EKS cluster. Below is a sample buildspec file which you can try ✌️</p><pre>version: 0.2</pre><pre>phases:<br>  install:<br>    runtime-versions:<br>      docker: 18<br>    commands:<br>      - echo test</pre><pre>build:<br>    commands:<br>      - curl -LO <a href="https://storage.googleapis.com/kubernetes-release/release/v1.16.0/bin/linux/amd64/kubectl">https://storage.googleapis.com/kubernetes-release/release/v1.16.0/bin/linux/amd64/kubectl</a><br>      - chmod +x ./kubectl<br>      - export PATH=$PWD/:$PATH<br>      - apt-get -y install jq<br>      - aws eks update-kubeconfig --name $EKS_CLUSTER_NAME --role-arn arn:aws:iam::44755xxxxxxx:role/EksCodeBuildkubectlRole<br>      - kubectl get nodes</pre><p>Now you can manually trigger a build to test it. If everything is configured as I mentioned in above steps, kubectl commands against the EKS cluster will execute successfully and it can be verified in build logs.</p><p>Hope you find this article useful and helped in building a secure CICD pipeline 👍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25ca7be73993" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adfolks/how-to-give-permission-to-aws-code-build-to-access-eks-cluster-using-a-role-25ca7be73993">How to give permission to AWS Code build to access EKS cluster using a role</a> was originally published in <a href="https://medium.com/adfolks">Adfolks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On-premise To Cloud To Serverless To Cloud Native To Serverless Less Applications??]]></title>
            <link>https://medium.com/techietalks/on-premise-to-cloud-to-serverless-to-cloud-native-to-serverless-less-applications-7b80bf3e83d1?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b80bf3e83d1</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Thu, 09 May 2019 18:27:19 GMT</pubDate>
            <atom:updated>2019-05-09T19:12:28.466Z</atom:updated>
            <content:encoded><![CDATA[<h4>A story on digital transformation</h4><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fplay.ht%2Farticles%2F7b80bf3e83d1&amp;src=https%3A%2F%2Fplay.ht%2Fembed%2F%3Farticle_url%3Dhttps%3A%2F%2Fmedium.com%2F_p%2Fon-premise-to-cloud-to-serverless-to-cloud-native-to-serverless-less-applications-7b80bf3e83d1&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=play" width="700" height="185" frameborder="0" scrolling="no"><a href="https://medium.com/media/004c022783839bd527e642766dff8534/href">https://medium.com/media/004c022783839bd527e642766dff8534/href</a></iframe><p>Ok! So the journey started when you created the first application and hosted it in your server; let it be on-premise or on the cloud. Gradually as part of the digital transformation journey, you got compelled to create a mobile application and you ended up creating one! You wrote separate services along with the backend- both for mobile as well as a web application. Later you unified the logic and decoupled the services from the thick monolithic structured application and embraced the ‘<strong>Microservices Architecture</strong>’. And then, backend and the services for mobile and web application became the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UgzwkLQUj26H6_DOyG3Evg.png" /><figcaption>Image source: Internet</figcaption></figure><h4>Microservice Architecture</h4><p>The Microservices architecture started with “Container” adoption. Each service in this ran independently in an isolated place called “container”. This helped the application to work as a single unit. At a not so later stage, cloud hit the market with container strategies. We then deployed our application workloads on cloud-based container solutions. Kubernetes helped the microservice adoption flourish by making the management of container easier. Cloud played equally well by providing Container as well as Kubernetes service. After the container adoption or at the beginning of the container adoption, we started to hear a new term -‘<strong>Serverless</strong>’.</p><h4>Serverless</h4><p>Serverless is cloud-born application architecture. It is purely based on FaaS, SaaS and some of the PaaS components provided by cloud vendors. “Serverless” is very attractive owing to its own benefits. Zero upfront cost — just pay for the time consumed by the CPU to process a task for a trigger, no need of the server to be up and run 24/7 to serve the requests, high scalability and high immutability are few of its great advantages. It is, in fact, the most efficient and cost-effective (to say “costless” would be better) way to deploy an application (though not all applications can be deployed in serverless functions). In spite of all, serverless functions- the compute unit, holds few limitations as well — it can run only for a few minutes, variables have validity till the run time, it is more stateless application friendly. These limitations exist for a reason, serverless functions are PaaS services which runs on a shared environment. Let’s say you have some issues with the current cloud vendor where you have deployed your serverless application, it can be cost-related issues, lack of developers, lack of features, lack of community support etc. So, you decided to migrate your serverless application from one cloud vendor platform to different. You might have used object store, database, compute functions, in memory cache etc to create the application. The look, feel and the behaviour of the mentioned services is entirely different for each cloud vendor. This validates and reaffirms that you cannot run your serverless application deployed in one cloud vendor platform in a different cloud platform. If you want to migrate, you will have to rewrite the application for the new platform. Ideally saying, your application is <strong>vendor locked</strong>. It’s not as easy as you think to migrate your serverless application from one cloud vendor to the other cloud vendor. Here come’s our next destination in the journey, “<strong>Cloud native with Kubernetes</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*Fjsk_yELuDAavR8sXOW6Sg.png" /><figcaption>Image source: Internet</figcaption></figure><h4>Cloud native with Kubernetes!!</h4><p>Several myths and fallacies about Cloud native architecture are found among developers. Cloud native promotes a set of tools for deploying cloud-native serverless applications on the cloud. So now, if you think to switch the cloud vendor by re-engineering and re-platforming your entire application design, think twice and design and deploy your application in a cloud-native way. I’ve already mentioned earlier that cloud-native promotes a set of tools for deploying serverless applications or systems; we should thus focus more on Kubernetes based cloud-native toolsets to build the solution. All cloud vendors provide service to run a Kubernetes cluster. If you look at the CNCF landscape, you will identify a set of open source tools for serverless platforms which can be deployed on top of Kubernetes. There will be tools for serverless functions, databases, observability, logging, tracing, management and more. Pick up the tools required, cook it on top of Kubernetes cluster, scale the pods as needed, create your serverless functions, connect it with the database and other components. Sounds like a recipe? Yes, that’s it. This is what is cloud-native now. The application now you created can be deployed in on-premise, any cloud platform and in the hybrid cloud. The only disadvantage is that there will be a fleet of servers up and running always which incur you more cost than a true serverless.</p><p>It’s always a tradeoff. If you are sure you can stick with a single cloud provider in the entire digital transformation journey, no offence, go serverless. If not, go cloud-native with Kubernetes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5tdZuexihjNTmtnAaljGwg.jpeg" /><figcaption>Image source: Internet</figcaption></figure><h4>So, what’s next? Serverless less application?</h4><p>It may feel like a bit futuristic, or maybe strange, but lets debate. Most of the online applications require a server only for fetching the data. These days all of us have smartphones and better computing devices with good processing capacity, wherein processing can be done at the client side. The server is needed only for storing the data. If people can store and exchange/share the data, your application will be decentralized. This idea of serverless less originally came from the concept of Flat web/open web. The “serverless less” cannot fit in all the cases. This space is very new, there is no proper protocol or standard adopted by the community for creating P2P(peer to peer) network. Still, our tech heroes are working towards it. <strong>IPFS(Internet planetary filesystem), DAT, SSB, Storj </strong>are some<strong> </strong>of the projects which I found so far.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eOTvUqgPd9sR8QhGOVpv7Q.png" /><figcaption>Image source: Internet</figcaption></figure><p>Benefits of this architecture are very attractive than serverless. In addition to the advantages of serverless, we don’t have to invest money for infrastructure anymore. The application will be self-sustainable, will run by itself. More users in the network would mean richer experience for the users. Thus, the data is not stored centrally anywhere, but relevant data will be available virtually everywhere. Privacy is the primary concern on the internet. Yes, you might have security concerns, but I would say you will have more control over the data in this architecture. Think of a future where applications connect devices to share data and run without a server remotely.</p><p>The takeaway from this, ‘Digital transformation journey is an endless trip’.</p><p>Let’s discuss more decentralized applications in the next part.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b80bf3e83d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techietalks/on-premise-to-cloud-to-serverless-to-cloud-native-to-serverless-less-applications-7b80bf3e83d1">On-premise To Cloud To Serverless To Cloud Native To Serverless Less Applications??</a> was originally published in <a href="https://medium.com/techietalks">techietalks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should go cloud native?]]></title>
            <link>https://medium.com/techietalks/why-you-should-go-cloud-native-546616c1cdda?source=rss-6d9a2cd85ded------2</link>
            <guid isPermaLink="false">https://medium.com/p/546616c1cdda</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Vishnu ks]]></dc:creator>
            <pubDate>Sat, 09 Mar 2019 18:33:11 GMT</pubDate>
            <atom:updated>2019-03-09T18:33:11.616Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXN6FeAd81MIe2CMYCtKGw.png" /><figcaption>Image Source: Internet</figcaption></figure><p>It’s been years we have moved to the cloud and went through a series of transformations on application architecture from monolith to microservices to serverless and now what?? Cloud native?</p><h4>Cloud native — Fallacy</h4><p>When I said cloud-native at least some of you might have thought of your serverless application which is deployed in AWS or Azure or GCP using its serverless components might be cloud-native. What else is cloud-native? If you are thinking, deploying an application in the cloud using there PaaS or SaaS services in the cloud makes your application cloud native, WRONG!!<br>If your application can be deployed serverless in any cloud or on on-premise, then that solution can be said as cloud-native. So now the question is how can we achieve that?</p><p>Serverless application deployed in AWS cloud using lambda, S3, RDS need to be re-engineered if we have to bring that app to Azure or GCP and vice versa. So when you deploy application serverless even by achieving benefits of microservices, your application gets vendor locked!!</p><p>Cloud native provides a vendor-neutral solution to achieve serverless and microservice benefits. Let’s see how.</p><blockquote>Cloud native computing uses an open source software stack to deploy applications as microservices, packaging each part into its own container, and dynamically orchestrating those containers to optimize resource utilization. Cloud native technologies enable software developers to build great products faster. — CNCF</blockquote><h4>Kubernetes the saviour!!</h4><p>For deploying a cloud-native application, you have to build the platform, refactor the application to decouple the dependencies using open-source tools and containerize each of the microservices and deploy them in kubernetes cluster.</p><p>There is a wide variety of tools to build platforms for compute functions, object store, API management, message queue, monitoring etc. You can get the complete list here.</p><h4>What will be the result in doing so?</h4><p>You will get a highly resilient, immutable application which will never fail until and unless your application has a bug. The application can be run on on-premise kubernetes cluster, in the cloud or in a hybrid model.</p><p>I would recommend going with managed services provided by public cloud vendors like EKS in AWS, AKS in Azure and GKE in GCP. Cloud will bring more resiliency and immunity to your Kubernetes cluster. And scaling of the cluster will be a cakewalk on the cloud.</p><p>So, in a nutshell, we can say that deploying an application in a cloud-native way makes your application cloud neutral, resilient and more immune to hardware failures. The application will be merged more with the platform layer, and we can decide the tools to build the platform from CNCF landscape <a href="https://landscape.cncf.io/">https://landscape.cncf.io</a><br>Hope you guys enjoyed reading about cloud-native computing. Have a good day!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=546616c1cdda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/techietalks/why-you-should-go-cloud-native-546616c1cdda">Why you should go cloud native?</a> was originally published in <a href="https://medium.com/techietalks">techietalks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>