Using a Headless and API-First approach comes with a problem. With only an API (or multiple) to start with, how do you know you are building your project codebase ("head") to account for best practices such as caching, security, and best performance. How do you know what path offers to allow for the most flexibility with the least amount of headaches? It isn't the same as just having a database and template engine on the backend.

SaaS based Headless solutions are a powerful way to build modern enterprise class websites. They are also becoming more popular by the day.

Luckily, multiple solutions have now been built around these "API first" platforms. Some best practice architecture patterns have emerged as a result, and this session aims to share them. Attendees will see and learn these patterns for designing, building, and deploying Headless based solutions.

Leave the session with proven architecture patterns and how to apply them when working with a Headless CMS and API first stack.