Appfuel Developer Handbook

Appfuel exists for the sole purpose of isolating your business logic into its own gem and exposing a set of interfaces to interact with that logic. Your ruby app (web, console, daemon) would represent its own boundary that simply interacted with your business gem. It would do this by declaring the business gem as dependency it needs to use and treating it like any other gem. In this book we are going to cover Appfuel's architecture as well as its usage.

The handbook is divided into the following parts:

• Architectural Overview
• Application bootstrapping & The app container (IoC)
• The request lifecycle & application boundaries
• Validation
• Domain Entities, Collections & Value Objects
• Repositories & presistence
• Interactor's & Commands
• Presentation of results
• Examples & Patterns