AWS Lambda is a serverless computing platform that lets users run code without provisioning or managing servers. With Lambda, users can run code for virtually any type of app or backend service—all with zero administration. It takes of requirements to run and scale code with high availability.
$NaN
Per 1 ms
OpenText MBPM
Score 7.2 out of 10
N/A
OpenText acquired BPM solution Metastorm in 2011, and has rebranded the product as OpenText MBPM. It is an alternative BPM solution to OpenText's primary BPM offering called OpenText Cordys Business Process Management.
N/A
Pricing
AWS Lambda
OpenText MBPM
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
No answers on this topic
Offerings
Pricing Offerings
AWS Lambda
OpenText MBPM
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Lambda
OpenText MBPM
Features
AWS Lambda
OpenText MBPM
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
Lambda excels at event-driven, short-lived tasks, such as processing files or building simple APIs. However, it's less ideal for long-running, computationally intensive, or applications that rely on carrying the state between jobs. Cold starts and constant load can easily balloon the costs.
Metastorm is well-suited for scenarios in which internal stress testing an application is needed in a hurry before showcasing it to potential customers. It supports different views of the process from Swimlane perspective, so different methodologies can be handled. It is an Enterprise level tool and handles both small and large projects quite well, although smaller companies may be stressed out by the amount of time it takes to properly maintain the application.
Developing test cases for Lambda functions can be difficult. For functions that require some sort of input it can be tough to develop the proper payload and event for a test.
For the uninitiated, deploying functions with Infrastructure as Code tools can be a challenging undertaking.
Logging the output of a function feels disjointed from running the function in the console. A tighter integration with operational logging would be appreciated, perhaps being able to view function logs from the Lambda console instead of having to navigate over to CloudWatch.
Sometimes its difficult to determine the correct permissions needed for Lambda execution from other AWS services.
The Metastorm process engine is based on an older version of .NET. Updating to a newer version would resolve several known issues with .NET email functionality.
Metastorm builds web pages at run time. While the UI presented to the end user is fine, the Document Object Model is convoluted and subject to change with new releases. Providing a more simplified DOM or at very least a custom function to replace document.getElementById() would make client-side scripting a much more powerful tool.
One function that I've seen Metastorm competitors do well, is email wizards. Having a WYSIWYG email editor would be really nice.
I give it a seven is usability because it's AWS. Their UI's are always clunkier than the competition and their documentation is rather cumbersome. There's SO MUCH to dig through and it's a gamble if you actually end up finding the corresponding info if it will actually help. Like I said before, going to google with a specific problem is likely a better route because AWS is quite ubiquitous and chances are you're not the first to encounter the problem. That being said, using SAM (Serverless application model) and it's SAM Local environment makes running local instances of your Lambdas in dev environments painless and quite fun. Using Nodejs + Lambda + SAM Local + VS Code debugger = AWESOME.
Amazon consistently provides comprehensive and easy-to-parse documentation of all AWS features and services. Most development team members find what they need with a quick internet search of the AWS documentation available online. If you need advanced support, though, you might need to engage an AWS engineer, and that could be an unexpected (or unwelcome) expense.
AWS Lambda is good for short running functions, and ideally in response to events within AWS. Google App Engine is a more robust environment which can have complex code running for long periods of time, and across more than one instance of hardware. Google App Engine allows for both front-end and back-end infrastructure, while AWS Lambda is only for small back-end functions
We found that OpenText MBPM held its own quite well against IBM BPM. We ended up choosing OpenText MBPM due to the analytics, complex routing, and the ease of SOA service integration. Furthermore, the ability to quickly develop simple User interfaces make this tool a daily component of our most-used toolbox components.
Positive - Only paying for when code is run, unlike virtual machines where you pay always regardless of processing power usage.
Positive - Scalability and accommodating larger amounts of demand is much cheaper. Instead of scaling up virtual machines and increasing the prices you pay for that, you are just increasing the number of times your lambda function is run.
Negative - Debugging/troubleshooting, and developing for lambda functions take a bit more time to get used to, and migrating code from virtual machines and normal processes to Lambda functions can take a bit of time.
