Home → Documentation → Getting Started → FAQ
No. Phase 1 uses EF Core mapping classes as the metadata source — see First Service → Write a mapping class. Coffee Beanery reads that mapping at compile time; it doesn’t ask you to learn a parallel schema language.
No — it deliberately doesn’t. Hot Chocolate remains the GraphQL framework, Dapper remains the SQL executor. Foundgine sits between your domain model and those tools, generating the execution plan that connects them. See Architecture → Vision for the full positioning.
Treat it as early-stage. The mapping source generator is explicitly marked “not yet build-verified” against arbitrary mapping shapes beyond the sample — see Source Generators → Diagnostics. Review the Roadmap and ADRs before depending on it for anything load-bearing.
The extended architecture FAQ — covering source generators vs. reflection, transport and provider independence, and Native AOT — lives in Reference → FAQ.
| ← Previous: Configuration | Next: Architecture → |