Let's look at the different serverless options In Azure.
Microsoft offers four different services that can be used for serverless applications.
actual functions and actual up service Web jobs
Logic UPS and Microsoft flow are targeted toe business users and technical users with limited programming skills like pro integrators or I t. Odd means
both logic caps and floor off are in browser designed tool that can be used to design the workforce.
Microsoft Floor is built on top off logic caps, and it's targeted toe nontechnical that users
hence Onley, the designer to is available for building the workforce.
At the same time, logic caps is targeted toe technical users and in addition to the designer, to offer so options to build workforce in visual studio or describing them using Jason.
There are hundreds of tribute connective survivable for logic. Absent floor
logic caps also alos building custom connectors that can be exposed to the flow. Users.
Floor and logic caps have different tools for management
flow Applications can be designed in non production environments and promoted toe prediction when ready, using the flow at mean center.
At the same time, logic caps can leverage the develop stools and national resource manager toe build and deport to different environments
from security. Point of view Flow uses Office 3 65 security tools, while larger caps can be integrated with the azure security tools like security center, azure, audit locks and song
if we are to compare the logic caps with azure functions,
logic caps use designer first approach while functions use code first, the poor approach.
You can develop functions using coal development tools like visual Studio, B s coat or browser based court editor, but there is no designer for functions.
While logic caps allow you to use hundreds of pre build connectors. Azure functions allow you to use just a small set of binding options, but give you higher flexibility to develop custom functionality. To connect toe any application
logic caps have rebuilt actions that you can leverage. Those actions can have multiple activities in them,
as your functions require you to write called forage activity.
While logic APS run Onley in the cloud, you can azure functions on your local machine as well as in the cloud.
To summarize logic, absoluto quickly prototype using pre built building blocks like connectors and activities
But this is at the expense of the flexibility as your functions give you the flexibility to build any functionality but requires programming skills.
Actual wrap service Web jobs allow you to run the script of court in the context of a NAP Service Web. One typical example is to create a trump nail of an image when applauded by the wipe application
Web jobs can use the Web Job says Decay, which is a framework designed to write, called that response to events in national services.
Because, as your functions are built on top of the Web, job says decay functions and the Web jobs share. The same event triggers in connections to other actual services. However, there are some differences between national functions and up service Web jobs. Let's see what those are and what are their similarities.
Both actual functions and AB service. Web jobs Use cold First approach.
Azure functions offer through serverless functionality and can be used with different types of applications. While up service web jobs can only be used in the context of an up service Web application,
actual functions can scare automatically based on the demand, while the AB service web jobs need to be scared together with the Web application
as your functions are built for use, while the building off Web jobs is tied to the APP service weapon apps.
Although built on the same framework, actual functions offer more triggers like HTTP Web hoops and Asher event grip.
Last but not least, azure functions offer more flexibility for choosing the implementation language.
This gives you on good overview of the different server less options that Microsoft offers.