The applications we build and the systems we run generate a massive amount of logging data ranging from alerting, monitoring, availability and performance. Analyzing logs, or log analytics, is a widespread practice to capture insights from mobile data, IoT devices, servers, websites and other sources. Most companies need programmatic access to this massive amount of […]
IBM Cloud Functions offers great flexibility when it comes to using events to invoke your Actions. Scheduled events are cloud native events you can programmatically control when they need to fire to run your serverless apps, instead of allocating an idle server just to schedule a job, you can use IBM Cloud Functions to orchestrate […]
For my tutorial on automated data retrieval and analytics, I use IBM Cloud Functions to automatically fetch GitHub traffic statistics once a day. It is implemented as a serverless Python action. Because some Python packages are needed, the question was how to pack and create the action. In this blog post, I share my experiences.
In serverless applications, functions are small and need to execute in less amount of time in a stateless environment. Logging then becomes a challenge for DevOps to do Root Cause Analysis (RCA) or get insights about the behavior of their applications. One logging approach is to add code to your functions to send logs to an external API, which can be a […]
If you work with Cloud Functions, you know that building serverless applications mainly happens by creating actions–small pieces of code that each do one thing well. You can of course sequence actions together or create event-driven workflows. Through our work with customers, we have realized that some scenarios (for example, image processing, file processing, data pipelines) require more time […]
In a serverless application platform, functions as a service (Faas) run opaquely for the most part. In general terms, when a serverless function is invoked, the platform accepts the request and provisions resources before it executes the function. Let’s refer to the duration between accepting the request and the start of the function execution as the […]
Recently, I introduced you to a new tutorial for a database-driven Slackbot. Today, I am going to discuss security details, how the IBM Watson Conversation service is accessing a Db2 Warehouse service from within a dialog. It uses a serverless setup with IBM Cloud Functions. All the necessary credentials to execute the code and to access the Db2 database are automatically bound. Hence, the function code and the dialog don't need any account-specific changes and are generic.
Ever wanted to build a Slackbot, a chatbot integrated into Slack, on your own? I am going to show you how easy it is to integrate Slack or Facebook Messenger with the IBM Watson Conversation service. As a bonus, the bot is going to access a Db2 database to store and retrieve data. The code in the tutorial uses a serverless fashion with IBM Cloud Functions.