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
Joomla
Score 8.3 out of 10
N/A
Joomla! is a free and open source content management system used to publish web content. Included features are page caching, RSS feeds, printable versions of pages, news flashes, blogs, polls, a search function, and support for language internationalization.
N/A
Pricing
AWS Lambda
Joomla!
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
Joomla
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
Joomla!
Features
AWS Lambda
Joomla!
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.
If your developers want to have some fun, Joomla offers the stability and friendliness to do custom coding. Certain marketing initiatives require us to get "cute" with the interface, and Joomla allows for that a bit easier than WordPress (and definitely easier than sites like Squarespace). The security of Joomla is also always a plus.
Security. Its got many new features in the new Joomla! 4 which make the already good security even better. I like the ability to use my Yubi keys to log in with the new webauth standard, I don't think any other CMS has that built in
W3C Accessibility Guidelines (WCAG) 2.1 (with AA compliance)
Really good SEO that gets our sites to the top of the search engines again without the need for any extra things
Speed, it gets a really good score (100%) in the google lighthouse on our server, can't beat that
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.
Because Joomla's user community is smaller than WP, it lacks as many choices from 3rd party developers, meaning it can be a little more difficult to find the right extension for what you need to accomplish
Along the same vein, most of the best 3rd-party software for Joomla! is paid
Simple features such as Add to Menu and Cache cleaners should be adopted as part of the Joomla! core, though they are available as extensions
Joomla! could use a simpler and easier URL rewriting process
I gave it a rating of 10 because I just love how Joomla! works, how it is set up and how it handles many users. Also it is very fast, and there is no overload on the MySQL database or servers ever.
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.
Joomla! 3.x is easily installed either manually or via a script provided by your host. It contains most of the tools needed to begin creating websites right from the start. Those features that it doesn't have are easily installed via links and buttons from the thousands of extensions available in the community
Today's Modern Joomla performs very well and is robust and durable. The pages load faster than they ever did in the past and Modern Joomla's integration into other software or systems has become seamless. Modern Joomla sites will last long and will stay running forever.
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.
Between the core Joomla developers who are excellent at answering questions and providing support, you have a whole community of developers who work with Joomla and are happy to help fellow developers out answering questions and supporting the Joomla project. Out of the many communities I am involved in for open-source software, Joomla's community is by far the best.
Joomla has gone through tremendous growing pains. It is now better than ever. But before, when it was going from 1.5-2.5, the templates and plugins would break over and over again. If you don't understand what Joomla was trying to do back then, you might have a bad attitude toward it. Today, those pains are over and things don't break like they used to during that time period.
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 tested other platforms like WordPress, Magento and some local CMS. But Joomla offered us better resources for generating content. Joomla is a CMS suitable for many types of projects, especially if you have several people editing content at the same time. It allows you to maintain visual standardization and offers many options for working with images. With its ability to control access to different articles, categories or even different components, it is a great tool, even if they are managed by different people.
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.