One of the more consistent problems faced by service management is transparency of billed hours and a lack of automation. Currently in Deloitte Operate, we leverage Jira Tempo to keep track of our clients’ billed hours and current utilisation levels. 

Lack of transparency comes from the inability of the customer to...

In the previous post of the series, I described how messages can be transmitted from a sender application to intended receiver applications through Messaging Channels, and how the Azure Integration Services can be leveraged to implement these Enterprise Integration Patterns. Messaging Endpoints are the application...

In the previous post of the series, I covered how application data are to be serialised and packaged into messages so they can be transmitted between applications. In this post, I’ll describe the Messaging Channels patterns, which focus on solving the challenges of transmitting messages from a sender application to...

When we are designing a message-based integration solution, one of the first things we need to define is how the application data are going to be serialised into messages, so they can be transmitted to other applications. The Message Construction Enterprise Integration Patterns provide documented knowledge that can...

In January 2019, Azure Functions Team has released a new version of its runtime, 2.0.12265.

I wasn’t able to believe what that meant at the first place.

Does that mean we now can get rid of the infamous static modifier from both classes and methods?

In fact, Fabio from Azure Functions Team showed a demo at Ignite...

Introduction

If you are reading this post, chances are that you know that things can go wrong and thus logging can be very useful when a solution is in production to monitor or troubleshoot it. But, not all logs are equal. While you can have enough information available, unstructured logging can be hard to read,...

Introduction

Azure Durable Functions have support for different patterns, which enable us to build serverless and stateful applications without worrying about the state management implementation details. One of these useful patterns is the Asynchronous Http APIs. This pattern comes in handy when client applications...

Introduction

Azure currently has two service offerings of serverless compute: Azure Logic Apps and Azure Functions. Until recently, one could argue that Azure Functions were code triggered by events while Logic Apps were event-triggered workflows. However, that changed after the release of Azure Durable Functions...

Introduction

This is a post part of a series of implementing serverless approval workflows on Azure:

1. Approval Workflow on Logic Apps with Twilio
2. Approval Workflow on Azure Durable Functions and SendGrid
3. Approval Workflow on Azure Durable Functions and Slack (this)

Recently, I published a post about implementing an

Introduction

This post is part of a series about implementing serverless approval workflows on Azure:

1. Approval Workflow on Logic Apps with Twilio
2. Approval Workflow on Azure Durable Functions and SendGrid (this)
3. Approval Workflow on Azure Durable Functions and Slack

Durable Functions is a new (in preview at the time...