<?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 Vedha Sankar on Medium]]></title>
        <description><![CDATA[Stories by Vedha Sankar on Medium]]></description>
        <link>https://medium.com/@vedhasankar26?source=rss-7c64d829f78a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8GjKqNkBuLXyjd9X</url>
            <title>Stories by Vedha Sankar on Medium</title>
            <link>https://medium.com/@vedhasankar26?source=rss-7c64d829f78a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:22:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vedhasankar26/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[Streamline Your Brownfield Deployment: Creating an Application Gateway and Linking it to AKS]]></title>
            <link>https://vedhasankar26.medium.com/streamline-your-brownfield-deployment-creating-an-application-gateway-and-linking-it-to-aks-ca4014053cb7?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca4014053cb7</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[azure-kubernetes-service]]></category>
            <category><![CDATA[kubernetes-ingress]]></category>
            <category><![CDATA[azure-application-gateway]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Fri, 02 Jun 2023 07:53:52 GMT</pubDate>
            <atom:updated>2023-06-02T07:53:52.213Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V0yMkuYvvt0e4ZJCoQqQ8w.jpeg" /></figure><p>In the realm of cloud-native applications, adopting a brownfield deployment approach can be an effective strategy for modernizing existing applications and infrastructure. Brownfield deployment involves incorporating cloud-native components into an already established environment, allowing organizations to leverage the benefits of cloud technologies while preserving their existing investments. One crucial aspect of this process is connecting a Kubernetes cluster, such as Azure Kubernetes Service (AKS), with an Application Gateway. This article will guide you through the steps to create an Application Gateway and seamlessly integrate it with AKS.</p><p>Start by connecting to your AKS Cluster:</p><pre>az account set --subscription subscriptionId<br>az aks get-credentials --resource-group resourceGroup --name aksClusterName</pre><p>Before setting up our Application Gateway, we would need the following:</p><ul><li>Public IP — this should be in the same resource group as the AKS Cluster</li><li>Virtual Network</li></ul><p>The public IP should be in the same resource group as the AKS cluster with the allocation method as Static.</p><pre>az network public-ip create -n myPublicIp -g resourceGroup --allocation-method Static --sku Standard</pre><p>The virtual network should with address prefix <em>10.0.0.0/16 </em>and subnet prefix <em>10.0.0.0/24.</em></p><pre>az network vnet create -n myVnet -g resourceGroup --address-prefix 10.0.0.0/16 --subnet-name mySubnet --subnet-prefix 10.0.0.0/24</pre><p>Create the application gateway in the required zone, with the required configurations. I’m going to be creating my application gateway in the US East zone and with the SKU to be Standard. This SKU could be configured to be a WAF (Web Application Firewall) as well. Attach the created public IP and subnet as well.</p><pre>az network application-gateway create -n myApplicationGateway -l eastus -g resourceGroup --sku Standard_v2 --public-ip-address myPublicIp --vnet-name myVnet --subnet mySubnet --priority 100</pre><p>Configure it to be WAF using:</p><pre>az network application-gateway create -n myApplicationGateway -l eastus -g testing --sku WAF_v2 --public-ip-address myPublicIp --vnet-name myVnet --subnet mySubnet --priority 100</pre><p>Enable the add-on for the AKS integration with Application Gateway in Application Gateway Ingress Controller. Get the Application Gateway ID first and enable it for that particular application gateway.</p><pre>appgwId=$(az network application-gateway show -n myApplicationGateway -g resourceGroup -o tsv --query &quot;id&quot;) <br>az aks enable-addons -n aks-cluster -g resourceGroup -a ingress-appgw --appgw-id $appgwId</pre><p>Next, we need to create a virtual network (VNet) peering between an Application Gateway (AppGW) VNet and an AKS (Azure Kubernetes Service) VNet, and vice versa.</p><p>By establishing VNet peering between the AppGW VNet and AKS VNet, and configuring the necessary allow rules, you enable seamless and secure communication between the two environments. This integration empowers you to leverage the traffic management capabilities of AppGW, such as SSL termination, load balancing, and application routing, for your AKS cluster.</p><p>This can be achieved by:</p><pre># get node resource group and vnet name<br>nodeResourceGroup=$(az aks show -n aks-cluster -g resourceGroup -o tsv --query &quot;nodeResourceGroup&quot;)<br>aksVnetName=$(az network vnet list -g $nodeResourceGroup -o tsv --query &quot;[0].name&quot;)<br><br># create vnet peering between appgw vnet and aks vnet<br>aksVnetId=$(az network vnet show -n $aksVnetName -g $nodeResourceGroup -o tsv --query &quot;id&quot;)<br>az network vnet peering create -n AppGWtoAKSVnetPeering -g resourceGroup --vnet-name myVnet --remote-vnet $aksVnetId --allow-vnet-access<br><br># create vnet peering between aks vnet and appgw vnet<br>appGWVnetId=$(az network vnet show -n myVnet -g resourceGroup -o tsv --query &quot;id&quot;)<br>az network vnet peering create -n AKStoAppGWVnetPeering -g $nodeResourceGroup --vnet-name $aksVnetName --remote-vnet $appGWVnetId --allow-vnet-access</pre><p><strong>Let’s now deploy an application using AGIC (Application Gateway Ingress Controller)</strong></p><p>To ensure that your application is accessible through the newly set up Application Gateway for your AKS cluster, we will verify the IP address of the Ingress. This step will allow us to confirm the reachability of your application.</p><p>After obtaining the credentials for the AKS cluster you have created, execute the following command to deploy a sample application that utilizes AGIC (Application Gateway Ingress Controller) for Ingress to the cluster. AGIC will automatically update the previously configured application gateway with appropriate routing rules to direct traffic to the newly deployed sample application.</p><pre>kubectl apply -f https://raw.githubusercontent.com/Azure/application-gateway-kubernetes-ingress/master/docs/examples/aspnetapp.yaml</pre><p>Get the ingress using:</p><pre>kubectl get ingress</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca4014053cb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Handy GCloud CLI Commands]]></title>
            <link>https://vedhasankar26.medium.com/handy-gcloud-cli-commands-b62a2cf531ad?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b62a2cf531ad</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cli]]></category>
            <category><![CDATA[gcp]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Fri, 02 Jun 2023 07:08:27 GMT</pubDate>
            <atom:updated>2023-06-02T07:08:27.643Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/359/1*eqELzbpYQvmPAFd5NvrALA.png" /></figure><h4>Google Cloud CLI Set-Up — on Ubuntu</h4><p>Type in these commands one by one</p><pre>sudo apt-get install apt-transport-https ca-certificates gnupg<br>echo &quot;deb [signed-by=/usr/share/keyrings/cloud.google.gpg] https://packages.cloud.google.com/apt cloud-sdk main&quot; | sudo tee -a /etc/apt/sources.list.d/google-cloud-sdk.list<br>curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add -<br>sudo apt-get update &amp;&amp; sudo apt-get install google-cloud-sdk</pre><p>and finish off the set-up by initialising your terminal:</p><pre>gcloud init</pre><p>If you’re installing the GCloud CLI on Docker then use this:</p><pre>RUN echo &quot;deb [signed-by=/usr/share/keyrings/cloud.google.gpg] http://packages.cloud.google.com/apt cloud-sdk main&quot; | tee -a /etc/apt/sources.list.d/google-cloud-sdk.list &amp;&amp; curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key --keyring /usr/share/keyrings/cloud.google.gpg  add - &amp;&amp; apt-get update -y &amp;&amp; apt-get install google-cloud-cli -y</pre><p><strong>GCP Commands</strong></p><ul><li>List the currently configured accounts in the Google Cloud SDK</li></ul><pre>gcloud auth list</pre><ul><li>Configure the SDK</li></ul><pre>gcloud init</pre><ul><li>Initiate the login process</li></ul><pre>gcloud auth login</pre><ul><li>Set the active project</li></ul><pre>gcloud config set project PROJECT_ID</pre><ul><li>List available configurations</li></ul><pre>gcloud config configurations list </pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b62a2cf531ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Architecture — Processes run on Master Node]]></title>
            <link>https://medium.com/featurepreneur/kubernetes-architecture-processes-run-on-master-node-c5869b89b931?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5869b89b931</guid>
            <category><![CDATA[etcd]]></category>
            <category><![CDATA[kubernetes-schedular]]></category>
            <category><![CDATA[kubernetes-architecture]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[api-server]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Sat, 15 Jan 2022 08:13:40 GMT</pubDate>
            <atom:updated>2022-01-15T08:13:40.569Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kubernetes Architecture — Processes run on Master Node</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hMpmo9YCQ5Cl7ajE.jpg" /></figure><p>In Kubernetes, all of the managing processes are done by Master nodes. They don’t do any of the heavy lifting but only manage the tasks and nodes.</p><p>Master nodes schedule pods and monitors for down time. It re-schedules or restarts pods.</p><p>The Master nodes are responsible for managing the cluster. Information about the members of the cluster and its health is stored in the Master nodes. All the nodes are monitored by the Master node and if a node fails, the workload of the failed node is transferred to another worker node. It is responsible for the actual orchestration of the containers in the worker nodes.</p><p>There are four processes that are run on the Master nodes:</p><ul><li>API Servers</li><li>Scheduler</li><li>Controller Manager</li><li>Etcd</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*M9uZ1m9SYJv7f57RP59fYQ.png" /></figure><p><strong>API Server</strong></p><p>The API server acts as a gateway for all requests that come in. It validates whether the request is authentic or not. There is only one entry point into the cluster which is the API server. Only if the API server authenticates the request, the other processes will proceed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*TEyhpidwOJWhnLt8J7HL2Q.png" /></figure><p><strong>Scheduler</strong></p><p>The scheduler will start the pod in one of the nodes depending upon which node is less busy. It will check the request and see how much CPU is required, depending on that, it will assign the pod to the node that is more available or has less CPU usage.</p><p>The scheduler will just decide on which node to put the new pod in, the Kubelet will start the new pod on the request of the scheduler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*9xBylNTI7N9sO52K_lCoWA.png" /></figure><p><strong>Controller Manager</strong></p><p>The controller manager detects the state changes like failure in pods/nodes or any other component. It tries to recover the dead pods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*SoiJ4npparWOY_RtcZ1maQ.png" /></figure><p><strong>Etcd</strong></p><p>The etcd is known as the cluster brain. It is a key-value store of the cluster state. All the cluster changes get stored in the etcd.</p><p>The etcd will know information such as what resources are available, if the cluster state changed, if the cluster is healthy etc.</p><p>Only based on this data, the other processes will know what has happened. Application data is <em>not</em> stored in the etcd.</p><p>Hope this article was useful. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5869b89b931" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/kubernetes-architecture-processes-run-on-master-node-c5869b89b931">Kubernetes Architecture — Processes run on Master Node</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minikube and Kubectl — Setup in Linux]]></title>
            <link>https://medium.com/featurepreneur/minikube-and-kubectl-setup-in-linux-3bff0a52f97f?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bff0a52f97f</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[featurepreneur]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[minikube]]></category>
            <category><![CDATA[kubectl]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Wed, 12 Jan 2022 15:25:02 GMT</pubDate>
            <atom:updated>2022-01-13T06:41:13.167Z</atom:updated>
            <content:encoded><![CDATA[<h3>Minikube and Kubectl — Setup in Linux</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/0*0eoRuzMUkbpVs3ec.jpg" /></figure><p>Minikube is a tool that helps you run Kubernetes locally on your system. You can use it for testing purposes. It is a one node cluster where the master processes &amp; node processes run on one machine.</p><p>Minikube has the runtime container (docker) preinstalled.</p><p>Kubectl is the CLI tool for the Kubernetes cluster. We will need it installed to make our lives easier when working with k8s.</p><p>Note: For this set-up you need to have docker configured previously</p><p><strong>Kubectl Set-up</strong></p><pre>curl -LO &quot;https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl&quot;</pre><pre>curl -LO &quot;https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl.sha256&quot;</pre><pre>echo &quot;$(&lt;kubectl.sha256)  kubectl&quot; | sha256sum --check</pre><pre>sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl</pre><p>To check if everything is working fine, we can use:</p><pre>kubectl version --client</pre><p><strong>Minikube Set-up</strong></p><pre>curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64</pre><pre>sudo install minikube-linux-amd64 /usr/local/bin/minikube</pre><p>You can start, stop and delete your minikube cluster using the following commands:</p><pre>minikube start<br>minikube stop<br>minikube delete</pre><p><strong>References:</strong></p><ul><li><a href="https://kubernetes.io/docs/tasks/tools/install-kubectl/">https://kubernetes.io/docs/tasks/tools/install-kubectl/</a></li><li><a href="https://minikube.sigs.k8s.io/docs/start/">https://minikube.sigs.k8s.io/docs/start/</a></li></ul><p>Hope this was helpful. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bff0a52f97f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/minikube-and-kubectl-setup-in-linux-3bff0a52f97f">Minikube and Kubectl — Setup in Linux</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Architecture — Node Processes]]></title>
            <link>https://medium.com/featurepreneur/kubernetes-architecture-node-processes-4d950bf6f474?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d950bf6f474</guid>
            <category><![CDATA[kubernetes-cluster]]></category>
            <category><![CDATA[featurepreneur]]></category>
            <category><![CDATA[kubernetes-architecture]]></category>
            <category><![CDATA[container-orchestration]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Wed, 12 Jan 2022 08:08:13 GMT</pubDate>
            <atom:updated>2022-01-12T08:08:13.712Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kubernetes Architecture — Node Processes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h56ncBTfHZvxGqsY" /><figcaption>Photo by <a href="https://unsplash.com/@ventiviews?utm_source=medium&amp;utm_medium=referral">Cameron Venti</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Kubernetes is a container orchestration tool that is helpful to run applications in production, orchestrate the connectivity between the containers and automatically scale up or down based on the load.</p><p>We will be looking at the main process run by one of its main components: Worker nodes</p><p>Worker nodes do all the heavy lifting in our Kubernetes cluster. Each node has multiple pods in it and each pod usually contains one container.</p><p>There are three processes that are run on every worker node:</p><ul><li>Container Runtime</li><li>Kubelet</li><li>Kube Proxy</li></ul><p><strong>Container Runtime</strong></p><p>You need to install a container runtime into each node in the cluster so that Pods can run there. By default the container runtime for Kubernetes is Docker but other alternatives to Docker are Rocket and CRIO.</p><p><strong>Kubelet</strong></p><p>The kubelet agent is responsible for interacting with the master node to provide health information of the worker node and carry out<br>actions requested by the master on the worker nodes. It schedules pods as necessary and is the only process that can interact with both the container and node.</p><p><strong>Kube Proxy</strong></p><p>Kube Proxy is a network proxy that runs on each node in your cluster and helps connect the k8s services to each other. It maintains the networking rules in your node and is an essential part on your node.</p><p>Hope this article was useful! Thank you for reading :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d950bf6f474" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/kubernetes-architecture-node-processes-4d950bf6f474">Kubernetes Architecture — Node Processes</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Connecting Azure Database for PostgreSQL to Azure Databricks using Python]]></title>
            <link>https://medium.com/featurepreneur/connecting-azure-database-for-postgresql-to-azure-databricks-using-python-2d7e6e8169e5?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d7e6e8169e5</guid>
            <category><![CDATA[databricks]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[pandas]]></category>
            <category><![CDATA[featurepreneur]]></category>
            <category><![CDATA[postgresql]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Tue, 30 Nov 2021 14:21:11 GMT</pubDate>
            <atom:updated>2021-11-30T14:21:11.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*ertoyMLpBWQXX3dC.png" /></figure><p>First, navigate to Azure Database for PostgreSQL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/722/1*QbxHNZHFmIQwLqZR6dm0Zw.png" /></figure><p>Select the flexible server as a deployment option as it is generally used for small-scale, development purposes.</p><p>I will be creating my Database with the following configurations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*7-Uq15f4nVJFV9cSq-MX5w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/1*xyqnxFJtEOF6NknwGUza7w.png" /></figure><p>Make sure to go for ‘Development’ in the workload type if you’re testing out stuff!</p><p>In the next step, add ‘<a href="https://portal.azure.com/#">current client IP </a>address in the firewall rules and allow public access from any Azure service like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*DRObLJLCUpA--voohFSYxQ.png" /></figure><p>It takes around 10 minutes to get deployed, so sit back and have some popcorn till then.</p><p>Once it’s deployed, you will find this page:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yx-fQ7Q9Pi6QWemaerZbXQ.png" /></figure><p>Connect to the database using the following command in your terminal:</p><pre>psql -h &lt;Server name&gt; -U &lt;Server admin login name&gt; -p 5432 -d postgres</pre><p>When prompted, enter your DB password. Once you’ve successfully completed that, you should see something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AJG9tXS23R7S9Cdp8cf3-g.png" /></figure><p>Create and connect to the database like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IkMmerqnSHw8lM9SGHC2VQ.png" /></figure><p>Commands for the same are:</p><ol><li>To create a database:</li></ol><pre>CREATE DATABASE test;</pre><p>2. To connect to the database:</p><pre>\c test;</pre><p>3. Once, you’re in create a table. I will be creating a table ‘city’ like so:</p><pre>CREATE TABLE CITY (</pre><pre>ID serial PRIMARY KEY,</pre><pre>NAME VARCHAR (50) UNIQUE NOT NULL,</pre><pre>STATE VARCHAR (50) NOT NULL,</pre><pre>COUNTRY VARCHAR (100) NOT NULL,</pre><pre>CREATED_AT TIMESTAMP NOT NULL</pre><pre>);</pre><p>4. Next, insert values into the table:</p><pre>INSERT INTO CITY (NAME, STATE, COUNTRY, CREATED_AT) VALUES (&#39;Toronto&#39;, &#39;Ontario&#39;, &#39;Canada&#39;, NOW());</pre><pre>INSERT INTO CITY (NAME, STATE, COUNTRY, CREATED_AT) VALUES (&#39;Montreal&#39;, &#39;Quebec&#39;, &#39;Canada&#39;, NOW());</pre><pre>INSERT INTO CITY (NAME, STATE, COUNTRY, CREATED_AT) VALUES (&#39;Chennai&#39;, &#39;Tamilnadu&#39;, &#39;India&#39;, NOW());</pre><p>5. Verify that the values have been inserted like so:</p><pre>SELECT * FROM CITY;</pre><p>Now that we’ve created a table, navigate to Azure databricks and create a new notebook.</p><p>To work with PostgreSQL in python, we will need to install the library, psycopg2. You can do so using the command:</p><pre>!pip install psycopg2</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QiBR3cpopHr5i5q5NNdUig.png" /></figure><p>You will need a connection string to be able to connect into your PostgreSQL Database, so get one, go to your database, and in settings, you will find ‘Connection Strings’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AN1f1sClBW7fWHDuuW2chA.png" /></figure><p>Copy the ‘PostgreSQL connection URL’ from there and type in your password and other details where required.</p><p>Note that in your connection string, you will also have to enter in your DB name like so:</p><pre>postgres://tact:{your_password}@tact-pg.postgres.database.azure.com/{db_name}?sslmode=require</pre><p>Connect to the DB like so:</p><pre>import psycopg2<br>import pandas as pd</pre><pre># Construct connection string</pre><pre>conn_string = &quot;&quot;<br>conn = psycopg2.connect(conn_string)<br>conn.autocommit = True<br>cur = conn.cursor()</pre><p>Once I’ve connected into the DB, I will be printing all the rows in the table, ‘city’ like so:</p><pre>def select_all(conn):<br>    &quot;&quot;&quot;<br>    Query all rows in the CITY table<br>    :param conn: the Connection object<br>    :return:<br>    &quot;&quot;&quot;<br>    cur = conn.cursor()<br>    cur.execute(&quot;SELECT * FROM city;&quot;)<br> <br>    rows = cur.fetchall()<br>    <br>    print(&#39;rows count : &#39;+str(len(rows)))<br>    <br>    if(len(rows) &lt;= 0):<br>        print(&#39;No Data available&#39;)<br> <br>    for row in rows:</pre><pre>print(row)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*033vZXE_mUXcpVMt1JaLXw.png" /></figure><p>You can also convert this to a Pandas DataFrame using the following commands:</p><pre>import pandas.io.sql as sqlio</pre><pre>sql = &quot;select * from city;&quot;<br>dat = sqlio.read_sql_query(sql, conn)</pre><p>Displaying the DataFrame:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*tpyk1MDGmwi8PVwWyY7rWw.png" /></figure><p>Hope this was useful to you! Thanks for reading!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d7e6e8169e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/connecting-azure-database-for-postgresql-to-azure-databricks-using-python-2d7e6e8169e5">Connecting Azure Database for PostgreSQL to Azure Databricks using Python</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[T-1 for the AWS Cloud Practitioner Exam!]]></title>
            <link>https://medium.com/featurepreneur/t-1-for-the-aws-cloud-practitioner-exam-54f551b0fd3e?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/54f551b0fd3e</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-ccp]]></category>
            <category><![CDATA[aws-cloud-practitioner]]></category>
            <category><![CDATA[featurepreneur]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Thu, 04 Nov 2021 02:43:39 GMT</pubDate>
            <atom:updated>2022-06-17T10:33:35.790Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FjjrakE0oyGfnHKj" /><figcaption>Photo by <a href="https://unsplash.com/@glenncarstenspeters?utm_source=medium&amp;utm_medium=referral">Glenn Carstens-Peters</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So, there’s around 30 hours to my AWS CCP exam.</p><p>Preparing and going through practice papers of the exam is what I’m spending most of my time on right now, and I have to say these papers are no easy feat 😂</p><p>Nervous is an understatement but I’m trying to keep my hopes up!</p><p>Pretty sure it’s been 6 months since I first heard of what AWS even was, and I can’t believe I’m taking this exam right now.</p><p>Honestly, I have to thank TactLabs for introducing me to what AWS was, because without their support I don’t think I would be writing the exam!</p><p>Everyone, there has always believed in me and made sure I knew of their support for me, and being sponsored by TactLabs is just the tip of the iceberg. Raja Sir and everyone always helped me with anything I needed, and because of their constant encouragement, here I am today!</p><p>Hoping and wishing I pass the exam tomorrow!</p><p>PS: I passed!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54f551b0fd3e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/t-1-for-the-aws-cloud-practitioner-exam-54f551b0fd3e">T-1 for the AWS Cloud Practitioner Exam!</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS App Runner — A quick way to deploy applications]]></title>
            <link>https://medium.com/featurepreneur/aws-app-runner-a-quick-way-to-deploy-applications-ec62d831a017?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec62d831a017</guid>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[apprunner]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Wed, 06 Oct 2021 15:36:22 GMT</pubDate>
            <atom:updated>2021-10-15T01:38:36.729Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS App Runner — A quick way to deploy applications</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*LsXkdedKSLkSOeVk545x5Q.png" /><figcaption>AWS</figcaption></figure><p>AWS App Runner is an AWS service that provides a fast and simple way to deploy applications from source codes or container images.</p><p>Before we start using App Runner, we will first need an ECR repository with the image that we want to deploy. So, let’s do that first.</p><p>You will need AmazonEC2ContainerRegistryFullAccess policy to create a repository in ECR, so make sure you have it.</p><p>Go to ECR from your management console and create a public repository.</p><p>Once you’ve create the repository, push the docker image using the push commands provided to you by ECR:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*NB064pEvsfmu2qi1UFrlgA.png" /></figure><p>The above push commands were for the repository I had created for demo purposes. Please refer to your own commands like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yoHMeDHNw3aNix-hU2pd_Q.jpeg" /></figure><p>Once you’ve pushed the image go to App Runner and create a service:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EWfp8g34V0c8orsl8f7YuA.png" /></figure><p>Name your service, add in environment variables, if any and add the required port too.</p><p>Once you’re done with that, you can just review and create your service.</p><p>After the service has been created, it should look like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6izhh84oL7wnqWOAGfc3-w.png" /></figure><p>You can test if you’re application is working fine by taking the default domain and entering it in a new tab.</p><p>Thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec62d831a017" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/aws-app-runner-a-quick-way-to-deploy-applications-ec62d831a017">AWS App Runner — A quick way to deploy applications</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pickle to API — Azure]]></title>
            <link>https://medium.com/featurepreneur/pickle-to-api-azure-48497986868?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/48497986868</guid>
            <category><![CDATA[pickles]]></category>
            <category><![CDATA[machine-learning-studio]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Wed, 06 Oct 2021 03:34:29 GMT</pubDate>
            <atom:updated>2021-10-06T03:34:29.479Z</atom:updated>
            <content:encoded><![CDATA[<h3>Pickle to API — Azure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSwKIo8Ucl6Entn_kTHarg.png" /></figure><p>So, pickle to API without writing any code. How exactly is it possible?</p><p>Using Azure’s Machine Learning Service we can do just that!</p><p>First navigate to Azure ML service from the Azure Dashboard.</p><p>You will find a page that looks like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6AH1vkjZNuSitFzl1BI9_Q.png" /></figure><p>Create a workspace using the following configurations for a basic and minimal set-up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V4BLbA0KIPZQ7k7H87rlfg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VPIUW7UbnOBIcNYp9sc9Qg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68_re-ts1QcEOZ3AraIHAA.png" /></figure><p>Once you’re done with the above set up tags (if required), review and create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*VsAZyguL22YmLHm5upmqSw.png" /></figure><p>Navigate to ML studio after the workspace has been created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRJKyfScIfnrBYcTIilblQ.png" /></figure><p>Go to models and register your model:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8jZS49wmZiLApZjr5Bp4A.png" /></figure><p>Once that’s done, you will have to deploy your model. Select the model you wanna deploy</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ahhSmwYrHDk0gPaj2yHrw.png" /></figure><p>Choose the type of deployment you wanna do, for this example I’ve deployed to a web service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cxCU0QjAAj5-MamxoYCeBQ.png" /></figure><p>Use the following configurations and deploy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ae86o_oMA-Y_a4jSk-X50g.png" /></figure><p>It takes about 20 minutes for the model to deploy, so make sure you have some music to keep you company!</p><p>While waiting you can check up on your model by navigating to endpoints &gt; model.</p><p>Here, you will see that the deployment state changes frequently from unhealthy to transitioning to nothing. But patience is the key here, make sure you wait till the state is either healthy or failed till you delete it.</p><p>You can use this guide as a reference to what other deployment states you’ll encounter;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/977/1*pPjVf8GdTG9MahFHE4HDNA.png" /></figure><p>So, once your model has been successfully deployed, it should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Mh2aTuphHo88zRHLmOADw.png" /></figure><p>All the best!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48497986868" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/pickle-to-api-azure-48497986868">Pickle to API — Azure</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TSON — Reduce your file size]]></title>
            <link>https://medium.com/featurepreneur/tson-reduce-your-file-size-c4645cd22ff1?source=rss-7c64d829f78a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4645cd22ff1</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[tson]]></category>
            <category><![CDATA[storage]]></category>
            <category><![CDATA[json]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Vedha Sankar]]></dc:creator>
            <pubDate>Sun, 03 Oct 2021 09:15:28 GMT</pubDate>
            <atom:updated>2021-10-03T09:15:28.422Z</atom:updated>
            <content:encoded><![CDATA[<h3>TSON — Reduce your file size</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_FYm-uEiWsS90Hdi" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>So what is TSON exactly? TSON is a file type that we came up with to reduce the size of JSON files.</p><p>It is especially useful when we’re dealing with large JSON files as it compresses the files by mapping unique key values to a unique integer value to reduce the file size.</p><p>When dealing with large JSON files, we will find that the key values are usually repetitive and it causes the file sizes to increase a lot.</p><p>So, by mapping the unique values we were able to reduce the file size by 98%.</p><p>We were able to reduce a 32 MB file to a 834 KB file.</p><p>Here is the before and after of one of the files we converted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*oFwrts9jw6UO9nVER9ExuQ.png" /><figcaption>Before</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*uZC1CbnOBMl-dYeP2yjwWw.png" /><figcaption>After</figcaption></figure><p>By using TSON, we can significantly reduce the file size.</p><p>Check out the open-source GitHub repository at <a href="https://github.com/tactlabs/tson">https://github.com/tactlabs/tson</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4645cd22ff1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/featurepreneur/tson-reduce-your-file-size-c4645cd22ff1">TSON — Reduce your file size</a> was originally published in <a href="https://medium.com/featurepreneur">featurepreneur</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>