PDA

View Full Version : WebObjects development



BrentusAsparagus
29th June 2007, 12:38 AM
Hi there,

Sorry if this is the wrong place to post, couldn't spot a better one though.

I'm wondering if anybody knows of / can recommend any commercial developers specialising in WebObjects development?

Sydney based, preferably.

Just feeling the waters at this stage. Thought there might be a few amongst the MacTalkers...

Thanks

Quamen
29th June 2007, 09:03 AM
You might find something here: WOCode (http://wocode.com/cgi-bin/WebObjects/WOCode.woa/1/wa/loadSection?sectionId=3&wosid=jcdSrC1ziUztcqiPjFOGr0).

Otherwise you might want to call Apple and ask them? They probably have a list of developers somewhere, or will at least be able to point you in the right direction.

W2ttsy
29th June 2007, 09:57 AM
not to be rude, but why specifically WOA?

its a proprietary technology that only runs (stable) on a Mac OS X based system (windows is no longer supported and the Linux/Apache plugin isnt really suitable for enterprise level roll out)

If youre after Java level programming for the web, then JSP/tomcat is the best method. Runs on any platform, and you can use raw Java for your application backend and JSP for your front end. Plus you will find alot more companies that support the development of that.

Just throwing it out there.

W2ttsy

BrentusAsparagus
29th June 2007, 10:07 AM
Thanks - WOA was just the first massively scalable rapid development multi tier architecture supported on the OSX platform I came across. Its pre-configured clustering / session management / visual designers etc look rather compelling from a rapid development point of view.

The client is looking for a transactional website which has real-world (and short term), potential to scale to hundreds of thousands of users, but needs it developed in a matter of a few months. I haven't dealt with scalability on this level before (thousands of users being my 'peak'), so am scoping the options. Of course, OSX isn't an absolute requirement but it would be nice.

I'll look into the JSP/tomcat option. Any other suggestions would be more than welcome!

Thanks


not to be rude, but why specifically WOA?

its a proprietary technology that only runs (stable) on a Mac OS X based system (windows is no longer supported and the Linux/Apache plugin isnt really suitable for enterprise level roll out)

If youre after Java level programming for the web, then JSP/tomcat is the best method. Runs on any platform, and you can use raw Java for your application backend and JSP for your front end. Plus you will find alot more companies that support the development of that.

Just throwing it out there.

W2ttsy

Quamen
29th June 2007, 11:41 AM
not to be rude, but why specifically WOA?

its a proprietary technology that only runs (stable) on a Mac OS X based system (windows is no longer supported and the Linux/Apache plugin isnt really suitable for enterprise level roll out)

If youre after Java level programming for the web, then JSP/tomcat is the best method. Runs on any platform, and you can use raw Java for your application backend and JSP for your front end. Plus you will find alot more companies that support the development of that.

Just throwing it out there.

W2ttsy

I thought WebObjects could deploy on any J2EE/J2SE platform? Also I think the roadmap for WebObjects is to open source it as of version 5.4 (next release).


Thanks - WOA was just the first massively scalable rapid development multi tier architecture supported on the OSX platform I came across. Its pre-configured clustering / session management / visual designers etc look rather compelling from a rapid development point of view.

The client is looking for a transactional website which has real-world (and short term), potential to scale to hundreds of thousands of users, but needs it developed in a matter of a few months. I haven't dealt with scalability on this level before (thousands of users being my 'peak'), so am scoping the options. Of course, OSX isn't an absolute requirement but it would be nice.

I'll look into the JSP/tomcat option. Any other suggestions would be more than welcome!

Thanks

Is our client sure of that scalability requirement? Rapid development and scalability don't really go hand in hand.

If they can throw hardware at the problem then Ruby On Rails would probably give them a faster development cycle.

BrentusAsparagus
29th June 2007, 11:54 AM
They're forecasting rapid growth from nothing to 10000+ regular users in the first few months, scaling up proportionally over the next three years. Obviously it's all conceptual now so it may not play out like that, but they want to build the infrastructure to cope if it does.

I agree regarding the rapid development vs. scalability comment. Personally I have difficulty envisioning how this will all come together in time without some seriously talented developers. However, they are working towards a perceived market opportunity the entry point for which is open for a very narrow period of time. Hence the rush.

There is talk about a 'first version' which could cope for a while (while the bulletproof version is being built). Obviously it would be nice to be able to scale up the v1.0 product rather than have two parallel disconnected efforts with the necessary migration in the future... but it may come to that.


Is our client sure of that scalability requirement? Rapid development and scalability don't really go hand in hand.

If they can throw hardware at the problem then Ruby On Rails would probably give them a faster development cycle.