mHSEQ VS PostGraphQL

• Integration
  mHSEQ allows for seamless integration with existing safety and quality management systems, enhancing efficiency and consistency across processes.
• User-Friendliness
  The application is designed with a user-friendly interface, making it accessible for users of varying technical backgrounds.
• Real-Time Data
  mHSEQ offers real-time data collection and reporting, enabling timely decision-making and response to safety and quality issues.
• Customization
  The platform can be customized to suit specific organizational needs, allowing for tailored safety and quality management solutions.
• Mobile Accessibility
  Users can access the system via mobile devices, increasing accessibility and flexibility for field operations.

Possible disadvantages

• Cost
  The service might be costly for small organizations with limited budgets, potentially limiting access for some users.
• Technical Support
  There may be limited technical support available, which can pose challenges for users needing assistance.
• Learning Curve
  New users might experience a learning curve when initially adopting the system, requiring training and adjustment time.
• Compatibility
  There could be compatibility issues with certain legacy systems, requiring additional resources to integrate smoothly.
• Internet Dependency
  mHSEQ relies on internet connectivity, which can be a limitation in remote areas with poor or no internet access.

• Automatic Schema Generation
  PostGraphQL automatically generates a GraphQL schema based on the structure and relationships within your PostgreSQL database, reducing the need for manual schema definition and maintenance.
• Efficiency
  By leveraging PostgreSQL functions, PostGraphQL can efficiently execute complex queries directly within the database, leading to potentially faster query performance.
• Consistent API
  The tool ensures a consistent and predictable API is generated from the database schema, which can simplify client-side development and integration.
• Support for PostgreSQL Features
  PostGraphQL takes advantage of PostgreSQL's advanced features such as triggers, views, and stored procedures, allowing for rich and powerful API capabilities.

Possible disadvantages

• Complexity with Custom Logic
  Implementing custom business logic can become complex, as it often requires embedding logic within the database using SQL or PL/pgSQL, which may not be as straightforward as writing it in a standalone application server.
• Overhead for Simple Applications
  For simple applications with limited database interactions, PostGraphQL might introduce unnecessary complexity and overhead compared to using a traditional REST API or a simpler GraphQL server.
• Learning Curve
  Developers unfamiliar with PostgreSQL might face a learning curve in leveraging the full capabilities of PostGraphQL, particularly if they're not accustomed to database-centric application design.
• Tight Coupling with Database
  PostGraphQL closely ties the API design to the database schema, which may reduce flexibility in cases where the API design needs to evolve independently of the database structure.

Tracking mHSEQ since Mar 2021.

• Best Orm that uses Graphql and Postgres

  If you point is to abstract all the CRUD/GraphQL application, Go isn’t needed. You can go with PostgREST or Postgraphile. Source: almost 4 years ago

• Ask HN: Locally generate GraphQL schema and resolvers from DB

  What do you mean locally? Hasura is OSS, and you can run it locally (you have autogenerated SQL statements) Here you can just use Nhost and its CLI; Alternatives are https://github.com/graphile/postgraphile or dgraph as you mentioned.... - Source: Hacker News / almost 4 years ago

• Supabase (YC S20) raises $80M Series B

  I've personally found Postgraphile to be fantastic. Nicer to use than Hasura and fully OSS: https://github.com/graphile/postgraphile/. - Source: Hacker News / over 4 years ago

View more