"The dream behind the Web is of a common information space in which we communicate by sharing information. Its universality is essential: the fact that a hypertext link can point to anything, be it personal, local or global, be it draft or highly polished."
Home of the
A prototypical enterprise that works with the principles of a Resource Oriented Architecture.
These concepts have proven to be extremely flexible, reliable and scalable. And these qualities are badly needed, because the ROE is like most enterprises today: an ever moving ecosystem with changing organisational structures, including acquisitions; deals with a multitude of external customers and suppliers; it is subject to new regulations; creates an unbelievable amount of data every day, and so on...
To model and support its real world activities, the ROE adapts an IT architecture based on the principles of the Resource Oriented Architecture (ROA). It relies on the proven concepts of the WWW, as denoted in the epochal doctoral thesis of Roy T. Fielding, commonly known as REST architecture style.
The ROE integrates its information with the power of HTTP and the Universal Resource Identifiers (URIs), implements it with commonly available and relatively low priced infrastructure and - most importantly - makes its business the big winner of a simplified SW architecture!
The Web & YOU
A presentation held for the Swiss ARMA chapter about the usage of the Web information model for Enterprise Records- and Information Management. click here
ROE in 30 seconds
Learn with this animation about ROE's central concepts here>>
The Business Case
Few things are harder to do than to write a business case for SOA. Here's our take on that. Because ROE is not a real enterprise, don't expect hard figures, but do expect some thoughts on advantages and risks of going RESTful, and a SWOT analysis. more>>
The Resource Oriented Enterprise — What is it?
Today, HTTP is heavily used in enterprises to transport data; however, it is not really appreciated as a complete protocol. All sorts of additional protocol stacks are written on top of it, thereby obscuring the real power of HTTP.
Thus, the first step when forming a ROE is to change our mindset: we must respect that HTTP is a full-fledged communications protocol that satisfies by itself the needs of almost all modern business applications. Applying HTTP in a consequent way, we can eliminate dozens of unnecessary software layers, taking many protocols as superfluous to trash, thereby simplifying the enterprise architecture. A Resource Oriented Architecture yields better to maintain, faster, and more flexible systems that require less IT resources. And URIs dramatically improve the addressibility of information fragements of any type in and outside the enterprise. more>>
A closer look at a Resource
The Resource is the central element and abstraction in the Resource Oriented Enterprise and in Fielding's REST. It has many interesting qualities that we describe in the following article. more>>