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
Oracle Integration (OIC)
Score 7.0 out of 10
N/A
The Oracle Integration Cloud Service is an iPaaS providing prebuilt integration flows between applications, including other Oracle products. The Integration Cloud Service is scaled for enterprises, with prebuilt codeless adapters for on-premises and SaaS systems and low-code automation capabilities.
N/A
Pricing
AWS Lambda
Oracle Integration (OIC)
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
Oracle Integration (OIC)
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
AWS Lambda
Oracle Integration (OIC)
Features
AWS Lambda
Oracle Integration (OIC)
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.
For all type of integration except those with a huge volume. It can deal with 20MB of transactions and processing of 1GB file when a file is being read using file or FTP adapters. It cannot be used for EDI as this support is not there. OICS is a perfect fit for other integration and is best when a customer has Oracle applications in the landscape. It is even greater if you have a requirement to create a custom form and make use of Process Cloud. All of these work very well together seamlessly. API needs can be handled by APIary.
Auto-association of Oracle applications prepopulates the application connector select box and preconfigures Oracle Integration (OIC) using secure credential access for faster integration.
Various other system connectors are available to use readily.
User-intuitive experience--Connectors, integrators, and dashboard can be seen on one page.
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.
Currently, it is not retaining the logs for more than 3 days, which it needs to address.
We also need some functionality inside the interface to re-push the same transaction again so that it will be helpful while testing and fixing the issue.
Also, some log errors are not giving the correct details. Oracle needs to rectify those.
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
The nearest thing I have used to OIC is UiPath, as it is often used as a tool to integrate software together. However, it is much more suited to legacy software which have little to no API endpoints. If the infrastructure already exists I understand why people use RPA for integration, however for when API's are easily accessible and you're using Oracle tools, OIC is better.
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.
Created a solution for unique business integration with minimal processing times
Saves my team about 7 hours per week because of how it communicates with all the information. Because it communicates faster, and because there's a lot of information to communicate with, another solution might not work.
