Open Web Services & SOA
A complete end-to-end SOA strategy to ensure that customers can get return on investment (ROI). The result is a no-nonsense SOA with clear directions that • puts IT and business on the same path • ensures the evolvability of services • ensures continuous creation of business value This workspace is committed to improving this strategy.
- A software architect is a part-time Archeologist
- A2A
- ACS
- Access Manager (AM)
- Aggregated Core Services
- Aggregated Core Servives
- Alignment of Business Intelligence and Service Oriented Architecture
- Alignment of Enterprise Search Platforms (ESP) and Service-Oriented Architecture
- Application 2 Application Services
- Application to Application Services
- Architecture
- Architecture Principles and Axioms
- Are there alternatives to this SOA Service Categorization? Which?
- Availability Over Consistency
- Build to excel, buy to support
- Business Intelligence (BI) and Enterprise Search in a Service Oriented Architecture Strategy
- CS
- Case - Return Of Investment of a company internal strategic knowledge initiative
- Categorized Services Pattern
- Command Pattern
- Core Services
- Data Processing
- Data Warehouse (DW) and Business Intelligence (BI)
- Democratic Master (DM)
- Design-Time Governance - SOA Design Rules
- Design-Time Governance - SOA Design Rules FAQ
- Design-Time Governance for A2A Services
- Design-Time Governance for ACS Services
- Design-Time Governance for CS Services
- Design-Time Governance for H2A Services
- Difficult to develop and test portlets out of context
- Distributed IAM checklist
- EDR Simple Master Mapping
- EDR-MDS - Real Business Value Delivered - Business Cases
- Enterprise Architecture (EA)
- Enterprise Domain Repository Pattern
- Evolving Service Endpoint Pattern
- Evolving excellent IAM People
- Example solutions combining Service-Oriented Architectrure, Business Inteligence and Enterprise Search Platforms
- From EA to SOA (and back)
- Generating OpenESB artifacts with Maven 2
- Getting Started with SOA
- Glossary
- Governance
- H2A
- High coupling in portlets and portlet container
- High evolve ability and changeability costs
- High round-trip cost when developing portlets
- HotChanges
- How does this SOA relate to Guerilla SOA?
- How does this SOA relate to Mark Little SOA
- How does this SOA relate to REST
- How? Eventing?
- Human 2 Application Services
- Human to Application Services
- Hva gjør tjenesten?
- I don't think I understand what's meant with law 4 and 5 (I understand the words, but not what you want people to do and when)
- I think I agree with law 3, Establish service ownership and Key Performance Indicators for your services, but an example of a KPI would be helpful
- I think I agree with law 8, Security is not optional in SOA, but I don't understand what you mean by it yet
- Identity Management (IdM)
- If your portlets share more than 2-4 global parameters, you are getting into trouble
- In SOA - Is my customer the same entity as your customer? Is my product list the same as your product list? In which situations?
- It is all about the data
- Last Attribute Update Wins (LAUW)
- Law 1 and 2 - Does this mean that you recommend small, fine grained services?
- Master Changed OOB-Update Remaining Sources (McOOBURS)
- Master Data Management Notes
- MasterPerAttribute
- Metadata
- Mini-Case - Analysis of email traffic - Data warehouse or enterprise search platform?
- Navigation
- No strategy for versioning and multi-versioning
- OW SOA empowered Shipbrokers
- Old front page
- One portlet does it all
- Our Heroes
- P1. A service shall have one named owner
- P2. A service shall provide documented business value
- P20. All services shall be in the service universe
- P21. A service shall be categorized (OW SOA category)
- P22. A service shall have an "authentication, authorisation, endpoint strategy"
- P23. A service shall document its Service Level Agreement SLA (response time, availabillity++)
- P3. A service shall do one only thing, and one thing well
- P30. A service shall have a versioning strategy (ACS, CS)
- P31. A service shall provide for audit and monitoring of service usage
- P32. A service shall document its Service Level Agreement SLA (response time=30ms, availabillity=99.995%)
- P4. A H2A service (webpart or portlet) shall be an independent component
- P40. A service shall provide at least one Evolving Service Endpoint
- P41. A service shall provide heartbeat and traffic monitoring
- P42. A Core service shall have orthogonal functionality
- P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
- P6. A H2A service shall not have internal workflow
- P7. Too generic webparts or portlets shall be avoided
- P90. A service shall have a documented coupling to the contractual and requirement for service usage
- PAB
- Pattern Wiki Template
- Policy Advisory Board
- Portal strategies
- Portlets grow huge and complex
- Presentation Repository
- Publications
- Real SOA versus REST
- RecommendedReading
- Recording Command Pattern
- Recording Proxy Pattern
- Relationship to other SOA strategies FAQ
- Requirements for container application
- SOA
- SOA - Service Categorization
- SOA - Service Categorization FAQ
- SOA - Services and service invocation
- SOA Community Home
- SOA Patterns
- SOA for Architects
- SOA for Developers
- SOA security and IAM
- SaaS BI Comparison
- Scalability Axiom no 1 - Utmost scalability
- Scalability Axiom no 2 - CAP theorem
- Scalability Axiom no 3 - Divide and Conquer
- Scrapyard
- Seamless integration of JAX-WS and Spring Framework
- Search-driven Business Intelligence
- Security Token
- Self Monitoring Service Pattern
- Service Assembly Pattern
- Service Categories
- Service Categorization - Real Business Value Delivered - Business Cases
- Service Dialect Adapter pattern implemented as JAX-WS handler
- Service Management, Operations and Monitoring
- Service Manifest
- Service Manifest FAQ
- Service Oriented Architecture FAQ
- Service Oriented Architecture Forum
- Service categorization and SOA patterns 911
- Smart Service Proxy Pattern
- Software Design
- Source Code
- Statistics
- Successful IAM Person
- SurrogateMaster
- Synchronization
- The Laws of SOA
- The laws of SOA FAQ
- The most common portal project mistakes
- Tightly coupled and big-bang deploy and production, error-prone processes
- Too generalized portlets
- Traditional Single System Master
- Unclear responsibility and definition of services..
- WebServices can lead to function oriented services, while REST can lead to a resource oriented architecture. Are both SOA?
- What does it mean to "provide great service"?
- When do I need to start thinking about Service Categorization?
- out-of-bounds updates