Hi De Witte,
That would happen if you are successful. Imagine building a complex app
using app engine.
It's pretty difficult to stay away from modules.
For example:
imagine a social network scenario, where you have long running tasks
competing with frontend requests.
then put britney spears
sorry, my last phrase was confusing, I meant: That would happen if you are
successful building a complex architecture using app engine
On Fri, Feb 28, 2014 at 1:00 AM, Rafael mufumb...@gmail.com wrote:
Hi De Witte,
That would happen if you are successful. Imagine building a complex app
This is pretty much our experience of modules too - especially the
maven integration feels half-baked. But we have a couple batch
operations that run at midnight that require extra memory, and it
sucks to have to pay for that all day.
I think I've been one of the loudest people complaining about
Hi Jeff,
I would describe mine as success too.
Although, the only point of using appengine was the ease of development and
that it would scale as we grew.
1) Ease of development is out of question with a big code base.
2) scale comes at the highest cost.
Thanks
Rafa
On Feb 28, 2014 2:23 AM,
We don't use modules, why should you? Do you have a requirement which
cannot be done without them?
Op donderdag 27 februari 2014 02:58:56 UTC+1 schreef Rafael Sanches:
De Witte,
Do you have a multi module project?
How do you handle that without module? The eclipse plugin doesn't work
How long is the warmup time of your app?
Can you show the configuration file of your app? (appengine-web.xml)
On Friday, February 28, 2014 1:02:28 AM UTC+8, de Witte wrote:
We don't use modules, why should you? Do you have a requirement which
cannot be done without them?
Op donderdag 27
We have been working with Java and GAE for several years now and so far no
problems.
AngularJs + ExtJS 4.0 is a good combo for the front end. Although I prefer
GWT.
Spring+Maven is a headache even without GAE. We have been avoiding it and
doing fine.
Op maandag 24 februari 2014
De Witte,
Do you have a multi module project?
How do you handle that without module? The eclipse plugin doesn't work with
that setup.
thanks
rafa
On Wed, Feb 26, 2014 at 3:45 PM, de Witte wd.dewi...@gmail.com wrote:
We have been working with Java and GAE for several years now and so far no
De Witte,
Do you have a multi module project?
How do you handle that without module? The eclipse plugin doesn't work with
that setup.
thanks
rafa
On Wed, Feb 26, 2014 at 3:45 PM, de Witte wd.dewi...@gmail.com wrote:
We have been working with Java and GAE for several years now and so far no
On Sunday, February 23, 2014 1:47:28 PM UTC+8, Rafael Sanches wrote:
Can you try and let us all know? it may be the solution you're looking
for.
The Google App Engine module for Play has not been updated for 2 years! :(
For another one, Objectify ,
Not being updated doesn't mean it doesn't work properly.
GAE + java is definitely frustrating, but some of your statements are a bit
too broad ;)
On Sun, Feb 23, 2014 at 12:44 AM, Tapir tapir@gmail.com wrote:
On Sunday, February 23, 2014 1:47:28 PM UTC+8, Rafael Sanches wrote:
Can you
Emanuele, I'm not going to disagree with your points, I think there is
validity to what you say. I would like to make a counter-point though.
I think that there are many standard 'good software engineering practices',
which are only good in a historical and pragmatic sense. What i mean is
that
Can you try and let us all know? it may be the solution you're looking for.
On Thu, Feb 20, 2014 at 8:29 PM, Tapir tapir@gmail.com wrote:
On Friday, February 21, 2014 5:39:17 AM UTC+8, Rafael Sanches wrote:
Have you tried playframework? They have optimizations to make your life
easier
Have you tried playframework? They have optimizations to make your life
easier when developing.
My life is living hell right now when developing with maven and appengine.
The play framework solves that by running their own thing.
Read more: http://www.playframework.com/documentation/1.0/gae
On Friday, February 21, 2014 5:39:17 AM UTC+8, Rafael Sanches wrote:
Have you tried playframework? They have optimizations to make your life
easier when developing.
My life is living hell right now when developing with maven and appengine.
The play framework solves that by running their
On Tuesday, February 18, 2014 6:43:56 PM UTC+8, Tapir wrote:
On Tuesday, February 18, 2014 4:56:51 PM UTC+8, Rafael Sanches wrote:
very interesting...
can you tell me how you did that? in a maven build or only via eclipse?
neither, I did it manually.
ok, the new test result:
1. if
Great stuff
hope you don't move to Go too soon!
On Thursday, 20 February 2014 03:52:33 UTC+13, Tapir wrote:
On Tuesday, February 18, 2014 6:43:56 PM UTC+8, Tapir wrote:
On Tuesday, February 18, 2014 4:56:51 PM UTC+8, Rafael Sanches wrote:
very interesting...
can you tell me how you
On Thursday, February 20, 2014 6:26:52 AM UTC+8, Emanuele Ziglioli wrote:
Great stuff
hope you don't move to Go too soon!
Why?
It is a way of no ways.
On Thursday, 20 February 2014 03:52:33 UTC+13, Tapir wrote:
On Tuesday, February 18, 2014 6:43:56 PM UTC+8, Tapir wrote:
On
Ok, I removed all core GAE jar files under SDK/lib/user
Now the warmup time dropped from 5-7 seconds to 3-4 seconds.
What is appengine-api-labs-1.x.x.jar? is it essential?
And must the appengine-api-1.0-sdk-1.x.x.jar be included in the project war
directory?
On Tuesday, February 18, 2014
very interesting...
can you tell me how you did that? in a maven build or only via eclipse?
On Tue, Feb 18, 2014 at 12:44 AM, Tapir tapir@gmail.com wrote:
Ok, I removed all core GAE jar files under SDK/lib/user
Now the warmup time dropped from 5-7 seconds to 3-4 seconds.
What is
On Tuesday, February 18, 2014 4:56:51 PM UTC+8, Rafael Sanches wrote:
very interesting...
can you tell me how you did that? in a maven build or only via eclipse?
neither, I did it manually.
ok, the new test result:
1. if I remove all jar files from the war/WEB-INF/lib, the warmup time is
On Tuesday, February 18, 2014 6:43:56 PM UTC+8, Tapir wrote:
On Tuesday, February 18, 2014 4:56:51 PM UTC+8, Rafael Sanches wrote:
very interesting...
can you tell me how you did that? in a maven build or only via eclipse?
neither, I did it manually.
ok, the new test result:
1. if
On Tuesday, February 18, 2014 6:43:56 PM UTC+8, Tapir wrote:
On Tuesday, February 18, 2014 4:56:51 PM UTC+8, Rafael Sanches wrote:
very interesting...
can you tell me how you did that? in a maven build or only via eclipse?
neither, I did it manually.
ok, the new test result:
1. if
On Tuesday, February 18, 2014 6:43:56 PM UTC+8, Tapir wrote:
On Tuesday, February 18, 2014 4:56:51 PM UTC+8, Rafael Sanches wrote:
very interesting...
can you tell me how you did that? in a maven build or only via eclipse?
neither, I did it manually.
ok, the new test result:
1. if
On Tuesday, February 18, 2014 6:43:56 PM UTC+8, Tapir wrote:
On Tuesday, February 18, 2014 4:56:51 PM UTC+8, Rafael Sanches wrote:
very interesting...
can you tell me how you did that? in a maven build or only via eclipse?
neither, I did it manually.
ok, the new test result:
1. if
On Friday, February 14, 2014 2:37:02 PM UTC+8, Tapir wrote:
On Friday, February 14, 2014 2:13:20 PM UTC+8, Tapir wrote:
On Friday, February 14, 2014 6:23:38 AM UTC+8, Nick wrote:
Hi Tapir, I'm not sure I understand what you mean by this '*I think it
can't solve the warmup problem*'.
Our warmup time was 15 seconds, then I looked at the hello world project
that the GAE plugin generates with one servlet.
That took 2 seconds to startup (once the servlet was hit).
Then I added all the jars from our project but kept the same web.xml
configuration.
Startup time went up to almost
On Tuesday, February 18, 2014 3:57:37 AM UTC+8, Emanuele Ziglioli wrote:
Our warmup time was 15 seconds, then I looked at the hello world project
that the GAE plugin generates with one servlet.
That took 2 seconds to startup (once the servlet was hit).
On F2 instance?
Then I added all
On Tuesday, February 18, 2014 4:04:16 AM UTC+8, Tapir wrote:
On Tuesday, February 18, 2014 3:57:37 AM UTC+8, Emanuele Ziglioli wrote:
Our warmup time was 15 seconds, then I looked at the hello world project
that the GAE plugin generates with one servlet.
That took 2 seconds to startup
Not sure where my reply went.
On Tuesday, February 18, 2014 3:57:37 AM UTC+8, Emanuele Ziglioli wrote:
Our warmup time was 15 seconds, then I looked at the hello world project
that the GAE plugin generates with one servlet.
That took 2 seconds to startup (once the servlet was hit).
On F2
I think (and previous guidance supports this) that it isn't the loading of
the jars that is taking time, its actually fetching your war (and the files
in it, so *down*loading the jars) that is taking so much elapsed time. The
smaller your overall artifact, the quicker it can be pulled in and
On Tuesday, 18 February 2014 11:50:20 UTC+13, Nick wrote:
I think (and previous guidance supports this) that it isn't the loading of
the jars that is taking time, its actually fetching your war (and the files
in it, so *down*loading the jars) that is taking so much elapsed time.
The
On Tuesday, February 18, 2014 4:33:16 AM UTC+8, Emanuele Ziglioli wrote:
Not sure where my reply went.
On Tuesday, February 18, 2014 3:57:37 AM UTC+8, Emanuele Ziglioli wrote:
Our warmup time was 15 seconds, then I looked at the hello world project
that the GAE plugin generates with one
Unfortunately no, i can't provide links. Working with appengine for a few
years now, you tend to soak stuff up. Who knows whether it's current info.
If i get some time I might try a basic benchmark.
On Tuesday, February 18, 2014 10:31:17 AM UTC+11, Emanuele Ziglioli wrote:
On Tuesday, 18
If you have a very large and complex Java application, it might be easier
to simply run it (unchanged) on GCE rather than attempt to shorehorn it in
to App Engine's architecture. You could migrate functionality to App
Engine over time.
You still have to manage GCE instances (they don't
Hi Tapir, I'm not sure I understand what you mean by this '*I think it
can't solve the warmup problem*'.
Unfortunately (for everyone) there's no real avoiding waiting for startup
of your app with appengine right now.
The best you can do is make it as quick as possible. The key is to avoid
any
On Friday, February 14, 2014 6:23:38 AM UTC+8, Nick wrote:
Hi Tapir, I'm not sure I understand what you mean by this '*I think it
can't solve the warmup problem*'.
Unfortunately (for everyone) there's no real avoiding waiting for startup
of your app with appengine right now.
The best
On Friday, February 14, 2014 2:13:20 PM UTC+8, Tapir wrote:
On Friday, February 14, 2014 6:23:38 AM UTC+8, Nick wrote:
Hi Tapir, I'm not sure I understand what you mean by this '*I think it
can't solve the warmup problem*'.
Unfortunately (for everyone) there's no real avoiding waiting
On Friday, February 14, 2014 2:13:20 PM UTC+8, Tapir wrote:
On Friday, February 14, 2014 6:23:38 AM UTC+8, Nick wrote:
Hi Tapir, I'm not sure I understand what you mean by this '*I think it
can't solve the warmup problem*'.
Unfortunately (for everyone) there's no real avoiding waiting
On Friday, February 14, 2014 2:37:02 PM UTC+8, Tapir wrote:
On Friday, February 14, 2014 2:13:20 PM UTC+8, Tapir wrote:
On Friday, February 14, 2014 6:23:38 AM UTC+8, Nick wrote:
Hi Tapir, I'm not sure I understand what you mean by this '*I think it
can't solve the warmup problem*'.
Warren,
Compute engine wouldn't work with big table. Would it?
It would require a large migration. In that case people would probably go
full aws.
On Feb 12, 2014 11:52 AM, Warren Strange warren.stra...@gmail.com wrote:
Google Compute Engine would probably be a better option for a large
On Wed, Feb 12, 2014 at 8:28 AM, Rafael mufumb...@gmail.com wrote:
Compute engine wouldn't work with big table. Would it?
BigTable is available through the Cloud Datastore service. There's much
more configuration involved than accessing it through App Engine, but it is
possible:
On Thursday, February 13, 2014 7:17:18 AM UTC+8, Vinny P wrote:
On Wed, Feb 12, 2014 at 8:28 AM, Rafael mufu...@gmail.com javascript:
wrote:
Compute engine wouldn't work with big table. Would it?
BigTable is available through the Cloud Datastore service. There's much
more
On Sunday, February 9, 2014 11:48:44 PM UTC+8, Warren Strange wrote:
Google Compute Engine would probably be a better option for a large legacy
Java code base.
Haven't noticed your reply before.
Could you please explain more?
On Friday, February 7, 2014 12:16:14 AM UTC-4, Tapir
Google Compute Engine would probably be a better option for a large legacy
Java code base.
On Friday, February 7, 2014 12:16:14 AM UTC-4, Tapir wrote:
For the size of my project, I think it is impractical to port it to other
languages. :(
I tried python and go, their warmup time is very
Please define what is a large legacy Java code base”…
PK
http://www.gae123.com
On February 11, 2014 at 6:52:14 PM, Warren Strange (warren.stra...@gmail.com)
wrote:
a large legacy Java code base
--
You received this message because you are subscribed to the Google Groups
Google App Engine
I really like the basic part of your framework, the python route config
style and the simple view files.
For it is also based on servlet, I think it can't solve the warmup problem.
Bit I would give it a try in my later new projects.
On Monday, February 10, 2014 5:29:32 AM UTC+8, Nick wrote:
On Tuesday, February 11, 2014 1:32:23 PM UTC+8, Tapir wrote:
I really like the basic part of your framework, the python route config
style and the simple view files.
For it is also based on servlet, I think it can't solve the warmup problem.
Bit I would give it a try in my later new
Hi Tapir,
You could give porting your spring app over to the thundr framework a go:
http://3wks.github.io/thundr/ (usual disclaimer, I'm a maintainer)
The basic concepts are very similar to spring, so it should be relatively
simple. Its designed specifically to have fast boot up times on
Welcome to the club. People have been waiting for this for years.
On Feb 6, 2014 8:16 PM, Tapir tapir@gmail.com wrote:
For the size of my project, I think it is impractical to port it to other
languages. :(
I tried python and go, their warmup time is very short. For python, it is
less
Depends on the size of your project.
I started with plain java/jsp.
As the project grew the overhead of maintenance was so big that we opted to
moving everything to spring-mvc.
That move increased the instance boot time from 7 to 35 seconds. In order
to overcome cold startups we had to add 6
For the size of my project, I think it is impractical to port it to other
languages. :(
I tried python and go, their warmup time is very short. For python, it is
less than one second, for go, it is less than 0.5 second I think.
But Java still has a big advantage: large quantity of libraries.
So
Is it worth dong it?
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to
53 matches
Mail list logo