Home / Archive by category "Presentation"

Composite UI for Service Oriented Systems – Challenges Part II

This blogpost is part of a larger blog post series. Get the overview of the content here.

Slide94

Start early with an automated deployment. It will safe your ass! But try to keep it as simple as possible. If your deployment gets to complex this usually indicates that your “thing” decomposition is also too complex. Tools like Octopus Deploy or the Deployment Manager from Redgate help to visualize and monitor the deployment process to multiple environments. Keep in mind that managing the configuration files can be tricky and design for it from the beginning. Continue reading

Composite UI for Service Oriented Systems – Challenges Part I

This blogpost is part of a larger blog post series. Get the overview of the content here.

Slide88

Speaking about trade-offs. You’ll face some challenges regarding decomposition. But rest assured composition isn’t a piece of cake either. There are a number of challenges you’ll face and I’m sure there are even more I haven’t discovered yet. But surely you’ll tell me when you stumble over one in your project, don’t you? Continue reading

Composite UI for Service Oriented Systems – Composition Patterns

This blogpost is part of a larger blog post series. Get the overview of the content here.

Slide85

 

The Composite Front End pattern glues “things” together as a cohesive whole still keeping them autonomous. The Composite Front End patterns takes the ideas of web portals and applies them to SOA. It is composed of two main components: the portlet and the host. Continue reading

Composite UI for Service Oriented Systems – Mashup means bringing it together

This blogpost is part of a larger blog post series. Get the overview of the content here.

Slide83

A frontend is not owned by a single “thing”. It is a mashup of multiple “things” combined together to provide a single user experience. Looking at it from the deployment perspective we can say that many “things” can be deployed to the same box, many “things” can be deployed in the same app, many “things” can cooperate in a workflow and many “things” can be mashed up in the same page. Which brings us directly to service composition. Continue reading

Composite UI for Service Oriented Systems – Immutable and stable

This blogpost is part of a larger blog post series. Get the overview of the content here.

Slide76

Immutable data is unchangeable once it is written. An immutable data needs an identifier which allows to always return the same data no matter when it is requested or where it is request. Immutable data can be found everywhere in the real world. Continue reading

Composite UI for Service Oriented Systems – Services are not webservices

This blogpost is part of a larger blog post series. Get the overview of the content here.

But messaging alone is not enough! We need to decompose our system. Service Orientation can help us with that. Service Orientation or Service Oriented Architecture was first used in 1996 when Roy Schulte and Yeffim V. Natiz from Gartner defined it as “a style of multitier computing that helps organizations share logic and data among multiple applications and usage modes”. Unfortunately the term SOA has become a loaded term filled with misconceptions and hype. Continue reading

Composite UI for Service Oriented Systems – More message patterns

This blogpost is part of a larger blog post series. Get the overview of the content here.

Slide61

I briefly mentioned that the message has a body. The body carries on the payload or the actual business data identified by the message. Furthermore a message can contain metadata on its header. This allows the message to carry on additional information which can be consumed by the receiver side. Message forwarders need to make sure that the headers remain intact during the communication process. This means a forward should only append additional information to the metatadata or body but never remove information. Leveraging the metadata which can build up more message patterns. Continue reading

Composite UI for Service Oriented Systems – Messaging and fault tolerance

 

This blogpost is part of a larger blog post series. Get the overview of the content here.

Slide55

Consider a classical application approach where clients invoke remote procedure calls on the server. Now, what happens to the initiating request when a crash occurs? For example when the IIS App pool recycles or a connection has been refused by the remote host when too many transactions are waiting to time out. The initiating request is lost or if you are lucky somewhere present as cryptic information in a log file. Continue reading