An ORM is not necessary with HarperDB, as the primary method of interaction is through the API. This does not add any overhead to the application, in fact, it removes a layer from your application stack because HarperDB natively returns JSON objects.
Additionally, HarperDB can be installed wherever you'd like. We offer a DBaaS product, HarperDB Cloud, but you can also find HarperDB on npm.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
I think you've not internalized what an ORM is but anyway I'll take a look for another stuff i've in mind it can work well with some controller or gateway or without that depending on the possibilities of Harper :D
An ORM is not necessary with HarperDB, as the primary method of interaction is through the API. This does not add any overhead to the application, in fact, it removes a layer from your application stack because HarperDB natively returns JSON objects.
Additionally, HarperDB can be installed wherever you'd like. We offer a DBaaS product, HarperDB Cloud, but you can also find HarperDB on npm.
I think you've not internalized what an ORM is but anyway I'll take a look for another stuff i've in mind it can work well with some controller or gateway or without that depending on the possibilities of Harper :D
Thanks for answering
Sounds good Joel, please let me know if any additional questions come up or you can always connect with our team on the Community Slack! :)