Finding the jelly in the jam stack
0 likes148 views
The document discusses the benefits and use cases of the Jamstack architecture presented by Tessa Mero at a Seattle Jamstack meetup. It highlights issues with traditional web applications, such as security and performance, and presents Jamstack as a solution that ensures speed, scalability, and simplicity. Several real-world use cases are examined, including examples from Freecodecamp, Sequoia, and Nike, showcasing various implementations of Jamstack and accompanying technologies.
Finding the jelly in the jam stack
- 1. Finding the Jelly in the JAMStack ...getting a taste of awesome use cases on JAMStack, by Tessa Mero May 8th, 2019 - Seattle JAM Stack Meetup The content of this presentation is proprietary information of Cloudinary. It is not intended to be distributed to any third party without the written consent of Cloudinary. © 2019 Cloudinary inc.
- 2. Oh hai ● Communities: Joomla, PHP, API, Vue.js ● Developer, Teacher, Advocate ● Gamer + Mom ● Korean Food Enthusiast ● Steak Hobbyist
- 3. Topics ● The JAMStack ecosystem ● The Problem & Fix ● Business Use Cases/Stories Ready for a scoop?
- 4. The Problem: web apps are getting messy ● Security ● Reliability ● Performance
- 5. JAMStack = Problem Fixed +
- 6. The JAMStack ecosystem Why should you use JAMStack on your next project?
- 8. Reasons for JAMStack ● Speed ● SEO ● Security ● Deployment & Workflow ● Community Image credit: builtvisible.com
- 10. Knowing Your Basic Account Identifiers and Navigating Your Account ● Cloud Name
- 11. 3 Reasons why JAMStack is being used 1. Speed - CDN Delivery! 2. Scaling - No DevOps! 3. Simplicity - No Database!
- 12. FreeCodeCamp’s Jelly ● Github + ● Gatsby + ● Netlify + ● mLab + ● Auth0 ● Node/Loopback +
- 14. System Architecture and Delivery Lifecycle ● Browser Browser - This is the first request, where a resource is requested by the user via their browser. Management Console Elastic Load Balancing: Console
- 15. Sequoia’s Jelly ● MiddleMan ● 2 APIs for Content and Jobs ● JSON
- 16. Use Case: JAMStack CMS
- 17. 3 CMS Types ● Coupled CMS ● Decoupled CMS ● Headless CMS <3 (winning)
- 18. Contentful’s Jelly ● Custom designed CDN ● JSON ● Images API ● RESTful API architecture
- 19. Use Case: Nike
- 20. Nike’s Jelly ● Cloudinary (Headless DAM) ● Frontend decoupled into a headless CMS ● GatsbyJS
- 21. << end ● Twitter: https://twitter.com/tessamero ● Email.: [email protected] THANK YOU!