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
WordPress
Score 8.6 out of 10
N/A
Wordpress is an open-source publishing platform popular with bloggers, and a content management system, known for its simplicity and modifiability. Websites may host their own blogging communities, controlling and moderating content from a single dashboard.
$3
per month 6 GB storage
Pricing
AWS Lambda
WordPress
Editions & Modules
128 MB
$0.0000000021
Per 1 ms
1024 MB
$0.0000000167
Per 1 ms
10240 MB
$0.0000001667
Per 1 ms
Personal
$4
per month 6 GB storage
Premium
$8
per month 13 GB storage
Business
$25
per month 50 GB storage
Commerce
$45
per month 50 GB storage
Enterprise
Contact for pricing
Offerings
Pricing Offerings
AWS Lambda
WordPress
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
—
Pricing for Business and Commerce plans vary on number of GB.
More Pricing Information
Community Pulse
AWS Lambda
WordPress
Features
AWS Lambda
WordPress
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.
Wordpress is a great solution for a website of nearly any type. It may not be as suitable if a fully custom solution or app is needed, and it does have some limitations when it comes to connecting it to external products (especially if the product doesn't have any support from a native system), and it does require a lot of testing. Multiple plugins in one install are common but also increase the risk of conflicts, and when those do occur, it can be exceptionally time-consuming and tedious to identify what is causing the issue. As third parties create many plugins, you're also at risk with each potential security breach, which needs to be kept in mind. I would be cautious to use WordPress to store any sort of sensitive PPI. That said, it's a wonderful, easily customizable solution for many, many different types of websites and can allow even inexperienced client users with low-tech knowledge to update basics.
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.
WordPress breaks often so you need to have someone who understands how to troubleshoot, which can take time and money.
Some plugins are easier to customize than others, for example, some don't require any coding knowledge while others do. This can limit your project if you are not a coder.
WordPress can be easily hacked, so you also need someone who can ensure your sites are secure.
The complications we have and the lack of support. Every plugin has a differente team of support in charge and make one plugin work with the other one always affects the website performance. It's a thousand times better to have only one provider with all functionalities included unless you are an expert web developer or have a team dedicated to it
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.
Extremely easy to use and train users. It took very little time to get everyone trained and onboarded to start using WordPress. Anytime we had any issues, we were able to find an article or video to help out or we were able to contact support. The menu options are well laid out so it is easy to find what you are looking for.
Anyone can visit WordPress.org and download a fully functional copy of WordPress free of charge. Additionally, WordPress is offered to users as open-source software, which means that anyone can customize the code to create new applications and make these available to other WordPress users.
Mostly, any performance issues have to do with using too many plugins and these can sometimes slow down the overall performance of your site. It is very tempting to start adding lots of plugins to your WordPress site, however, as there are thousands of great plugins to choose from and so many of them help you do amazing things on your site. If you begin to notice performance issues with your WordPress site (e.g. pages being slow to load), there are ways to optimize the performance of your site, but this requires learning the process. WordPress users can learn how to optimize their WordPress sites by downloading the WPTrainMe WordPress training plugin (WPTrainMe.com) and going through the detailed step-by-step WordPress optimization tutorials.
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.
I give this rating, which I believe to be a great rating for a community based support system that's surrounding it. Most platforms and products have their own, and as WordPress does have their own team that help here and there, a lot of it's handled by community involvement with dedicated users who are experts with the system who love to help people.
Varies by the person providing training. High marks as it's incredibly easy to find experienced individuals in your community to provide training on any aspect of WordPress from content marketing, SEO, plugin development, theme design, etc. Less than 10 though as the training is community based and expectations for a session you find may fall short.
WordPress is not a great solution if you have: 1) A larger site with performance / availability requirements. 2) Multiple types of content you want to share - each with its own underlying data structure. 3) Multiple sites you need to manage. For very small sites where these needs are not paramount, WordPress is a decent solution
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
WordPress isn't as pretty or easy to use as certain competitors like Jimdo, Squarespace or HubSpot, but it makes up for it with its affordability, familiarity and the ability to find quality outside help easily. The same can't be said for certain competitors, as you might need to find an expert and it could get costly.
WordPress is completely scalable. You can get started immediately with a very simple "out-of-the box" WordPress installation and then add whatever functionality you need as and when you need it, and continue expanding. Often we will create various WordPress sites on the same domain to handle different aspects of our strategy (e.g. one site for the sales pages, product information and/or a marketing blog, another for delivering products securely through a private membership site, and another for running an affiliate program or other application), and then ties all of these sites together using a common theme and links on each of the site's menus. Additionally, WordPress offers a multisite function that allows organizations and institutions to manage networks of sites managed by separate individual site owners, but centrally administered by the parent organization. You can also expand WordPress into a social networking or community site, forums, etc. The same scalability applies to web design. You can start with a simple design and then scale things up to display sites with amazing visual features, including animations and video effects, sliding images and animated product image galleries, elements that appear and fade from visitor browsers, etc. The scaling possibilities of WordPress are truly endless.
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.