Apache Thrift VS EdgeDB

• Cross-Language Support
  Apache Thrift supports numerous programming languages including Java, Python, C++, Ruby, and more, enabling seamless communication between services written in different languages.
• Efficient Serialization
  Thrift offers efficient binary serialization which helps in reducing the payload size and improves the communication speed between services.
• Service Definition Flexibility
  Thrift provides a robust interface definition language (IDL) for defining and generating code for services with strict type checking, fostering strong contract interfaces.
• Scalability
  Due to its lightweight and efficient serialization mechanisms, Apache Thrift can handle a large number of simultaneous client connections, making it suitable for scalable distributed systems.
• Versioning Support
  Thrift supports service versioning which helps in evolving APIs without disrupting existing services or clients.

Possible disadvantages

• Steep Learning Curve
  For new users, especially those not familiar with RPC frameworks, learning and understanding Thrift’s IDL and operations can be complex and time-consuming.
• Documentation and Community Support
  Compared to some alternative technologies, Apache Thrift's documentation and community support can be less robust, which might pose challenges in troubleshooting or seeking guidance.
• Lack of Advanced Features
  Thrift does not support some advanced features like streaming or multiplexing out of the box, which could limit its use in complex systems requiring these functionalities.
• Infrastructure Overhead
  Integrating Thrift into an existing system might introduce infrastructure overhead both in initial setup and ongoing maintenance, especially when dealing with multiple languages.
• Protocol Limitations
  While Thrift is highly efficient, its protocol limitations might require additional workarounds for certain data structures or transport mechanisms, complicating development.

• Graph-Relational Model
  EdgeDB combines the features of relational and graph databases, allowing for complex queries and relationships while maintaining data integrity typical in relational databases.
• Advanced Query Language (EdgeQL)
  EdgeQL offers a more intuitive and expressive query syntax compared to traditional SQL, facilitating easier and more efficient data retrieval.
• Schema Evolution
  EdgeDB provides robust tools for schema migrations and versioning, making it easier to evolve the database schema without downtime or data loss.
• Type Safety
  With its strong typing system, EdgeDB reduces runtime errors by ensuring data type consistency across the database operations.
• Integrated Indexing and Constraints
  EdgeDB supports advanced indexing and constraints, improving query performance and maintaining data integrity natively.

Possible disadvantages

• Relative Newness
  Being relatively new in the market, EdgeDB might lack extensive community support and third-party integrations compared to more established databases.
• Learning Curve
  Technicians accustomed to traditional SQL or other database paradigms might face a learning curve when adapting to EdgeDB's unique features and query language.
• Limited Ecosystem
  EdgeDB's ecosystem, including tooling, documentation, and community resources, is less mature compared to other well-established database systems.
• Potential for Rapid Changes
  As a developing technology, EdgeDB may undergo rapid changes and updates, which may lead to instability or additional maintenance overhead.
• Hosting and Compatibility Concerns
  Deploying EdgeDB might have specific hosting requirements, and compatibility with existing infrastructure could be a concern for some users.

No analysis of EdgeDB yet.

Apache Thrift

Checking out EdgeDB - The Developer Database (Better than Prisma ORM?!)

More videos

• Show HN: TypeSchema – A JSON specification to describe data models

  I once read a paper about Apache/Meta Thrift [1,2]. It allows you to define data types/interfaces in a definition file and generate code for many programming languages. It was specifically designed for RPCs and microservices. [1]:... - Source: Hacker News / almost 2 years ago

• Delving Deeper: Enriching Microservices with Golang with CloudWeGo

  While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / over 2 years ago

• Reddit System Design/Architecture

  Services in general communicate via Thrift (and in some cases HTTP). Source: over 3 years ago

View more

• Beyond SQL: A relational database for modern applications

  A new DB, with a new query language that's like "SQL done right"? This immediately reminded me of EdgeDB: https://edgedb.com/ Is there anyone here who knows enough about these two products to do a compare/contrast? - Source: Hacker News / about 3 years ago

• Beyond SQL: A relational database for modern applications

  See also https://edgedb.com/ which is another relational database without sql. - Source: Hacker News / about 3 years ago

• DuckDB 0.8.0

  >relational no-sql Do you mean something like edgeDB?[0] Or do you mean some non-declarative language completely? I don't see the latter making much sense. The issue with SQL for me is the "natural language" which quickly loses all... - Source: Hacker News / over 3 years ago

View more