Comments on: Does Serverless WordPress Make Sense? Shifter vs HardyPress – Top “Headless WordPress Hosting” Options Compared https://wpshout.com/serverless-wordpress-shifter-vs-hardypress-top-headless-wordpress-hosting-options-compared/ A hub for advanced WordPress users, developers & savvy business owners. Wed, 11 Oct 2023 18:32:00 +0000 hourly 1 https://wordpress.org/?v=6.4.3 By: Sparx BPO https://wpshout.com/serverless-wordpress-shifter-vs-hardypress-top-headless-wordpress-hosting-options-compared/#comment-15039 Fri, 19 Oct 2018 06:12:50 +0000 https://wpshout.com/?p=39360#comment-15039 In reply to David Bennett.

I dont think so, it is possible mate.

]]> By: Thomas Bacon https://wpshout.com/serverless-wordpress-shifter-vs-hardypress-top-headless-wordpress-hosting-options-compared/#comment-14994 Fri, 12 Oct 2018 13:31:29 +0000 https://wpshout.com/?p=39360#comment-14994 Thanks for the detailed rundown, but I think that you’ve conflated a number of sometimes related, but distinct, concepts. “Static” sites, “headless” WordPress, and “serverless” architectures are very different things.

“Headless” WordPress refers to the decoupling of the WordPress backend from the the traditional frontend. Often it’s used to refer to building a JavaScript app / frontend and using the WordPress API to connect to that frontend. While a static site might be considered headless, it’s kind of a stretch in my opinion, since the statically generated site is simply a copy of the WordPress site as it was output using a traditional WordPress theme.

“Serverless” on the other hand, just means using third-party app services to run your application, rather dealing with MySQL server, operating system, memory, storage, etc… Basically, letting someone else deal with the infrastructure while you just build the application on it.

I love the appeal of a static WordPress site, and in some cases as you point out it can work, but in my experience as sites grow they require features that make using a static site unrealistic. A properly managed WordPress site with aggressive page caching and properly secured is the way we usually go.

]]> By: David Bennett https://wpshout.com/serverless-wordpress-shifter-vs-hardypress-top-headless-wordpress-hosting-options-compared/#comment-14996 Fri, 12 Oct 2018 10:50:59 +0000 https://wpshout.com/?p=39360#comment-14996 For a suitable site I can only think of one solid reason to want to go from WP to static and that is if the potential vulnerabilities in WP are kept away from being exploited because they are not forward facing. If that’s the case then it takes the pressure off the site owner to continually do the rounds updating stuff on multiple sites. So, is that the case – is the code protected more than in a straightforward WP site?

]]>