A GraphQL Star Wars example implementation using GraphQL for .NET, ASP.NET Core, and Entity Framework Core.
StarWars is a GraphQL example project built with .NET technologies that implements a complete Star Wars universe API. It demonstrates how to create a GraphQL server using GraphQL for .NET, ASP.NET Core, and Entity Framework Core with proper architecture patterns and testing strategies. The project solves the problem of finding a comprehensive, production-quality reference implementation for GraphQL in the .NET ecosystem.
.NET developers learning GraphQL implementation, teams adopting GraphQL with ASP.NET Core who need architectural guidance, and educators looking for a complete example with testing and CI/CD integration.
Developers choose this project because it provides a fully-featured, well-architected reference implementation that goes beyond basic tutorials, covering testing, logging, dependency injection, and continuous integration while implementing the official GraphQL Star Wars example specification.
GraphQL 'Star Wars' example using GraphQL for .NET, ASP.NET Core, Entity Framework Core
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements a full Star Wars database with characters, planets, and episodes, as detailed in the README's advanced section, providing a real-world GraphQL schema reference.
Follows Domain-Driven Design and multi-layer architecture (API, Core, Data) with dependency injection, ensuring clean separation of concerns and testability.
Includes unit tests, integration tests, and code coverage reporting using tools like xUnit and OpenCover, demonstrated in the README's testing sections.
Configured with VSTS/CI pipeline for automated builds and testing, as shown in the Continuous Integration section, promoting DevOps practices.
The roadmap indicates key GraphQL features like mutations are not implemented, limiting its usefulness for full CRUD operations in production scenarios.
Requires additional tooling like NPM and webpack for GraphiQL integration, which adds complexity for .NET developers unfamiliar with JavaScript ecosystems.
Relies on VSTS (now Azure DevOps) for continuous integration, which may not align with teams using other CI/CD platforms like GitHub Actions or Jenkins.