[D] Why XORM using instead of GORM [incubator-answer]

["surapuramakhil (via GitHub)" <gi...@apache.org>]

GitHub user surapuramakhil created a discussion: Why XORM using instead of GORM

Are there any specific reason why XORM https://xorm.io/ has been used for this project instead of GORM https://gorm.io/ ?

GORM has more wide community, more matured ORM compared to XORM.

An Example of more matured
- GORM support advanced scaling mechanism like sharing (for RDBMS) which XORM doesn't support as of today. 
- plugin extensibility support (above is provided as plugin)

And lot more



GitHub link: https://github.com/apache/incubator-answer/discussions/837

----
This is an automatically sent email for commits@answer.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@answer.apache.org

Re: [D] Why XORM using instead of GORM [incubator-answer]

["PaiHL (via GitHub)" <gi...@apache.org>]

GitHub user PaiHL added a comment to the discussion: Why XORM using instead of GORM

插一句，gorm 有及其复杂的 tag 规则以及莫名其妙的隐式规则。

GitHub link: https://github.com/apache/incubator-answer/discussions/837#discussioncomment-11661528

----
This is an automatically sent email for commits@answer.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@answer.apache.org

Re: [D] Why XORM using instead of GORM [incubator-answer]

["surapuramakhil (via GitHub)" <gi...@apache.org>]

GitHub user surapuramakhil added a comment to the discussion: Why XORM using instead of GORM

>  it is sufficient for our use

Problem is with max scale Apache answer can go. There is no extensibility for higher loads or scale.

Apache answer can go max data scale up to 3 to 5 TB (that where vertical scaling hits its threshold). In our previous discussion https://github.com/apache/incubator-answer/discussions/775, I was checking about MySQL NDB (network databases) unfortunately that isn't supported / not designed for that.

Now falling back on considering traditional RDBMS approach for horizontal scaling. Unfortunately, Even extensibility is not supported due to XORM.

 However, I have raised feature request at XORM https://gitea.com/xorm/xorm/issues/2427 hopefully they add features for horizontal scaling
 
 **Things to be praised:**
-  Based on articles / blogs written both evaluation, XORM beats GORM in performance (especially in read and update queries)

GitHub link: https://github.com/apache/incubator-answer/discussions/837#discussioncomment-8753864

----
This is an automatically sent email for commits@answer.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@answer.apache.org

Re: [D] Why XORM using instead of GORM [incubator-answer]

["LinkinStars (via GitHub)" <gi...@apache.org>]

GitHub user LinkinStars added a comment to the discussion: Why XORM using instead of GORM

There is no other reason, it's just that our team is more familiar with xorm and it is sufficient for our use. I am also a contributor to xorm.

GitHub link: https://github.com/apache/incubator-answer/discussions/837#discussioncomment-8753678

----
This is an automatically sent email for commits@answer.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@answer.apache.org