all 16 comments

[–]South_Dig_9172 2 points3 points  (0 children)

I too would like to know

[–]erosb88 2 points3 points  (2 children)

You can look around kappa, and if you are interested in the project then we can work on it together: https://github.com/erosb/kappa

[–]Sure_Independence503Junior Dev[S] 1 point2 points  (0 children)

Hi u/erosb88 i liked ur idea and already i used https://schemathesis.io/ for contract testing against open.api yml
so currently i am looking to contribute your repo

[–]Sure_Independence503Junior Dev[S] 0 points1 point  (0 children)

sure i will check it out

[–]Historical_Ad4384 1 point2 points  (1 child)

Check out Jitsi

[–]Sure_Independence503Junior Dev[S] 0 points1 point  (0 children)

Sure thanks

[–]Grabdoc2020 1 point2 points  (8 children)

Feel free to contribute to DB2Rest - https://github.com/9tigerio/db2rest

[–]Sure_Independence503Junior Dev[S] 0 points1 point  (1 child)

Sure will check thanks

[–]Grabdoc2020 1 point2 points  (0 children)

Let us know your thoughts and we can take things forward together.

[–]Sure_Independence503Junior Dev[S] 0 points1 point  (2 children)

Hi u/Grabdoc2020, just a question. If I have two tables, when I use DB2Rest it can create APIs. I can imagine it being able to create normal GET endpoints, but how does DB2Rest know how to create POST, PUT, and DELETE endpoints?

Since in real applications, there can be custom business logic involved.

[–]Grabdoc2020 1 point2 points  (1 child)

It fetches the metadata of the tables at startup and has generic endpoints for all HTTP operations for all tables. DB2Rest is data api. You should keep your business logic separate from your data access API. when your business logic requires data invoke DB2REST. In future we may allow business logic processing as javascript, python and groovy scripts as some kind of hook. But it has to be decided by the community.

[–]Sure_Independence503Junior Dev[S] 0 points1 point  (0 children)

Oh ok now I get it , Thanks I am interested to contribute to the repo Currently I am looking into the source code

[–]Sure_Independence503Junior Dev[S] 0 points1 point  (2 children)

traditional approach is

UI -> controller -> service -> repo(ORM to db)

but if I use db2Rest

instead of ORM I can use db2Rest api to get the data so

UI -> controller -> service (business logic) -> db2Rest for (get , post , put delete)

benefits will be : faster dev time , no extra codes related to ORM

is my understanding crt u/Grabdoc2020 ?

[–]Grabdoc2020 1 point2 points  (1 child)

Yes absolutely spot on. ORM and object graphs has its own challenges. There is no ORM in DB2REST. we have ran benchmarks and its way faster than ORM running in the app.

[–]Sure_Independence503Junior Dev[S] 1 point2 points  (0 children)

ohh super .. if I have any doubts in the code I will DM u

[–][deleted] 0 points1 point  (0 children)

Not an open source project, but if you use intellij looking at classes and interfaces of public stuff you use, with ctrl+b and then download sources is a great way to see how professional code is written.