@Hotsos 2009: Starting this blog
So here I am at Hotsos Symposium 2009. I've presented my vision on how to build "Window-on-Data" applications, yet again. I think it must have been the tenth time or so, ever since 2002, when I first...
View ArticleThe Helsinki declaration: observation 1
So why is this blog called the Helsinki Declaration? Obviously it has nothing todo with the real Declaration of Helsinki. Hence the "IT-version" postfix in the title above. In line with the text of the...
View ArticleThe Helsinki declaration: observation 2
To illustrate the second observation, let's take a look at the following quadrant. It maps character-mode / GUI-mode applications against stateless / statefull underlying protocol.At the end of the...
View ArticleThe Helsinki declaration: observation 3 (Yafets)
After observation 1 "we-do-not-use-the-feature-rich-DBMS", and observation 2 "we-are-still-delivering-UFIs-only-in-ways-much-more-complicated-than-we-used-to-do-so", let's move on to the third...
View ArticleThe Helsinki declaration: observation 4
So here is the last observation while looking back at 20+ years of (web) database application development. The fourth observation is about the required developer knowledge investment. How much time do...
View ArticleJ2EE and traditional MVC (Part 1)
A short note to new visitors: this blog documents my vision on how to build database web applications. Normally I do this by presenting a two hour presentation know as "A Database Centric Approach to...
View ArticleJEE and traditional MVC (Part 2)
In the previous post I gave a high level introduction into the MVC design pattern. This pattern classifies all code that you write to implement a database web application, into three classes:Model...
View ArticleWindow-on-Data applications
Up till now I have been focussing on technology. We have seen DBMS´s evolve, the web and n-tier architectures come into existence, Yafets prosper, and developer productivity go down the drain. I also...
View Article(slightly off topic) Chris Date event @Dallas
You may want to check out this unique event.[will return to the declaration shortly]
View ArticleIssues with current trend
In my last post I have introduced the code classification used by the Helsinki declaration (as opposed to MVC used by JEE):User Interface (UI) code: all code that creates UI and responds to events in...
View ArticleThe Helskinki approaches to WoD application development
[continuing from my previous post]In a very similar way as I did here for MVC, the Helsinki UI/BL/DL code classes can be mapped across the client, middle and data tiers too:What I do differently here...
View ArticlePeople ask the wrong question
People who know me, know that I am enthusiastic about Apex. But I am certainly not an Apex expert. By far not. The DBMS is where my knowledge is. But because they know of my enthusiasm, I often get the...
View ArticleHelsinki code layers in the DBMS
Ok, let's continue with the second part of "The Helsinki Declaration". That would be the part where I zoom in on the DBMS and show you how best to do this database centric thing.We have seen that the...
View ArticleResuming transmission...
I've been busy lately: preparing papers and presentations for the upcoming ODTUG, presenting at Hotsos-revisited, and presenting at the Dutch DBA-symposium. All spare time went into these activities,...
View ArticleRebound for database design?
My fellow Oaktable member Robyn Sands posted something very "inline" with the Helsinki declaration. Good comments too.
View ArticleTwo weeks to go for ODTUG
ODTUG Kaleidoscoop 2009 is approaching soon. I'll be hosting two presentations.Fat Databases: a Layered ApproachThis will basically be the Helsinki Declaration talk, only crammed into just one hour....
View ArticleThe Helsinki Platform
Nice picture from "OraDude" showing the Fat Database, or Helsinki's first observation.
View ArticleContinuing with part 2 of the Helsinki presentation
The second part of my two-hour Helsinki presentation brings the message that in order to avoid PL/SQL spaghetti when taking the "fat database" approach, one must employ a layered PL/SQL code...
View ArticleUsing pipelined table function as the UI API object
In my previous post I've introduced you to an example WoD application page, and showed how the render-flow could be built in an Helsinki manner using a ref-cursor. The UI technology stack would call a...
View ArticleArticle 2
Nice one:http://ora-00001.blogspot.com/2011/07/mythbusters-stored-procedures-edition.html
View Article
