Re:The Unofficial Guide to Migrating Off of Google App Engine
by mhusby on Saturday February 26, 2011 @11:32AM
(#2265859)
I guess I can see that argument, but at the same time its so easy to add memcache that it really seems silly not to add memcache for you models at are accessed a lot. Here is a simple user model, adding memcahce is a total of 7 lines. I just cant see the case where you wouldn't add this to start with:
[ Parent
| on HN ]
Re:The Unofficial Guide to Migrating Off of Google App Engine
by jasonkester on Saturday February 26, 2011 @01:16PM
(#2266092)
Easy is good. It's a similar level of effort in most frameworks, which is handy.
The thing is, if you turn it on right away you never get a chance to see and fix a bunch of low hanging fruit optimizations that can really help you out. You don't know about them until you start to run up against scaling issues despite all your caching. Once you're there, it's not any fun to try to go back, find and fix those original bottlenecks, so you don't have much option but to start throwing hardware at it.
If, on the other hand you hold off and handle your first few scaling episodes by making your queries and code faster, only adding caching after you're not seeing returns from that other stuff anymore, you'll be able to go a lot farther before you have to start adding hardware.
Re:The Unofficial Guide to Migrating Off of Google App Engine
by fletchowns on Saturday February 26, 2011 @03:09PM
(#2266385)
Or if you are using Objectify:
@Cached
public class MyEntity {
@Id Long id;
...
}
:)