Integration

In this session, Chris is joined by Karl Cooke, Blogger at https://irishtechie.com. Chris and Karl talk all about the CloudWithChris.com integration platform, and the numerous automation/integration activities that Chris has in place to save time and focus on building content!

Back in June, I wrote a blog post on API Management and how you can use API Management policies to enforce access restriction policies. I was going to write a follow up post on how to use API Management policies in additional scenarios, but it’s one of those scenarios where great minds think alike!

I’ve written blog posts previously around Azure Service Bus vs Azure Storage Queues, as well as an introduction to Azure Logic Apps and how I used it at the time. Back then, my use-case was fairly rudimentary and focused on a specific scenario. In this blog post, I explain the changes that I have made and how I’ve used common cloud design / integration patterns to implement a more robust solution.

I’ve recently been involved in a few integration focused discussions, where there is a requirement to bring together multiple separate systems. If you’ve been following the Architecting for the Cloud, one pattern at a time series, then you’ll have heard Peter Piper repeat a common phrase - ‘High Cohesion, Low Coupling’.

We recently introduced you to API Management, how it maps to architectural principals and why you may consider using it as a producer or consumer of APIs. In this post, we’ll be continuing on the story - focusing mostly on the API Management policies functionality.

We now live in a world where multiple systems connect or integrate with each other. This is not new, and has been a technology trend for some time. But - in a world of distributed compute (on the increase, thanks to cloud), and the rise of microservices, we find that we have more and more services that we need to integrate with each other. Integration is typically handled through a couple of routes, including Enterprise Messaging (such as message brokers), as well as APIs (Application Programming Interface). There are many areas that we should consider when building our APIs, and that’s what we’ll give some thought to in this blog post.

Have you heard about Azure Event Grid, but not exactly sure what it is or how you could use it? In this Cloud Drop, we’ll create an event-driven process using Azure Event Grid, Azure Storage Queues and Azure Functions. Get ready to learn all about Event-Driven workflows, Event-Handlers, Topics, Subscriptions and more!

You may have heard of Event-Driven Architectures before, but haven’t had the chance to get hands-on and build one as yet. That’s exactly what we’ll be working through in this blog post!

Serverless computing is a cloud computing code execution model in which the cloud provider fully manages the infrastructure needed to serve requests. In this session, we will explain why and how we should use Azure Functions and PowerShell together, and we will show you how to deploy a PowerShell based Function. In some live demos, we will explain how to create a Function and execute some cool PowerShell code!

Following hot off the heels of my recent blog post introducing Logic Apps and how I use the technology on cloudwithchris.com, I thought it made sense for the second post to continue the Logic Apps theme. This time, we’ll be focusing on Logic Apps preview (sometimes referred to as Logic Apps v2) - the evolution of Logic Apps. Typically when you deploy Logic Apps, you deploy it as a multi-tenanted service. There are some benefits to that, including the serverless capability, so being able to pay per execution rather than an overall infrastructure cost. But what if cost is less of a requirement for you? What if you care more about portability, greater performance, and ultimately control over your environment? If those are more along the lines of your requirements, then you may want to investigate the Logic Apps previewhttps://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-overview-preview. The Logic Apps preview builds upon the Azure Functions extensibility model. Yes, you read that right - Azure Logic Apps is effectively building on top of Azure Functions. Why should you care? Anywhere that Azure Functions can run, then Logic Apps can run.