JAMstack or Drupal? - Part I
Why are organizations still building websites on old technology like Drupal or Wordpress these days when there are so many more hip ways to deliver your content?
What's up internet; Tom Friedhof here, a solutions architect here at ActiveLAMP. First off let me start by giving you some background on the problem. Our team here at ActiveLAMP has built some pretty large-scale Drupal sites for organizations such as Riot Games, UCLA, and the Grammys. Sites like these get bombarded with traffic and require significant infrastructure tuning as well as code tuning to make sure that servers that they're hosted on can deliver as many pages per second as possible so that under extreme traffic loads the server doesn't blow up and stop serving traffic to anyone causing an outage. There's a lot of complexity involved to deliver content for high traffic sites like these on traditional server-side applications, like Drupal. For instance, code optimization spending countless hours profiling your code to find slow areas that can be improved to speed up response time. Or implementing a caching strategy so that your code doesn't have to execute as often. If a request comes in that's already been processed the server knows how to handle that. There's also scaling servers horizontally so that you can distribute the incoming load across several servers to keep up with web traffic and also ensure high availability of your site. And if your site is prone to burstable traffic setting up auto scanning to deploy new servers when thresholds are met on the currently launched servers so that your site can continue to deliver content when enormous spikes of traffic hit your infrastructure. There's a lot of complexity involved when delivering content from a traditional CMS like Drupal to serve high loads of traffic.
This concept of building a statically generated site isn't a new thing. Our team has been building static sites for our customers for almost a decade. In fact, if you're watching this video in September of 2020, our current website activelamp.com is built on Jekyll, the pioneer of statically generated sites. In my opinion, the react players in this space are changing the landscape of static sites and making building static sites the new norn. The new activelamp.com site that we're getting ready to launch is built on Gatsby and it's amazingly fast, faster than our current Jekyll static site.
I'm going to answer these questions in part two and part three of this series. In my next video, I'll dive deeper into the questions I presented regarding Drupal coupled, Drupal decoupled, Drupal, or hosted CMS. Part three of this series, I'll talk about the differences between Gatsby and Next.js and when I think it's better to use one over the other.
Make sure that you hit that subscribe button so that you're notified when we release these videos and hit that like button for us. See you in the next video.
Subscribe on YouTube
We update the channel regularly with the latest client work and special event videos.