Back to Ext Javascript

Back to UI enhancement today putting reports results into a grid in a flexible manor. Big debate is whether to go for a html approach and use javascript as conversion of the presention, or drop presentation and go for JSON data hash to client and do the full presentation there.

HTML has better fallback to hmtl but JSON as less traffic and server overhead. Currently prototyping the JSON route. But a close call really.

How to you pick a database.

How to you pick a database. Normal answer is the customer desides for you if is a large project with a must run on X.

If given a free choice the decision goes like this.

1. Database size > x 100 server memory given me Oracle any day.
2. Database size < x 10 server memory any big name database will work well
   
3. Database <= server memory would use postgres as default , using it on off for years, its does everything a rdms should.

When your having rows appears in 10M blocks oracle partitioning and other trick are a god send. Otherwize most of the database out they do eventhing needed.

In the old 2 tier client/server days, always went for oracle because of Pl/Sql and used the oralce as combined application server and database with all business logical in the database. Now with n-tier only really want the database to do SQL database stuff to dont care so much. In porting applications arround the playing field very level for both open source and commerical offerings. All major ones to joins,foreign keys, unions etc.

Process v.s. Productivity

Spent the day replying to a RFP.
Client done a great job of written the RFP. Only real worry is with the amount of work in the document and our reply may actually be the same as actually doing the project in Rails.