Hybrid deployment places each operation at the edge or origin according to its data dependencies. Edge infrastructure handles lightweight, latency-sensitive work; origin infrastructure handles centralized database access and complex computation. section 5.3.2
Apply the pattern by separating operations before choosing infrastructure:
- Keep operations that need only local inputs, such as token handling and signing, at the edge. section 5.3.2
- Forward database-dependent operations, such as profile updates, to infrastructure near the origin database. section 5.3.2
- Assemble cached product data, personalized recommendations, and user-specific pricing before returning one response. section 5.3.2
- Check database round trips rather than assuming edge execution is faster; distant queries can add more than a second of latency. section 5.3.2
Netflix Open Connect
Netflix keeps authentication, recommendations, and playback decisions in AWS while serving video bytes from Open Connect Appliances inside ISP networks. Application logic and content delivery therefore use different infrastructures. section 5.3.2
Figure 5.7 CDN latency advantage
Use the latency diagram to compare centralized delivery with content served from nearby edge infrastructure. section 5.3.2








