Introducing my Jamstack

All Posts

Introducing my Jamstack

Updated: April 1, 2018 by Tony Alves

Update: Although my original site at used this configuration, I'm now using Gatsby. Still valid though. I'm a proponent for using what works for your use case.

Technologies Used for Site

  • React
  • React-Static
  • React-Redux
  • Firebase/Firestore
  • Material-UI (React Components)
  • Netlify (Hosting)
  • Netlify CMS (Custom Build)
  • Webpack
  • NodeJS

How it "stacks" up

This stack can be dubbed as an example of a Jamstack site.

J = Javascript
M = Markdown

The Jamstack has proved to be quite the setup for a site that wants speed and simplicity. The simplicity is not in the development. Simplicity is in the developer experience. If you have had the opportunity to build a static site, you understand the benefits right away. Until lately, static sites were not very complex at all. Today that complexity has come in the behind the scenes structure of how they are built and maintained. This complexity is very well received by the development community, because it's straight forward and recognizable.

Benefits of the Jamstack

  • No Servers to maintain
  • Great Performance
  • Higher Security
  • Cheap to almost free for most hosting
  • Incremental change control
  • Hacking becomes a mute point and limited security issues
  • Content can live in the same place as code
  • Not tied to any one service or tool
  • Rollbacks become instantaneous
  • Global scale for everyone, not just those with $$$
  • Today's modern build tools rather than old technologies
  • Happy Customers

Limitations of Jamstack

  • Dynamic features are more difficult to accomplish for the developer and in some cases performance prohibitive
  • Dependent on 3rd party SaaS solutions could cause issues later if a service shuts down.
© Tony Alves