Fragments or no fragments? GAE / JAVA / JDO

I am currently porting some work from Mysql to Google App Engine / Java I am using JDO and the required low-level Java API

I read the optimization guide for slice counters: http://code.google.com/appengine/articles/sharding_counters.html

I'm still building the foundation of my application I know that premature optimization is the root of all evil; But this is clearly documented to avoid contention So it's hard for me to decide whether I should prefer a certain way

So should I default to the sharding counter (and other write objects that may have a higher frequency), or should I move forward without sharding and implement it as needed?

Solution

The significant meaning of "precocious" here is "before the appropriate time" Design to avoid limitations. It is too early to understand these limitations well

Break your counter

The content of this article comes from the network collection of netizens. It is used as a learning reference. The copyright belongs to the original author.
THE END
分享
二维码
< <上一篇
下一篇>>