Web Oriented Architecture (WOA) Gluecon, May 2010

Web-Oriented ArchitectureOriginally presented at Gluecon 2010
Aaron Fulkerson
@roebot

About MindTouch
Open source company
Strategic documentation platform
And a new kind of ECM
Projects
DReAM
SGMLReader
MindTouch Core/2010

What is WOA?

WOA in a Nutshell
(
)
REST
WWW
WOA
*Originally coined by Nick Gall @ironick (Gartner) 2005

REST Cheat Sheet
Representational state transfer (REST) is a style of software architecture for distributed hypermedia systems such as the World Wide Web. (source: Wikipedia)
Principles
Everything is a RESOURCE
Every resource has a REPRESENTATION
Every resource has a canonical NAME
There is a finite VOCABULARY of actions
State transitions require DISCOVERY

WOA in a Nutshell
Information is represented as Resources
Resources are identified by URIs
Resources are manipulated via HTTP
Contracts are implicit in the representation of the resource
Interfaces are generic

REST applied to WWW

God Bless HTTP
Leverage HTTP to its full potential
Simple: verbs, headers, status codes
Scalable: every operation is self-contained
Every browser can be a client
Easy discovery
Easy debugging
Build on existing (standard) infrastructure
Proxies
Load balancers

Of Clients and Servers
In WOA…
Services rely on other services
Communicate over HTTP
Are clients of some resources and servers of others
Extensibility, Scalability == Interconnection

Web APIs everywhere
APIs allow others to integrate with you
Simplifies integration
Frees you from custom engineering for partners
Fosters “Unexpected reuse”
Let others provide features not on your roadmap

Most APIs are Data Island Veneer
Closed, specific internal architecture
Only exposes use cases directly envisioned by API designers
Only outward facing
Do not aid internal integration stories

Web APIs, WOA style
Connect internal systems over REST services
Internals become generic
Extensibility becomes application neutral
Location, availability and breadth of dependencies can take advantage of HTTP
Enables internal innovation without requiring integration work

API first!
Don’t expose a feature after the fact via an API
Build an API for every feature first
Better understanding the feature by internal and external consumers
No blind spots of API inaccessible parts

A word about MindTouch Core/2010
Open source collaboration platform
for the enterprise and the web
Built with Mono/.NET and PHP
Runs on SLES, RHEL, Debian/Ubuntu, Windows and even Solaris
Downloaded over 500,000 times
Used by over 15M people
MindTouch is API first!

Application Architecture
Email
Authentication
Extensions
Scripts
Package
Core
Subscriptions
Lucene
PubSub
Varnish
PubSub
Host
Storage
MindTouch DReAM

MindTouch API
http://developer.mindtouch.com/Deki/API_Reference
Exposes capabilities of MindTouch as web services
MindTouch web UI uses API
Anything the web UI can do, a third party can do
Uses REST for extensibility
Service Discoverability
@blueprint
@about

Some links
http://developer.mindtouch.com/en/ref/MindTouch_API (glorious)
http://developer.mindtouch.com/@api/deki/@blueprint
http://developer.mindtouch.com/@api/deki/@about
http://developer.mindtouch.com/@api/deki/pages/3228
http://developer.mindtouch.com/User:AaronF
{{web.xml("http://developer.mindtouch.com/@api/deki/pages/3228/contents?format=xhtml")}}
http://developer.mozilla.org
www.Shelfari.com
www.Whorunsgov.com

Extensibility
Web Services
Standalone services
Local or remote
Only requirement: provide a REST API
Extensions
Hosted or remote
DekiScript Extensions
Hosted or remote
Native or script

Architectural Benefits
100% API coverage there’s an API for that
Uniform programming model
One model to rule them all!
Agnostic extensibility
Any programming language
Hosted anywhere on the network
Flexible deployment topologies
Many sites on one machine
Many machines for one site

The DReAM REST framework
MindTouch is built on DReAM
DReAM optimizes REST calls within framework, by providing an in-process HTTP pipeline
Local REST calls do not hit the wire
Serialization/Deserialization only required for out of framework calls
Local Routing of bypasses DNS

WOA makes your life easier
Simplifies extensibility, scalability
Reduces development time for new features
Reduces engineering time spent on integration
Creates opportunity for mash-ups and other unforeseen user stories

Thanks
Aaron Fulkerson
@roebot

http://www.readwriteweb.com	241
http://innovacion.ticbeat.com	164
http://www.mindtouch.com	103
http://www.slideshare.net	97
http://www.ticbeat.com	66
http://webtechman.com	21
http://readwrite.com	18
http://www.readwriteweb.es	9
http://innovacion.readwriteweb.es	8
http://swik.net	6
http://static.slidesharecdn.com	6
http://translate.googleusercontent.com	2
http://reader.youdao.com	1
http://elsterama.com	1

Web Oriented Architecture (WOA) Gluecon, May 2010

by MindTouch on May 29, 2010

Accessibility

Categories

Upload Details

Usage Rights

14 Embeds 743

Statistics

Web Oriented Architecture (WOA) Gluecon, May 2010 Presentation Transcript