kidustiliksew
Reputation: 463
What is wrong with using the low level Datastore APIs
Several sources recommend that I use standard interfaces such as JDO, JPO, and Objectify with the Datastore instead of the low-level APIs for "simplicity" reasons. Many code samples i've seen use these interfaces. But I don't find the low-level APIs all that complicated. Is there a better reason why I shouldn't use the low-level APIs besides simplicity?
Upvotes: 0
Views: 101
Answers (1)
Andrei Volgin
Reputation: 41089
Reasons to use low-level API: (1) better performance, (2) fast instance start-up time, (3) precise control over your code, (4) fewer dependencies.
Reasons to use Objectify: (1) less boilerplate code, (2) more familiar approach for experienced Java developers.
Reasons to use JDO/JPA: compatibility with legacy code/software.
Upvotes: 2
Related Questions
- How can I create an executable/runnable JAR with dependencies using Maven?
- What are the differences between a HashMap and a Hashtable in Java?
- What are the -Xms and -Xmx parameters when starting JVM?
- What is the difference between public, protected, package-private and private in Java?
- What is the equivalent of Java static methods in Kotlin?
- What is the difference between canonical name, simple name and class name in Java Class?
- What are the possible values of the Hibernate hbm2ddl.auto configuration and what do they do
- What is the difference between JDK and JRE?
- Dealing with "Xerces hell" in Java/Maven?
- Using low level api for datastore in google app engine ? is it bad?