This is the first in a series of 12 blog posts on Azure Enterprise Integration.
Each blog post is accompanied by a video that covers the same content.
It’s been nearly 9 months now since Logic Apps went GA, and there’s starting to be real growth in adoption and usage. We’re also seeing a lot more community content, as developers and companies start to see the real benefits of cloud integration and, specifically, the use of Logic Apps.
But for all this, there is a lot that is missing. If you’re new to Logic Apps, especially if you’ve come from a more formal development background (e.g. BizTalk or C# development) you’ll notice that there’s not a massive amount of development or pattern guidance out there.
For our purposes, we’ve defined Enterprise Integration Development as development that:
Let’s assume you’re a BizTalk developer: You’re used to how BizTalk development works.
For example, some of the tasks you perform may include:
And if you don’t know how to do any of the above, you’ll be able to easily find out online, or look in one of the many BizTalk books.
Now compare this to Azure Integration Development. If you’re new to Logic Apps, you’ll find that it’s not clear what the equivalents to the above steps are: Cloud development in Azure works differently.
Azure integration development also introduces a series of unique challenges that we didn’t have with local development.
5. How we’ll address these questions and issues
This series of videos and blog posts aims to answer most of those questions and address these issues, by providing guidance on how to develop integration solutions in Azure. It’s based on our experience, at Affinus, on working with Logic Apps and Azure integration for over a year, both internally and for our clients.
If you’ve been using BizTalk for a while, you might remember that when BizTalk 2004 first came out, there was very little guidance or patterns or conventions. But then the BizTalk 2004 Unleashed book came out, and the Bloggers Guide to BizTalk was released, and then various forums and blog posts appeared, and developers gained experience and gradually a network of community content and support appeared.
The same will happen with integration development in Azure: we’re at the early exciting stages of integration PaaS development, and what’s more, Microsoft have moved to a new agile model where new features and capabilities are being released on a 2-weekly cycle.
Whether you’re a single developer, a small-medium business, or a large enterprise, Azure integration has a lot to offer.
This series is all about practical examples and samples, hence the video webcasts.
In this series, we’ll be creating a moderately complex integration application that will consist of the following:
Powered by: newtelligence dasBlog 2.3.12105.0
The opinions expressed herein are my own personal opinions and do
not represent my employer's view in any way.
Theme design by Jelle Druyts