Custom software
GraphQL in SIDECUBE digital projects
GraphQL makes sense when the app has multiple roles and interfaces that take data from the same backend in different ways.
Match
When we use GraphQL
The technology is chosen after we understand the objective, the rhythm of the team, the level of administration and how much the project needs to increase.
- Complex dashboardsWe organise indicators, filters and multiple actions without losing the hierarchy of important information.
- Role applicationsWe assign available operations and information according to the tasks of each user type.
- Multiple frontendsWe define common contracts for interfaces that use the same data and business rules.
- SaaS ProductsWe plan the customer's experience and the management of the product from activating the account to recurring use.
Uses
What can we build with GraphQL
We only use technology where it helps the project to be faster, easier to manage or safer to expand.
Deliverables
What goes into implementation
Accurate delivery depends on the project, but we keep every documented, tested and prepared implementation for maintenance.
- GraphQL schema markup
- Resolvers
- Authorisation
- Front integration
- Documentation querys
Connected services
GraphQL usually occurs in these projects
Choose the service that best describes your need, then determine if this technology is the right choice.
Custom softwareSee serviceWeb, mobile and SaaS applicationsSee service
Software solutions
Applications, dashboards and integrations that gather important processes into a more manageable system.
Applications
Web and mobile applications, SaaS platforms and portals connected to company data and processes.
Recommended pages
Services, technologies and guides related to this technology and its use in projects.
Specialised services
Close technologies
Industries
Guides
Frequently Asked Questions
Before you choose technology
Uses, integration and costs for GraphQL.
01 / Match
When that choice makes sense
What projects do you consider GraphQL?
Suitable situations: Complex Dashboards; Role Applications; Multiple Frontens; SaaS Products. The choice shall be confirmed after analysis of existing requirements, team and solutions.
What are you proposing for GraphQL?
Relevant examples are: Flexible API; Data aggregation; Complex Frontend; Controlled Data Scheme. We determine what serves your objective and what would add complexity without a clear benefit.
02 / Implementation
Integration and deliverables
Can the solution be integrated into an existing project?
We inventory available applications, data and interfaces. We check compatibility, permissions and consequences for existing processes before changing an operational flow.
What could include implementation?
For GraphQL, we can define in the offer: GraphQL schema markup; Resolvers; Authorization; Integration frontend; Documentation querys. We confirm the deliverables after verification of compatibility and available access.
03 / Operation
Verification and costs
How do you check that implementation works?
We use scenarios with representative data to check the rules, data integrity and errors. To connect systems we also check access, synchronisation and possibility of recovery.
What costs should be foreseen in the long term?
We separate the analysis and development of infrastructure, licenses and use. Data volume, number of users and availability requirements influence the long-term cost.