AWS Lambda vs. WP Engine

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.

Incentivized

I am an enterprise user of WordPress and host over 7000 sites with WPEngine. Areas that I think they are well suited for include customers that need enterprise-level support and uptime and have more complex needs than a simple blog. They also manage scale well with a variety of isolated install options that you can scale up or down depending on your contract needs. They also provide premier support for enterprises and have highly knowledgable Technical Account Managers that provide a significant value add. If I were to look at where it isn't as appropriate for usage I would focus on the low-end needs and say while they do support small sites, there are options out there for cheaper hosting that lack the support a WPEngine gives you.

Incentivized

• No provisioning required - we don't have to pay anything upfront
• Serverless deployment - it gets executed only when request comes and we pay only for the time the request is getting executed
• Integrates well with AWS CloudWatch triggers so it is easy to setup scheduled tasks like cron jobs

Incentivized

• I love the database backups and how quickly & easy it is to restore from an old backup point. This gives me & my clients confidence that any change can be rolled back.
• The built in caching & CDN mean that I have to spend less time worrying about the speed of the server & site. The caching has some side-effects that take getting used to (on-page dynamic PHP code sometimes needs to be moved to API endpoints), but this is true for most caching systems.
• They have really good support for multiple environments. It's very easy to have separate production & staging environments. It's also very simple to deploy from staging to production, making product launches and large scale website copy changes much easier to coordinate.

Incentivized

• 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.

Incentivized

• I'd like to see WP Engine offer their own monitoring solution. When I say monitoring, I mean specific use cases that may end up being something you could script. This would keep customers from having to pay for additional services like Pingdom, New Relic, etc.
• I would like to see some proactive analysis done by WP Engine on their customer sites - at least on their home pages, and offer up suggestions. This kind of goes along with the other example.
• Finally, it would be nice to see a "lighter" offering, perhaps a plan that costs $49 for those who want to host only a few sites, or even 1 site.

Incentivized

I was in a situation where I had to bolt Wordpress on to an existing infrastructure that could not support it. If I ever end up in that situation again, please kill me. Other than that reasonably common use case, I don't think it offers a lot of value over robust shared hosting, virtual private server (VPS) or dedicated servers.

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.

Incentivized

From the onboarding and in the days afterward, it was very easy to get into the platform and begin creating important websites and configuring user options. The interface is easy to navigate, and the platform pages load quickly. Since the platform is built for Word plus press, it has features including backup, staging, maintenance mode, and direct WP-Admin login to make configuration and site management faster. We have never had any issues on the billing side of the account.

Incentivized

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.

Incentivized

Support is generally great. Enterprise support is fantastic, with little to no wait times. I find that chat support can almost always take care of the problem without escalating to a ticket for a higher level of troubleshooting. The chat support for many other hosting providers can only handle basic issues. This is a big bonus for us to get quick and helpful answers.

Incentivized

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

Incentivized

While we still use GoDaddy for some services, WP Engine definitely has been a major upgrade for our WordPress hosting. In addition to faster load speeds, WP Engine has been more adept at allowing us to manage a high number of websites without straining the system. We have never used Network Solutions for our own hosting needs, but when we do interact with them on behalf of our clients, their systems always seem to be clunky and hard to use, and they often overcharge customers by selling them products they do not need.

Incentivized

• 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.

Incentivized

• WP Engine reduces our time investment and upkeep costs which increases our margins.
• WP Engine simplifies site management with a built-in development server, which saves us headaches.
• WP Engine itself is positioned as a premium service, which allows us to use their branding as a tool to close sales.

Incentivized