Today I spoke at a Meetup group to discuss the Go Programming Language. Together with an awesome colleague (Miguel Torres) we spoke about Project Flogo and the lessons we learned building it. Click on the link to check out the talk on YouTube.

This year I wasn’t able to attend re:Invent, but I did want to do something nice in between the live streams and specifically around Serverless compute and AWS Lambda. Lambda lets you run code without provisioning or managing servers. You pay only for the compute time you consume - there is no charge when your code is not running.

With Project Flogo you can visually create Ultralight Edge Microservices and run them anywhere. But what if you want to run those incredibly light microservices using one of the most powerful container management platforms, Kubernetes? As described on the Kubernetes website Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications.

The explosion of SaaS as the typical acquisition pattern for enterprise software means that any given organization has (or will have) dozens of apps to connect to each other. In fact, the average Marketing department uses about 30 different SaaS apps, and the average HR department…

Last month TIBCO added the ability to add custom activities to TIBCO Cloud Integration - Web Integrator ( I’ll use Web Integrator going forward). The Web Integrator experience is “Powered by Project Flogo”, so when you create your own extensions for Web Integrator, and use them in every flow that you want, those activities will work with Project Flogo as well.

Back in 2012, the engineering team at Heroku created a set of best practices to develop and run web apps. That document, consisting of 12 incredibly important ‘rules’, was dubbed the 12 Factor App manifesto. Over the years the document gained a lot of traction and especially with the rise of microservices having a 12 Factor App compliant app became important. With the rise of microservices a lot of other practices and tools (like git, DevOps, Docker and Configuration Management) became very popular as well.

Pretty much all the large cloud platforms provide not only a great visual interface to get things done, they also have a great command line interface. As much as I love a great UI when browsing the web, I do tend to favor the command line interfaces when I’m focusing on developing things.

In 2016 TIBCO announced Project Flogo as an ultra lightweight integration engine. It is the lightest way to connect IoT devices being up to 20 to 50 times lighter than Node.js and Java® Dropwizard. Project Flogo was made available as Open Source Software because TIBCO believes there is a better way to integrate IoT devices. With it being Open Source and easily extensible, you want to make sure that the activities you build remain working after each check in on GitHub. These are a lot of words to say “How can I test my activities every time code is pushed to Git”?

Over the past few weeks I’ve gotten many questions on how to use Basic Authentication with the new Web Integrator in TIBCO Cloud Integration. It is really easy to do that!

In the age of large monolithic apps and app servers, it was not too difficult to monitor the status of your application as well as some more detailed monitoring of transactions. In today’s age of microservices, that whole monitoring thing is getting more and more complex. You not only have to deal with a bunch of more servers, you also have to deal with more (micro)services. You have different options depending on what you want to monitor. For example, you can use Nagios, Zabbix or Prometheus. My personal preference goes out to Greek deity that stole fire from Mount Olympus and brought it to us.