...
Info |
---|
OverviewThis working area is a broad investigation of the SOA and API spaces jointly. The popularity of commercial APIs, lightweight interfacing techniques have both overtaken and reinvigorated the need to apply SOA principles in the enterprise |
...
Section |
---|
Column |
---|
| Panel |
---|
Working GroupsWorking subgroups originating from an initial discussion are starting to take form. New participants and input is encouraged throughout. |
Panel |
---|
title | Want to Actively Collaborate or Contribute? |
---|
| Become a member of the main discussion list through Jim Phelps. Please see the Site Contributor Guide and review guidelines for wiki contributions. |
|
Column |
---|
| Panel |
---|
Big PictureHere is a simple draft taxonomy of the SOA API space based only on starting discussions. This overview will be useful to develop and refine as our interactions progress. SOA API Stages | Areas of investigation |
---|
Architecting/Selling | Determination of capabilities needed in an SOA API environment Leveraging Business Drivers (Analytics, Evidence-based decisions, monetizing access to enterprise data) Leveraging IT Drivers (better security, reduce complexity) Investigation of overlap with teaching and learning | Constructing/Deploying | Enterprise data defintion and management WS02 solution (selection, integrations, operations) Design of common API across higher education Securing APIs (authentication and especially authorization) Messaging (role of ESB solutions, push vs pull direction) Mobile device integration | Using/Governing | Creating public APIs (use cases, balancing openness and resource control) How to move enterprise from old techniques (ftp, direct database links) to SOA Impact on data custodians and new governance opportunities |
|
|
|
...
Working Groups
High-level Group (Contact: Jim Phelps)
For Evaluation work - Share what you went through in selecting your ESB software.
Why did you pick WS02? What else did you look at?
How are you using your ESB
Sharing Design Documents and Patterns
Sharing business cases and use cases used to make the case for investment
Are folks planning on single instance of an ESB or Federated so other Departments/Colleges can have their own?
And who locally (within University) manages/administers the ESB and other aligned software/services.
Best practices on integration between ESB and ETL.
What about changing out the infrastructure? What should I plan ahead for if I think we are going to change out our ESB?
What are the design concerns you should consider if you want to make the infrastructure swappable?
What about cloud deployment of the infrastructure either IaaS or Amazon WS / EC3?
Public access to data and API supporting community of developers
Data Definition and API Design Subgroup (seeking a leader for this sub-group)
...