Ck out this crash course in getting a java app up from scratch... http://goo.gl/UT2W3
My personal recommendations: - plan on spending a week or two learning how the datastore works before you get started - if you will ever need the High Replication Datastore, set it up now. it's a pain to add it later - wrap all data access in daos - wrap all gae services in daos - use slim3 for database access to get around "updating 2 entities in a single transaction" limitation - use stripes for the web framework to keep startup times under 3 seconds - use https for everything (firesheep is looking for your cookies) - convert to app engine biz accnt and pay the $9/mnth for 3 always-on servers. even 3 seconds start-up times make an app unusable for most folks - use jquery for minimal layout, do everything else in jsps to generate jquery content upon form post - add code to detect when datastore is read-only and handle it with a custom page (maybe a javascript game, tetris?) - add a apple-touch-icon.png touch icon so people can save your app to their phones - plan for mobile support from day one, ck out jquerymobile.com - volume test your site using jmeter to see how it will handle massive traffic spikes - pay me for not having to learn the hard way like I did :) On Apr 1, 7:38 am, Drew Spencer <[email protected]> wrote: > Hi all, > > Totally new to this, about to embark on a development for my own business > and think that GAE is the perfect solution. I basically want to make sure > that we are making the right choice, and to be informed of any pitfalls > early on. > > Basically the system will be a complete intranet/sales tool based around a > rather complex pricing engine. I have previous experience using Codeigniter > + Doctrine, but after tinkering with v2.0 for a while it just seems like it > is very buggy, and still has many limitations over using Java. > > We already use google apps for mail and have a simple intranet built on > google sites so users will be using their company email account for > validation. > > There are a few key features we need: > > - Small number of users (~100) > - Integration with salesforce.com (Using the force.com API?) > - Integration with Gmail so that the system can automatically log and > send emails, as well as pick them up. (Using IMAP/SMTP?) > - Ability to upload and store basic files that can be downloaded by staff > (Using docs API, or just datastore?) > > If anyone can advise of any things to investigate right now that would be > really helpful. > > I have quite a few years experience programming, and a willing assistant > with a bit of OO knowledge, other than that I will be learning to use things > like JDO and JSP for the first time. > > All of your input is appreciated. > > Drew -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
