Not too long ago Flogo introduced a new Go API that allows you to build event-driven apps by simply embedding the Flogo engine in your existing Go code. Now you can use the event-driven engine of Flogo to build Go apps while using the activities and triggers that already exist and combining that with “regular” Go code. In one of my other posts, I built an app that could receive messages from PubNub and for this post, I’ll walk through building the exact same using the Go API.
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 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 community) with your regular Go code and deploy using the Serverless Framework.
I got a ton of great feedback on my post Securely Chatting Microservices, so I decided to create a video out of it and start a new video series called Flynn in Flight!
Building microservices is awesome, having them talk to each other is even more awesome! But in today’s world, you can’t be too careful when it comes to sending sensitive data across the wire. Last week I was at PubNub for a Meetup where, together with Jordan Schuetz and Nicholas Grenié, we spoke about cool things you can do with PubNub. One of them is using PubNub as a messaging layer to have your microservices, built with Flogo (duh), talk to each other in a secure way. In this post, I’ll go over the steps to build those microservices and hook them up using PubNub.
Building multi-platform event-driven microservices and functions can get complicated fast. In this short webinar hosted by DZone, I cover how to use Project Flogo to build event-driven microservices and functions that target both Kubernetes and AWS Lambda — without losing your mind in the process.
“Serverless” allows developers to focus on writing their code, and a cloud provider, like AWS, takes care of all the other bits. Building serverless apps means the developer doesn’t have to worry about server management, scaling, or high availability, a convenience that usually comes with the added benefit of lower operational cost. We’ll be showing how to use the Project Flogo lightweight integration engine and open source framework to deploy functions to AWS Lambda using SAM.
This post walks through building a Slack bot that responds to a /cat slash command with cat facts. The bot is built with Project Flogo, runs on AWS Lambda, and is exposed through API Gateway. The whole thing takes about 15 minutes to set up.
Serverless has real potential to change how businesses build and architect cloud applications. No provisioning infrastructure, no dealing with maintenance, updates, scaling, or capacity planning — you just upload your apps to AWS and go. This webinar walks through the case for going serverless and what that looks like in practice.
Every developer has that one technology they gravitate toward — whether it’s ESB, open source tooling, or Node.js. The idea behind this webinar was simple: what if you could bring all of that into one place? And you’re not locked into iPaaS for deployment either. You can deploy on-premises, to a private cloud, to devices, or to serverless environments.
