text: If you're new to serverless development, you might be more familiar with traditional frameworks. 
  
  Let us look at the steps in a traditional request/response cycle for comparison: 
  
  1. Accept an inbound network request and create local data objects. 
  
  2. Map the URL, often called a route, with conﬁguration or annotations to an action. 
  
  3. Create global data and utility services, such as a database connection pool and an object 
  
  relational mapper. 
  
  4. Implement web hooks for logging, observability, and health monitoring components. 
  
  5. Process the request: query a database, store or retrieve data, call external systems. 
  
  6. Convert outbound data into a suitable response or error and serialize the data into JSON. 
  
  7. Add metadata, such as headers, cookies, tokens to the response object. 
  
  8. Send the response back to the client. 