<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rahul Bhati on Fission</title><link>https://deploy-preview-295--fission-website.netlify.app/author/rahul-bhati/</link><description>Recent content in Rahul Bhati on Fission</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-295--fission-website.netlify.app/author/rahul-bhati/index.xml" rel="self" type="application/rss+xml"/><item><title>Event Driven Scaling Fission Function Using KEDA</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/event-driven-scaling-fission-function-using-keda/</link><pubDate>Tue, 14 Jul 2020 18:09:02 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/event-driven-scaling-fission-function-using-keda/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;Events and integrations with event sources such as message queues are an important part of running functions. Fission had the MQ integration for invoking functions and this integration was available for Kafka, NATS, and Azure Queue Storage. This integration had a few limitations:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;For every new integration you want to enable - there was one pod running for enabling the integration&lt;/li&gt;
&lt;li&gt;Autoscaling of the trigger handler was not available.&lt;/li&gt;
&lt;li&gt;Lastly - one Fission installation could connect to and handle only one instance of a MQ. So for example you could only connect to one Kafka instance in a given Fission installation.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;When we decided to build out these features we came across &lt;a href="https://keda.sh"&gt;KEDA project&lt;/a&gt; and it solved most of the limitations which Fission had in the event integration area. Let’s dive into how it works!&lt;/p&gt;</description></item></channel></rss>