[nl]

I'm considering it (applying, not using AppEngine. If I apply I'll use AppEngine for some parts of it).

I do Java AppEngine work in my day job, so if you have questions let me know.

(When you say "enterprise focused" do you mean your application is enterprise focused, or do you mean GAE/J is? Because there are some issues with using GAE for enterprise software and it's important you have considered them)

[mel_llaguno]

Can you elaborate? I'd be curious to know what limitations you've experienced that work against GAE for enterprise deployments.

[nl]

(To be clear, I'm not using AppEngine for enterprise software. But I've done lots of enterprise software in the past, and I'm doing AppEngine now)

The main problems are as follows: 1) Data privacy. Usually this is just people worrying unnecessarily, but sometimes there are legal requirements about where customer data is stored. These may be jurisdictional or geographic requirements.

2) Integration issues. Enterprise software is all about integration. The AppEngine integration story is getting better, but you'll need to understand the SAML based single-sign-on support that is built into Google Accounts and/or implement it yourself, and you'll need to become familiar with Secure Data Connector (http://code.google.com/securedataconnector/) to integrate with private data sources.

[mel_llaguno]

Thanks for the info. I'm pretty sure I won't need SAML for my application, but the Secure Data Connector is definitely something that I will be looking into.

[mshafrir]

Also, mind sharing what type of work you do that you get to use AppEngine on the job?

[nl]

I'm not allowed to talk about the details actually. But it's consumer focused, using GWT.