Need advice about which tool to choose?Ask the StackShare community!
Deis vs Hasura: What are the differences?
Introduction: Deis and Hasura are both platforms designed to help developers deploy and manage applications. However, they have key differences that set them apart in terms of functionality and use cases.
Architecture: Deis follows a container-driven workflow that allows developers to build, deploy, and scale applications using Docker containers. On the other hand, Hasura is built on top of Kubernetes and abstracts away the complexities of managing Kubernetes clusters, providing a simpler way to deploy and manage applications.
Data Management: Deis focuses on container orchestration and application management, providing tools for developers to scale and monitor their applications. In contrast, Hasura specializes in data access and API management, offering powerful features for creating and managing APIs over databases.
Scalability: Deis is more geared towards providing scalability for applications by easily scaling containers and managing resources efficiently. Hasura, while also supporting scalability through Kubernetes underlying infrastructure, places more emphasis on data scaling and access control for APIs.
Deployment Workflow: Deis provides a comprehensive workflow for developers to build, deploy, and manage applications through a series of commands and configurations. Hasura simplifies the deployment process by automating many tasks and providing a user-friendly interface for developers to manage their applications.
In Summary, Deis and Hasura differ in their architecture, data management focus, scalability features, and deployment workflows, catering to different needs and preferences of developers in managing and deploying applications.
We wanted to save as much time as possible when writing our back-end, therefore Apollo was out of the question, we went for an auto-generated API instead. Hasura looked good in the beginning, but we wanted to retain the ability to add a few manual resolvers and modifications to auto-generated ones, which ruled out Hasura. Postgraphile with its Plug-In architecture was the right choice for us, we never regretted it!
Pros of Deis
- 12-factor methodology16
- Open source10
- Built on coreos8
- Built on Docker7
- Awesome team of people5
- Free4
- Backed by Docker2
- Apache 2.0 license1
Pros of Hasura
- Fast23
- Easy GraphQL subscriptions18
- Easy setup of relationships and permissions16
- Automatically generates your GraphQL schema15
- Minimal learning curve15
- No back-end code required13
- Works with new and existing databases13
- Instant production ready GraphQL12
- Great UX11
- Low usage of resources4
- Simple4
Sign up to add or upvote prosMake informed product decisions
Cons of Deis
- No longer maintained1
Cons of Hasura
- Cumbersome validations3