<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vishal Biyani on Fission</title><link>https://deploy-preview-295--fission-website.netlify.app/author/vishal-biyani/</link><description>Recent content in Vishal Biyani on Fission</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-295--fission-website.netlify.app/author/vishal-biyani/index.xml" rel="self" type="application/rss+xml"/><item><title>Headless Chrome with Puppeteer in a function</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/headless-chrome-with-puppeteer-in-a-function/</link><pubDate>Sun, 09 May 2021 23:50:51 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/headless-chrome-with-puppeteer-in-a-function/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;Running chrome headless is useful for various test automation tasks but running a headless Chrome in Docker can be tricky (&lt;a href="https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#running-puppeteer-in-docker"&gt;More details here&lt;/a&gt;). Also the &lt;a href="https://github.com/puppeteer/puppeteer/issues/3994#issuecomment-524396092"&gt;this Github issue&lt;/a&gt; has some good insights on the issues you might face. This blog shows running headless chrome in a fission function. You can find the working example with code etc. in &lt;a href="https://github.com/fission/examples/tree/main/miscellaneous/nodejs-chrome-headless"&gt;examples repo here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Typical use cases for which Puppeteer is used are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Generating screenshots of specific web pages&lt;/li&gt;
&lt;li&gt;Automating form submission at scale or doing any testing of web pages&lt;/li&gt;
&lt;li&gt;Testing of chrome extensions&lt;/li&gt;
&lt;li&gt;Crawl web pages to gather information from them.&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id="demo"&gt;Demo&lt;/h1&gt;
&lt;p&gt;If you simply want to get a sense of running function run, assuming you have Fission installed, you can run &lt;code&gt;fission spec apply&lt;/code&gt; and then then test the function&lt;/p&gt;</description></item><item><title>Penetration testing with Gobuster &amp; Fission</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/penetration-testing-with-gobuster-fission/</link><pubDate>Thu, 15 Apr 2021 15:57:51 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/penetration-testing-with-gobuster-fission/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;&lt;a href="https://github.com/OJ/gobuster"&gt;Gobuster&lt;/a&gt; is a tool for bruteforcing websites Directory/File, DNS and VHost written in Go. It enables penetration testing and and brute forcing for hackers and testers. In this tutorial we will use Gobuster with Fission&amp;rsquo;s binary environment to run it for specific sites and for specific patterns listed in a text file. Fission allows the teams doing penetration testing to focus on code and execution rather than understanding all things around infrastructure.&lt;/p&gt;</description></item><item><title>Functions On Steroids With PodSpec</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/functions-on-steroids-with-podspec/</link><pubDate>Mon, 20 May 2019 13:41:33 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/functions-on-steroids-with-podspec/</guid><description>&lt;p&gt;There are features which enable a specific new functionality and then there are features which enable a whole new class of functionality in a product. I am excited to share that PodSpec is now available in Fission. Fission functions can be extended to do many things with PodSpec - such as tolerations, volumes, security context, and more.&lt;/p&gt;
&lt;p&gt;Previously, Fission had support for &amp;ldquo;container specs&amp;rdquo; - which allowed you to add environment variables, etc. to functions. With PodSpec - a whole spectrum of new possibilities are now unlocked. While &amp;ldquo;container spec&amp;rdquo; still exists for backward compatibility, we recommend using PodSpec for extending your Fission functions moving forward. In this tutorial we will walk through various use cases and working examples with PodSpec.&lt;/p&gt;</description></item><item><title>New! Fission GitHub Action: Easily Automate Your CI/CD Workflows</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/new-fission-github-action-easily-automate-your-ci/cd-workflows/</link><pubDate>Thu, 25 Apr 2019 18:30:53 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/new-fission-github-action-easily-automate-your-ci/cd-workflows/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;GitHub recently launched &lt;a href="https://github.com/features/actions"&gt;GitHub Actions&lt;/a&gt; which enable developers to develop workflows and execute them based on events in code repositories such as a push event or an issue creation.&lt;/p&gt;
&lt;p&gt;There are many Actions available on the &lt;a href="https://github.com/marketplace?type=actions"&gt;Github marketplace&lt;/a&gt; which you can use for automating various tasks and workflows around development and deployment. In this tutorial we will use the recently launched &lt;a href="https://github.com/marketplace/actions/fission"&gt;Fission Action&lt;/a&gt; and build a simple workflow that deploys a Fission function to a Kubernetes cluster.&lt;/p&gt;</description></item><item><title>Monitor Fission serverless functions with OpenTracing</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/monitor-fission-serverless-functions-with-opentracing/</link><pubDate>Fri, 22 Feb 2019 15:42:30 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/monitor-fission-serverless-functions-with-opentracing/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;As the number of functions and their usage grows, it is crucial to monitor and manage them effectively. Fission already &lt;a href="https://fission.io/docs/usage/function/functions/"&gt;supports logs on CLI&lt;/a&gt; as well integration with external systems using Fluentd. Fission also has &lt;a href="https://deploy-preview-295--fission-website.netlify.app/blog/using-fissions-prometheus-metrics/"&gt;monitoring enabled using Prometheus&lt;/a&gt; and provides a great way to measure and track your functions automatically.&lt;/p&gt;
&lt;p&gt;Serverless functions can be part of a larger distributed system. For example, in the case of serverless applications that become more complex - spanning multiple functions, or in Microservices where functions are triggered between different services that talk to each other to process a single request or perform a business function.&lt;/p&gt;</description></item><item><title>Fission Kafka Sample</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/fission-kafka-sample/</link><pubDate>Thu, 30 Aug 2018 22:50:51 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/fission-kafka-sample/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;The open-source Apache Kafka is one of the most popular distributed Stream Processing platforms used for building real time streaming data pipelines and applications. To learn more about Kafka visit the &lt;a href="https://kafka.apache.org/intro.html"&gt;Kafka documentation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Most serverless functions are triggered by an event, and these in turn may trigger consequent events, which could invoke further functions. This makes Kafka - which acts as a event broker - a natural companion to a Functions-as-a-Service (FaaS) platform such as Fission.&lt;/p&gt;</description></item><item><title>Writing Serverless Functions for JVM with Fission.io</title><link>https://deploy-preview-295--fission-website.netlify.app/blog/writing-serverless-functions-for-jvm-with-fission.io/</link><pubDate>Thu, 30 Aug 2018 22:26:41 +0530</pubDate><guid>https://deploy-preview-295--fission-website.netlify.app/blog/writing-serverless-functions-for-jvm-with-fission.io/</guid><description>&lt;h1 id="introduction"&gt;Introduction&lt;/h1&gt;
&lt;p&gt;The Java Virtual Machine (JVM) is one of the most popular application frameworks, particularly when it comes to enterprise software development - due to the maturity of JVM, the breadth of integrated developer tools and the vibrant community, and the extension of JVM to additional languages.&lt;/p&gt;
&lt;p&gt;The historic data from &lt;a href="https://www.tiobe.com/tiobe-index/"&gt;TIOBE index&lt;/a&gt; also shows how popular JVM and Java have been through the years. In the last decade or so Scala and data-related technologies have made great progress using JVM as the base framework. Most recently Kotlin has seen great progress and also &lt;a href="https://developer.android.com/kotlin/"&gt;got blessings of Google as an official language for Android development&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>