-
Notifications
You must be signed in to change notification settings - Fork 2
Choosing between Lambda functions and activities
Gurmit Teotia edited this page Jan 1, 2020
·
4 revisions
This document is a work in progress:
Features | Lambda functions | Activities |
---|---|---|
Access to specialized hardware | In Lambda function you can't access specialized hardware (e.g. GPU) | In self hosted activities you can have access to specialized hardware |
Cancel the running task | Not available | You can cancel a running activity |
Timeout the running task | Available, you can configure the Lambda function to finish within a specific period | Available |
Scalability | Available, out of the box | You have to put the efforts to start/stop additional workers |
Human approvals | Available, Guflow provides intuitive signal API to support human approvals | Available |
Choice of programming languages | You can write the Lambda functions in good number of programming languages | Guflow provides you rich APIs to develop the activities. Hence your first option will be .NET. |
Cost |
Guflow
- Prerequisite
- Installation
-
Workflows
- Creating first workflow
- Registration
- Hosting
- Start workflow
- Schedule activities
- Schedule timers
- Schedule lambda function
- Schedule child workflows
- Lambda functions vs activities
- Workflow input
- Workflow actions
- Signals
- Workflow branches
- Deflow algorithm
- Workflow events
- Query APIs
- Custom polling strategy
- Things to take care of
- Activites
- Unit testing
- Performance & scalability
- Error handling
- Logging
- Debugging
- Tutorial
- Release notes