A thought about api design

Question

A thought about api design

btiernay opened this issue 11 years ago · comments

I'm not sure if you are familiar with Jongo, which makes working with MongoDB in Java more like working in the mongo shell, but you should take a look if not:

http://jongo.org/

What I like about it is that it doesn't try to hide the native look and feel of the query language and is very easy to work with. Also, it has great support for Jackson which is key in Java when working with JSON.

Anyways, you may be able to grok a few ideas from their design.

Cheers

Alex Popescu · Answer 1 · Sat May 25 2013 01:21:45 GMT+0800 (China Standard Time)

Thanks @btiernay. I need to look into it, but at the first glance there seem to be quite a bit of string parsing/interpolation being used in jongo.

Bobby Tiernay · Answer 2 · Sat May 25 2013 05:37:01 GMT+0800 (China Standard Time)

Depending on your perspective that may be a good or a bad thing. Sql is the same way and there is something to be said for not abstracting it too much (eg Hibernate criteria api). I thinm Jongo has done a good job at balancing typesafety with expressiveness and ease of use. Just my 2c.

Cheers

Bobby Tiernay · Answer 3 · Sat May 25 2013 05:40:20 GMT+0800 (China Standard Time)

Btw, why aren't YOU using testng in your code? :)

Alex Popescu · Answer 4 · Sat May 25 2013 06:16:33 GMT+0800 (China Standard Time)

My thoughts right now is that the first version should be API-centric. Adding a porcelain API on top of that would be easier.
I wanted to see how far can I get with JUnit. Parameterizing tests is still weak, so I'll probably go back to TestNG ;-)

Bobby Tiernay · Answer 5 · Sat May 25 2013 06:23:56 GMT+0800 (China Standard Time)

Fair point
No excuse ;)