Service Oriented Architecture Forum
Topics 120
Comments 22
| Topic | Author | Replies | Last Post | |
|---|---|---|---|---|
|
|
OW SOA empowered Shipbrokers
Abstract Here you will get an overview of the service categorization model used in a ship broker solution developed for to two major Norwegian ship brokers. We will show how categorized services provide a cleaner, more flexible and maintainable architecture ...
|
|
0 | - |
|
How does OW SOA relate to REST
an interesting question. There are in fact one key similarity between OW SOA (unlike most other SOA strategies) and EA:REST, and that is that OW SOA puts resources/business data as first class citizens of the architecture (ACS and CS category ...
|
Thor Henning Hetland
|
0 | - | |
|
|
EDR-MDS - Real Business Value Delivered - Business Cases
State of the art Enterprise Portal delivering value built on an Service Oriented Integration strategy realized through Enterprise Domain Repositories" IT Strategy Established a modern, flexible Service Oriented Architecture aligned with its business processes. The SOA implementation ...
|
Thor Henning Hetland
|
0 | - |
|
|
Service Categorization - Real Business Value Delivered - Business Cases
Telecommunication Company "State of the art Enterprise Portal delivering value built on an Service Oriented Integration strategy realized through Enterprise Domain Repositories" IT Strategy Established a modern, flexible Service Oriented Architecture aligned with its business processes ...
|
Thor Henning Hetland
|
0 | - |
|
|
Service categorization and SOA patterns 911
h3 Abstract Agenda SOA in 2 slides system strategy laws of SOA Service categorization motivation categories design rules Service Categorization Real Business Value Delivered Business Cases Harvest value from existing investments with EDR ...
|
Thor Henning Hetland
|
0 | - |
|
Service Oriented Architecture Forum
Service Oriented Architecture Forum
|
Thor Henning Hetland
|
0 | - | |
|
Too generalized portlets
|
Thor Henning Hetland
|
0 | - | |
|
One portlet does it all
|
Thor Henning Hetland
|
0 | - | |
|
If your portlets share more than 2-4 global parameters, you are getting into trouble
|
Thor Henning Hetland
|
0 | - | |
|
High coupling in portlets and portlet container
|
Thor Henning Hetland
|
0 | - | |
|
Tightly coupled and big-bang deploy and production, error-prone processes
|
Thor Henning Hetland
|
0 | - | |
|
No strategy for versioning and multi-versioning
|
Thor Henning Hetland
|
0 | - | |
|
Unclear responsibility and definition of services..
|
Thor Henning Hetland
|
0 | - | |
|
High evolve ability and changeability costs
|
Thor Henning Hetland
|
0 | - | |
|
Portlets grow huge and complex
|
Thor Henning Hetland
|
0 | - | |
|
Difficult to develop and test portlets _out of context_
|
Thor Henning Hetland
|
0 | - | |
|
High round-trip cost when developing portlets
I have been working on a solution for this for a while. The result is the "mavenjettyplutoembedded" project: http://boss.bekk.no/display/BOSS/MavenJettyPlutoEmbedded I have written about this in my blog as well: http://portletwork.blogspot.com http://portletwork.blogspot.com/2007/10/easyportletdevelopmentandreduced.html
|
Thor Henning Hetland
|
1 | |
|
|
|
Portal strategies
Characteristics Technology/developer driven "Not invented here" RSS/Agile/antiJEE Characteristics "Next version" syndrome High maintenance costs Low platform value in real projects Characteristics Pick niche and lightweight JSR 168/286 portlets, webpart for MS ...
|
Thor Henning Hetland
|
0 | - |
|
Case - Return Of Investment of a company internal strategic knowledge initiative
|
Thor Henning Hetland
|
0 | - | |
|
Mini-Case - Analysis of email traffic - Data warehouse or enterprise search platform?
|
Thor Henning Hetland
|
0 | - | |
|
|
Scalability Axiom no 3 - Divide and Conquer
Since simplicity rules http://labs.google.com/papers/mapreduce.html an all massive scalability strategies, we need to ensure that we are heavy on the divide and conquer bandwagon when building scalable solutions. !mshn69l.jpg
|
Thor Henning Hetland
|
0 | - |
|
|
Scalability Axiom no 1 - Utmost scalability
Tight data and function at the usage edge is the utmost of all scalability options. Latency Latency is Everywhere and it Costs You Sales How to Crush it http://highscalability.com/latencyeverywhereanditcostsyousaleshowcrushit Latency is Everywhere and it Costs You Sales How to Crush it My Take http ...
|
Thor Henning Hetland
|
0 | - |
|
Scalability Axiom no 2 - CAP theorem
What goals might you want from a shareddata system? Strong Consistency: all clients see the same view, even in presence of updates High Availability: all clients can find some replica of the data, even in the presence of failures ...
|
Thor Henning Hetland
|
0 | - | |
|
What does it mean to "provide great service"?
Q: I find the last statement of the manifest vague. What does it mean to "provide great service"? It is so vague that it doesn't have much value in a service manifest IMHO. A: The Service Responsibility REQUIRED: Fulfill the Service Contract RECOMMENDED: Fulfill ...
|
Thor Henning Hetland
|
0 | - | |
|
Service Manifest FAQ
What does it mean to "provide great service
|
Thor Henning Hetland
|
0 | - |
