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.

NATS is a lightweight, open source, high-performance, messaging system for cloud native applications, IOT messaging, and microservices architectures. The NATS messaging system implements a scalable publish-subscribe (or pub/sub) distribution model. There are a number of open source technologies like Kafka, and several cloud technologies such as Google Cloud Pub/Sub and Azure Service Bus that adopt this model as well. In light of NATS recently being accepted into The Cloud Native Computing Foundation last week, we thought it’d be cool to share how Fission functions and workflows utilize this sleek messaging system on top of Kubernetes.

First, What is Serverless? In the last blog post Kubernetes for Newbies, we went over how to get an application up and running on Kubernetes. Though Kubernetes is surely a hot topic in tech, the “serverless” space has become just as (if not even more) trendy. Why is serverless so popular in the dev community? Turns out, serverless is a developer’s saving grace when it comes to managing servers. Instead of managing a bunch of servers, Serverless solutions allow developers to … well … not manage servers at all!

Over the past 3 or so years, it seems the term “containerization” and the name “Kubernetes” have been amplified throughout the tech community non-stop. Even with that being so, as a developer, it can be easy to shy away from Kubernetes as its learning curve is notorious for being a steep one. But everyone’s gotta start somewhere, right? This tutorial will give you a basic overview of some of main features of Kubernetes, while walking you through the process of running a simple HelloWorld Golang application locally on your machine to running it on Kubernetes.