Patterns Refactored for the Cloud

Patterns Refactored for the Cloud Over the last six years, we've discussed “patterns” with several of our large system partners. Every one seems to come up with a hierarchy, usually at 3 or 4 levels. An example:

Solution

Micro-Architectures

Implementations

Operational/Run-time

How does this apply today? This structure forms the model on how this complex state machine operartes. At each level, there is different data required to solve for the dependencies. At the high level, implementation is far removed. Today, IT folks manage “images” -- binary blobs that represent so many things that they are difficult to control and decompose. Advanced developers deploy using OSGI. This is the difference that needs to be explored.

Images are a deployment payload

Models are the structures defined by the system

APIs and “Instruction sets” define tell the system how to operate at run-time

Policy help defines the “what” happens when and are in play even prior to run-time

Views are consistent – ie what a developer sees is different but is in the model such that an admin can see what's going on in the environment as necessary. An operator can “destroy” which effects the developer “view” should it be necessary.

Comments:

Post a Comment:
Comments are closed for this entry.
About

Thoughts from Jason Carolan -- Distinguished Engineer @ Sun and Global Systems Engineering Director - http://twitter.com/jtcarolan - http://archmatters.wordpress.com

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today