Introduction At Part 2, we knew what’s real payload was passed to function and how to create a serverless guesbook. In the last post, we will go through the final bank sample and know how to deploy a application to different fission clusters. A Serverless Bank Application in Golang (Sample) In this section, we use a more complex bank sample to demonstrate how to use AJAX interacts with fission functions.

Introduction Part 1 we talked about the advantage of adopting fission as serverless framework on kubernetes, basic concept of around fission core and how to create a simple HelloWorld example with fission. In this post we’ll dive deeper to see what’s the payload of a HTTP request being passed to user function and learn how to create a guestbook application consists with REST functions in Golang. How Fission maps HTTP requests to user function Before we diving into code, we first need to understand what exactly happened inside Fission.

Introduction When users try to develop serverless applications, they often choose to start with Serverless services offered on public clouds, like AWS Lambda or Google Cloud Functions. However, users may encounter following problems after application development: Simulating the same environment on local machines is difficult Vendor lock-in prevents moving applications from one cloud provider to another Sensitive data that should not be sent outside an on-premises datacenter Fission is a serverless framework built on top of Kubernetes.

Introduction 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 Kafka documentation. 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.

Introduction 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. The historic data from TIOBE index 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.

FaaS Functions give you the ability to quickly deploy services made of small functionality. But any more complex use case requires multiple functions. What are the different approaches to this? What are the parameters on the basis of which we should compare these approaches? In this short blog post, I’ll briefly go over the significance of function composition and why you should care about it. First off, What is Function Composition Function composition refers to combining single functions to create bigger, more complex functions.

Earlier this month, Software Engineer Erwin van Eyk and Developer Advocate Timirah James gave an awesome talk on function composition at KubeCon EU in Copenhagen, Denmark. The talk covered 5 serverless function compostion styles and the significance of function composition when deploying serverless functions. You can view and download the slides here, or you can check out the video below. What’s FaaS? FaaS is FaaS of course is functions as a service and FaaS frameworks allow developers to deploy individual parts of an application on an as-needed basis.

This is the second half of a 2-part introduction to Fission Workflows. In Part One of this series, we talked about the concepts around Fission Workflows, how to create them, as well as a few demos of use cases in which you might use them. So we’ve gone over what workflows are, along with when, and how to execute them. In this blog post we’ll dive deeper, breaking down each component that makes up the fabric of workflows, and what make workflows so efficient.

As we all know, the presence of active women in the Open Source community is scarce. Last year, GitHub conducted an online survey in which they randomly selected 5,500 developers of open source projects, and found that only 3% of that population were female (crazy right?!?). The knowledge of that fact alone can be intimidating for other women to particpate in the open source community. So this year for Women’s History Month, the Fission team decided to host the #WomenInOpenSourceHighlight series on social media, where we shined a light on amazing women in the Open Source field.

This is the first of a 2-part introduction to Fission Workflows. Fission provides fast serverless functions on Kubernetes. While functions are great for specific pieces of business logic, any non-trivial application requires a composition of functions. There are many ways to compose functions. You can directly call functions from each other — but there are some disadvantages to this. For one, the structure of the application becomes hard to understand; dependencies are not obvious; essentially, every function becomes an API.