Azure Logic App Service or simply Logic Apps are a great integration and workflow orchestrator. Think of IFTTT for the enterprise (and for non-enterprise projects of course). Logic Apps, like Azure Functions, offer a great set of tools which are built-in on the Azure portal. These tools allow you to create, run and monitor your integration workflow using a variety of connectors, conditions and actions. When creating Logic Apps in the portal you have the option to switch between the designer and the code editor with ease. However, a web browser is not the best medium for development and collaboration. …[read more]
Showing all posts tagged: 'Azure'
A 38-post collection
Last week I published an article on Serverless architecture on Azure. The post can be found on the Simple Talk website and I was honoured to be invited to have my piece published. You can read all about it here: https://www.simple-talk.com/cloud/cloud-development/serverless-architecture-azure/ Feel free to leave a comment here or at Simple Talk. …[read more]
Last week I started a mini-series that focused on [Azure Functions and DevOps. The tooling is still being worked and in the interim we need a solution in order to do proper CI/CD with Azure Functions. In this post we're looking into how to deploy Azure Functions using ARM Templates only. That's correct. This is a one stop solution but requires that you include your function code inline to the ARM JSON template. This is somewhat undocumented and I had to figure out how do it with help from the Azure PG (product group). The good parts Obviously this …[read more]
You can tell I'm working on Azure Functions from the frequency of posts. This one focuses on logging. Functions by default generate plenty of logs which you can view in the portal or download using the Kudu REST API. This is great and it comes out of the box without you having to configure a single thing. However, what if you have some custom, complex logic that you want to capture and log. And I guess that in most instances there will be more than one Function per AppService and potentially a lot more applications and services deployed on Azure. …[read more]
This approach is by far my preferred and favourite. Ok, it's not perfect but I believe that it provides the most open source, versatile and flexible way to deploy your functions using any tool and any platform. This one does not require you to install any special tools other than the Azure CLI on your build server. In this step, rather than trying to do everything from one file, i.e. the ARM template, I decided to go with the 2 step approach: Deploy the ARM template with the Application Service and Function(s) structure Deploy the Function(s) code. …[read more]
Azure Functions is Microsoft's answer the serverless architecture. They are very popular due to the incredible integration they provide with Azure Services, SaaS providers and on-premise application. It definitely drives the whole microservice architecture design which is built on top of Azure's established Platform-as-a-Service. And enables developers to think about APIs and integration in a totally different way - serverless (even though there are still servers under the hood). It's even more exciting seeing so many organisations embarking in larger scale projects that take advantage of Functions and LogicApps. If you want to know more about the whole serverless design, …[read more]