I’m currently travelling around in Germany and giving a whole day workshop about Composite UI for Service Oriented Systems. Part of that tour in Germany are also several Usergroup presentations each day in another city. So far I have visited Berlin, Leipzig and Dresden. The next station today is Braunschweig. After Braunschweig I will return back to Switzerland. I can only say it has been a blast so far! This blogpost is the overview and content linking blog post for a series of blogposts. I decided to divide the content of the Workshop into several blogpost because having all in one would be a massive one which nobody will have the motivation to read. In this handout I do not include the exercises we did during the Workshop. If you want the exercises too, then contact me and I’m more than happy to host the workshop at your event or in your company!
After this workshop you’ll be able to argument why it is important to decompose large systems and how the decomposition can be achieved. Furthermore this workshop will provide you with the necessary practices to reassemble the system together into a whole user experience by applying service composition techniques.
Let’s get started!
Blog post overview (will be updated after each blogpost has been published, you can also use the tag “CompositeUI” on the blog)
- Systems and Applications
- Fallacies of Distributed Systems Part I
- Fallacies of Distributed Systems Part II
- Fallacies of Distributed Systems Part III
- Monolithic and Big Ball of Mud Systems
- Coupling
- Messaging Introduction
- Messaging vs RPC
- Messaging and Fault tolerance
- More message patterns
- Ordering and buy-in
- Services are not webservices
- Data outside vs Data inside
- Immutable and stable
- Mashup means bringing it together
- Composition patterns
- Challenges Part I
- Challenges Part II
Disclaimer: The icons used in this presentation are stock icons. I bought a standard license for the following icons:
http://de.depositphotos.com/5170425/stock-illustration-400-top-signs.html
If you reuse my slides you might need to buy a license too.
http://depositphotos.com/license.html
You can also find a copy of the slides on my slideshare account.
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] I want to build that crazy sample from the ground up. So let’s do it! In my blogposts about CompositeUI for Service Oriented Systems I called about services or “things”. I don’t cover that theory here. I encourage […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] This blogpost is part of a larger blog post series. Get the overview of the content here. […]
[…] how to subscribe to messages and how to deploy components to endpoints. In my blogposts about CompositeUI for Service Oriented Systems I called about services or “things”. I don’t cover that theory here. I encourage […]