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
well the purpose of keeping it as thread is to answer possible questions others could have too.
I mean that If I set up an API let's say using PHP + MySQL I can use Laravel and benefit from the ORM plus isolating on that instance the microservice/service related code and DB.
I can set it up on an Amazon EC2 which will be cheaper than relegating the DB stuff to harperDB, isn't it?
Also the ORMs usually don't work through REST calls but connecting itself into a DB instance.
I'm trying to balance costs of development with costs of architecture comparing that to what it could be using it. Also I'm trying to understand what can HarperDB offers me that I can't get with Google Cloud Platform or Amazon Web Services "as is" or at low cost (few hours of a programmer)
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
well the purpose of keeping it as thread is to answer possible questions others could have too.
I mean that If I set up an API let's say using PHP + MySQL I can use Laravel and benefit from the ORM plus isolating on that instance the microservice/service related code and DB.
I can set it up on an Amazon EC2 which will be cheaper than relegating the DB stuff to harperDB, isn't it?
Also the ORMs usually don't work through REST calls but connecting itself into a DB instance.
I'm trying to balance costs of development with costs of architecture comparing that to what it could be using it. Also I'm trying to understand what can HarperDB offers me that I can't get with Google Cloud Platform or Amazon Web Services "as is" or at low cost (few hours of a programmer)
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! :)