Serverless

In my talk “Duct Tape and String: Continuously Delivering Serverless Microservices” at swampUP 2019, I got to talk about some best practice for the project that got me excited about both serverless and K8s: OpenFaaS! For me that meant I got to combine a lot of the things I care about (Containers, Serverless, and Golang), while talking about the awesome possibilities that using Artifactory brings you.

In some cases you might want to get some data from cloud based systems to an environment that doesn’t expose APIs or ports to the outside world. Using webhooks makes that a little easier, but you still need a system that accepts webhooks and is able to get them across your firewall. That is exactly where Solace PubSub+ Cloud comes in! I’ve built a small webhook forwarder app, that gets data from Solace and sends it onwards without having any of my systems exposed to the Internet.

Ever since I discovered Kubernetes, I’ve been looking at OpenFaaS to build and deploy serverless functions on top of it. So as I started building more and more functions to help the Developer Relations team at JFrog, I wanted to share how I use JFrog Artifactory and OpenFaaS together!

I’ve been playing with OpenFaas ever since I learned about Minikube a few years ago, so when one of my colleagues mentioned Google’s Distroless project I obviously needed to see if my Go projects could work using those images too.

Unless you’ve spent the last few months in outer space, or at the very least out of reach from the Internet, you’ve seen that serverless is one of the hottest topics when it comes to building apps. Over the last few months we’ve seen AWS announcing a ton of things at their annual user conference, Google announced support for Go in private beta and serverless containers in private alpha and even Gitlab announced some form of serverless support. With so many massive players it’s easy to forget smaller ones, but those smaller ones are quite often pretty interesting.

No matter the metric, “serverless” is definitely gaining interest. It’s the dream of every developer, supplying the ability to deploy services in the cloud in no time, automatically scale them, enjoy automatic management by a cloud provider—and, most important, keep it all cost effective! How does this dream become a reality? At TIBCO NOW we recorded this session which covers what serverless is all about and the benefits of running your apps in a serverless environment. We talked about a lot of things, including the monoliths-microservices-functions progression and when, where, and why to use serverless architecture.

I can hear you think “Part 2?! So there actually is a part 1?” 😱 The answer to that is, yes, there most definitely is a part 1 (but you can safely ignore that 😅). In that part I went over deploying Flogo apps that you built with the Flogo Web UI using the Serverless Framework. Now, with the Go API that we added to Flogo, you can mix triggers and activities from Flogo (and the awesome community) with your regular Go code and… deploy using the Serverless Framework

Building multi-platform event-driven microservices and functions shouldn’t drive you mad, and if so, there should be a method to your madness! In this short webinar hosted by DZone, learn to build event-driven microservices and functions using Project Flogo.

Let’s talk (to) bots! In this case I’m not talking about the awesome autobots, that save the world from Megatron, but Slack bots that help people collaborate and introduce a little fun! Several weeks ago Slack published an article about building the modern collaboration hub and how that hub makes sure that people can interact with each other and their data. On the Internet, everyone loves interaction… and cats, so let’s build a Slack bot that provides your Slack instance with a bit of cat facts!

As the AI-fueled, edge-exposed, blockchain-driven, and streaming analytics-enabled use cases of the future move closer into view, new technologies are needed to make the vision real. Unique and complex workloads accompany the use cases of the future, but luckily, the enabling technologies to compute those workloads have already arrived.