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 APEX
Score 8.2 out of 10
N/A
Oracle APEX (or Oracle Application Express) is an online low-code application builder that allows users to develop a database-drive application, customize the application's UI, and then give their users access to the application via URL. Oracle APEX includes a suite of pre-built productivity applications and examples, such as a Survey Builder, Bug Tracking, P-Track project management, etc
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.
Based on our organization's experience, Oracle APEX is a versatile and powerful tool, but its suitability depends on specific business needs, technical requirements, and the nature of the application being developed. Scenarios where Oracle APEX fits well: Business Process Automation/Workflows Reporting and Dashboards for Data Analytics AI based systems such as Select AI Chatbots for data insights based on LLMs Native-like Mobile Applications using PWA feature of APEX Scenarios where Oracle APEX may be less appropriate: Very Complex and highly interactive applications Use cases based on a non-oracle Database
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.
Can't think of any - the Application Express development team does a fantastic job adopting and supporting emerging trends with each new release.
Requires Oracle RDBMS; i.e., is not portable to other RDBMS platforms. On the surface this may seem like a con but it is as it should be - Oracle database is best RDBMS available and tight integration with Oracle RDBMS promotes creation of reliable performant apps.
I felt very comfortable using Oracle Application Express from the start. I designed my data model and quickly developed the basic CRUD pages for master tables. Then I designed the main functionality and was able to test and deploy it in a couple of days work. I will probably share the app with other members of the team and continue adding some features in the short term.
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.
its easy to use as a developer and applications designed using apex are easy and intuitive to use as an end user. Even non-coders can build good applications, the more code you can write the more you can enhance the application but you can get up and running quickly with almost no technical know how.
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.
Very active and knowledgeable community support includes quick and helpful responses from the Oracle employees on the product development team. I've never had to raise an official support request - everything is dealt with via forums and user groups - or via direct emails. The supposrt commuinty is one of the great things about Apex.
Using it on the cloud is really simple, the entire process of configuring and provisioning an Oracle Database takes only a few minutes (less than 10) and then Oracle APEX is already deployed on the database, so you just have to start using it. I would strongly recommend using APEX on Oracle Cloud Free Tier.
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
If you are expert in SQL and PLSQL and use Oracle Database, then the best choice is Oracle Application Express. The functionality is already complete and very easy to use, so it's useless to find another tool if you are using Oracle. You don't use Oracle APEX only if: (1) you are using other database than Oracle, and (2) your application load is unpredictable.
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.
In the mid-size organization, we had a BI tool that had a significant license cost involved. With Oracle back-end we were able to switch to APEX and move all reporting at literally zero cost.
For Oracle PL/SQL users the learning curve is very quick and easy, there are ready templates that you can start with and eventually create complex reports.
You can track authorization and authentication on data editing and usage. High performance as it is native oracle sql codes.
Centralized data capturing, makes your datawarehouse writable for lookup tables or reference tables.
