• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WO and criteria for choosing a database server
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO and criteria for choosing a database server


  • Subject: Re: WO and criteria for choosing a database server
  • From: Hunter Hillegas <email@hidden>
  • Date: Thu, 15 Dec 2005 22:35:28 -0800

We have excellent success with PostgreSQL and WebObjects.

It is much more 'Oracle-like' than MySQL, supporting many of the same features (tablespaces, etc...).

It has great JDBC support and works like a charm.

On Dec 15, 2005, at 9:20 PM, Chuck Hill wrote:

Hi David,

On Dec 15, 2005, at 2:52 PM, David Holt wrote:

Following on to the "images in the database" discussion from earlier in the week, I have been searching the archive for "Which Database?" discussions. So far my experience tells me that WO makes up for the limitations of databases such as MySQL for small applications under moderate load.
I came over from the world of PHP

<shudder>

and found data validation, referential integrity, and transaction support built right into the WO frameworks. Here are some of the external factors that I can think of that would influence a decision for choosing one database over another to use with WO:

1. performance under load is much better in some databases
2. price (of course)

Well, that leaves Oracle out.

3. there are data types that are not available in all databases

I avoid the use of special data types, triggers, stored procedures and other vendor specific features. I don't really want to have to care about what database is behind my apps. If your organization is standardized on one then it might make sense to use these.


4. some databases have better administration/maintenance tools

Well, that leaves Oracle out.

5. encryption (communication and storage) is supported in some databases
6. you're dealing with legacy systems


Since WO abstracts away from the database so well, does it really matter which database you choose?

No, not really, as long as it can handle the load you will have.

Does it come down to personal preference?

Maybe not personal preference so much as:
- do I have a compelling reason to use Open Source?
- how much do I value sql92 compliance for when I have to write SQL manually?
- is good, paid support worth it to me?
- will it scale to the data sizes that are likely to be needed?
- which databases are familiar to the organization where the app will be deployed (might be ISP etc)?



I have come across arguments for using almost every major database in the archives (most of them quite dated). My question is whether anyone has had any WO experience with a recent version of a database server that would tell you to never use it again for WO applications?

Yes, Oracle. It is too expensive and too much effort to administer. It works fine, but who needs the expense and aggravation?



If not, what criteria do you currently use to choose the database (s) you are using for WO?

Mostly the above ones. Where Open Source is not a requirement, we have found FrontBase to be an excellent balance of cost vs sql92 support, speed, scalability, ease of maintenance, and technical support. It just quietly does its job and does it well.


Where Open Source is important, PostgeSQL is probably the way to go. I have not used it enough to be able to personally attest to speed, scalability, or ease of maintenance. So far, I have been quite impressed with it though.

OpenBase is another one that people seem to like. I have some friends that rave about it. It certainly has pretty admin tools. It is not sql92 standard though and I have had some problems when I try to do something slightly out of the ordinary (like multi-column indexes). I've never really warmed to it, but that might be simple prejudice (I know and trust FrontBase).

Here is the current list of officially supported databases from the Apple WO page:

Database servers
	▪ 	Microsoft SQL Server 2000 8.00.194
	▪ 	MySQL 4.1.10a
	▪ 	OpenBase 8.0
	▪ 	Oracle 10g Enterprise Edition
	▪ 	Oracle 9i Enterprise Edition Sybase ASE 12.5


Chuck

--
Coming in 2006 - an introduction to web applications using WebObjects and Xcode http://www.global-village.net/wointro


Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/ practical_webobjects




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >WO and criteria for choosing a database server (From: David Holt <email@hidden>)
 >Re: WO and criteria for choosing a database server (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: WO and criteria for choosing a database server
  • Next by Date: How to install WebObjects deployement on OS X 10.4 Server
  • Previous by thread: Re: WO and criteria for choosing a database server
  • Next by thread: Re: WO and criteria for choosing a database server
  • Index(es):
    • Date
    • Thread