Hi Phil,
Coming from Java world, I'm very much spoiled with frameworks. When I first
created an app for GAE, I used Spring. But due to unacceptable start-up
time, I ditched it and just use Servlet+JSP.
I miss a lot of convenience (esp. Spring Security), but luckily GAE
provides other goodies,
I doubt that Google will commit to any official statement. So here's my 2
cents, from a low-usage, rather complex B2B application. "Frameworks are
okay, to a certain degree, but be prepared to rework if you're successful"
We're using one heavy framework (Apache Wicket) and plenty of the regul
I have been struggling with the same issue of whether GAE is suitable for
business apps or not (by business apps, I am thinking of order
processing, credit processing system, shipping systems, billing, etc.
eCommerce, etc.). For the past 10 years I have built web-based SaaS
applications and t
Thomas,
How do you access the datastore?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsub
That's an interesting comment. I had the impression that with Java you
would have only a small surface that's actually exposed to App Engine
and porting would be very, very simple (with the occasional required
profiling because it is a very distributed system). With Python, it's
very hard to avoid
On Mon, Jul 23, 2012 at 10:32 AM, Per wrote:
>
> I doubt that Google will commit to any official statement. So here's my 2
> cents, from a low-usage, rather complex B2B application. "Frameworks are
> okay, to a certain degree, but be prepared to rework if you're successful"
While I certainly woul
Hi Brandon,
I use both Objectify and low-level access. Objectify for most "fixed-field"
entities, and low-level for small entities (for session, as i override
GAE's Java session) and entities where it can have 30+ fields but only 5+
filled in average (but need to store them in 1 entity since pe
Look likes there's a niche for a new framework.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/9RiGLtk17W4J.
To post to this group, send email to
Jeff... regarding your Objectify optimisations... I'd be interested in details
if you have any to hand please :-)
I've personally made the introspection stage lazy load (moving it to trigger
inside the getMetadata methods)... it's probably limited in scope to my
specific needs (I'm not using an
What I've taken away from these long threads is that:
1. GAE is already faster than other AWS and others when it spins up new
instances
2. GAE's job is harder when there's a lot of initialization to do and lots
of jars to scan. Precompilation helps but not enough for large apps
3. the scheduler d
10 matches
Mail list logo
