Use Siebel as part of the source of your architecture ideas and spring.net and ajax

Use Siebel as part of the source of your architecture ideas

1. As explained in my previous blog, Siebel is pretty good -- even it has its "weirdness".
2. The special thing about Siebel is that its UI has strict rules corresponding to its entities and facades. It can do that because its UIs have strict rules -- sometimes counter-intuitive, but general and powerful.
3. Other than that, Siebel is basically a proprietary "close-to-best-practices" for all other things ("8 core techniques"), including centralized security, logging, validation, and even OR mapping, and it does not use stored procedures (and even not FKs! -- that is too extreme though).
4. As a result, Siebel is worth it to be a source of your architecture.
5. Further, once you use Siebel, it is inevitable that it will influence your architecture. You have to build other things to inter-operate with it.
6. The key of using Siebel as the source of your architecture, but not just "copy" it, is to abstract it into "8 core techniques" -- then, it is obvious that we should use spring.net and ajax.