《Modern Web Development on the JAMstack》简介：

Really pause and think about how much time and effort web teams around the world have spent building and managing infrastructure. For many years, launching a site or web application has been as much about deploying complex server environments as it’s been about building actual application code. e cloud made provisioning all these resources faster but no less complicated.

The JAMstack was born of the stubborn conviction that there was a better way to build for the web. Around 2014, developers started to envision a new architecture that could make web apps look a lot more like mobile apps: built in advance, distributed, and connected directly to powerful APIs and microservices. It would take full advantage of modern build tools, Git workflows, new frontend frameworks, and the shi from monolithic apps towards decoupled frontends and backends.

At Netlify, we’ve watched enthusiasm for the JAMstack grow well beyond our wildest expectations. It now powers every site we deploy for over 500,000 developers and companies. We’ve seen firsthand how the JAMstack improves the experience for both users and developers. Most importantly, we’ve seen how increases in site speed, site reliability, and developer productivity can contribute to the continued health and viability of the open web.

We’re thrilled that you, too, want to explore the JAMstack and hope this book serves as a useful guide. Welcome to the community. Welcome to a new way to develop, deploy, and power web content and applications. Welcome to the JAMstack.

Sincerely,

Matt Biilmann

CEO, Netlify

《Modern Web Development on the JAMstack》目录：

Table of Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
1. The Challenges of Modern Web Development. . . . . . . . . . . . . . . . . . . . 1
The Drawbacks of Monolithic Architectures
The Risk of Staying the Same
2. Introducing the JAMstack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
What’s in a Name?
JavaScript
APIs
Markup
Types of JAMstack Projects
Summary
3. Advantages of the JAMstack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Simplifying Systems and Simplifying Thinking
Costs
Scale
Performance
Security
For the Developer; For the Project; For the Win
4. Planning for the JAMstack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Setting Up the Project
Strategies for Managing Content
Choosing a Site Generator
Adding Automation
Selecting a CDN
Providing Functionality: APIs
5. Shifting the Mental Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
A Mindset and an Approach
One: Get to the CDN
Two: Design for Immutability and Atomic Deployments
Three: Employ End-to-End Version Control
Four: Automation and Tooling
Five: Embrace the Ecosystem
Six: Bridging the Last Gaps with Functions as a Service
Being Comfortable with Breaking the Monolith
6. Applying the JAMstack at Scale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A Case Study: Smashing Magazine
The Challenge
Key Considerations
Picking the Right Tools
Content Migration
Utilizing Structured Content
Working with Large Sites
Building Out the Core
Search
Content Management
Integrating Netlify CMS
Listings, Search, and Assets: Customizing the CMS for Large Projects
Identity, Users, and Roles
Ecommerce
Membership and Subscriptions
Tying It Together: Member Discounts in GoCommerce
Job Board and Event Tickets: AWS Lambda and Event-Based Webhooks
Workflows and API Gateways
Deploying and Managing Microservices
Summary
7. Conclusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
And One More Thing...
· · · · · ·