On the other hand, Logic Apps
can enable advanced or mission-critical integrations (e.g. B2B processes) where
enterprise-level DevOps and security practices are required. It is typical for
a business workflow to grow in complexity overtime. Accordingly, you can start
with a flow at first, then convert it to a logic app as needed.
The following table helps you
determine whether Flow or Logic Apps is best for a given integration.+
Flow
|
Logic Apps
|
|
Audience
|
office
workers, business users
|
IT
pros, developers
|
Scenarios
|
Self-service
|
Mission-critical
|
Design
Tool
|
In-browser,
UI only
|
In-browser
and Visual
Studio, Code
view available
|
DevOps
|
Ad-hoc,
develop in production
|
source
control, testing, support, and automation and manageability in Azure
Resource Management
|
Admin
Experience
|
||
Security
|
Standard
practices: data
sovereignty, encryption
at rest for sensitive data, etc.
|
Security
assurance of Azure: Azure
Security, Security
Center, audit logs,
and more.
|
Functions vs. WebJobs
We can discuss Azure Functions
and Azure App Service WebJobs together because they are both code-first integration
services and designed for developers.
These enable you to run a
script or a piece of code in response to various events, such as new
Storage Blobs or a
WebHook request. Here are their similarities:
·
Both are built on Azure
App Service and enjoy features such as source
control, authentication,
and monitoring.
·
Both are developer-focused services.
·
Both support standard scripting and
programming languages.
·
Both have NuGet and NPM support.
Functions is the natural
evolution of WebJobs in that it takes the best things about WebJobs and
improves upon those.. The improvements include:
·
Streamlined dev, test, and run of code,
directly in the browser.
·
Built-in integration with more Azure
services and 3rd-party services like GitHub WebHooks.
·
Pay-per-use, no need to pay for an App
Service plan.
·
Automatic, dynamic
scaling.
·
For existing customers of App Service,
running on App Service plan still possible (to take advantage of under-utilized
resources).
·
Integration with Logic Apps.
The following table summarizes
the differences between Functions and WebJobs:+
Functions
|
WebJobs
|
|
Scaling
|
Configurationless
scaling
|
scale
with App Service plan
|
Pricing
|
Pay-per-use
or part of App Service plan
|
Part
of App Service plan
|
Run-type
|
triggered,
scheduled (by timer trigger)
|
triggered,
continuous, scheduled
|
Trigger
events
|
||
In-browser
development
|
x
|
|
Window
scripting
|
experimental
|
x
|
PowerShell
|
experimental
|
x
|
C#
|
x
|
x
|
F#
|
x
|
|
Bash
|
experimental
|
x
|
PHP
|
experimental
|
x
|
Python
|
experimental
|
x
|
JavaScript
|
x
|
x
|
Whether to use Functions or
WebJobs ultimately depends on what you're already doing with App Service.
When you have an App Service
app for which you want to run code snippets, and you want to manage those
together in the same DevOps environment, then use WebJobs.
If you want to run code
snippets for other Azure services or even 3rd-party apps, or if you want to
manage your integration code snippets separately from your App Service apps, or
if you want to call your code snippets from a Logic app, then take advantage of
all the improvements in Functions.
Flow, Logic Apps, and Functions together
As previously mentioned, which
service is best suited to you depends on your situation.
·
For simple business optimization, then use
Flow.
·
If your integration scenario is too
advanced for Flow, or you need DevOps capabilities and security compliances,
then use Logic Apps.
·
If a step in your integration scenario
requires highly custom transformation or specialized code, then write a
function app, and then trigger a function as an action in your logic app.
You can call a logic app in a
flow. You can also call a function in a logic app, and a logic app in a
function. The integration between Flow, Logic Apps, and Functions continue to
improve overtime. You can build something in one service and use it in the
other services. Therefore, any investment you make in these three technologies
is worthwhile.+
Next Steps
Get started with each of the
services by creating your first flow, logic app, function app, or WebJob. Click
any of the following links:+
+
Or, get more information on
these integration services with the following links:+
No comments:
Post a Comment
if you have any doubts, please tell me