From Loose Coupling to Event Driven Architecture and Lean SOA

Loose coupling is one of the key factors of the success of the Service Oriented Architecture. It allows easy distribution and replacement of components across wide spread networks. The real value of Loose Coupling unfolds when it is used in an Event Driven Architecture (EDA). EDA is the basis of any modern operating system and the key factor of the internet. This presentation gives you a kick-start in orchestrating loosely coupled services via events. Thinking in events is different from classical procedural programming. This session will make you acquainted with the different thinking structures of EDA and the possibilities that lie in them. It explains why loose coupling in combination with EDA will lead into a much leaner overall service-based infrastructure and a lean SOA.

Java Persistence 2009: What’s New: What’s Still The Same

In the last five years, object-relational mapping has gone mainstream, with products like OpenJPA, TopLink and its descendants, and Hibernate fighting for market share and developer mindshare.

Specifications for persistence continue to evolve (convergence), persistence products continue to add features (divergence), and developers continue to search for the best tradeoffs between standardization and getting their own projects out on time.

Have the defining issues been resolved? Impedance mismatch between object models and database storage; independence of web frameworks from storage abstractions; and relational versus object databases continue to frustrate and amuse developers.

This talk will offer a view of the current state of Java Persistence and where we are likely to go near term.

Rails and the Real World

Since it’s creation Ruby on Rails has emerged as the most influential web application development framework. In it’s infancy it was very opinionated and even arrogant in it’s marketing but has matured to be very inclusive and widely copied. Almost every other language has taken great ideas from Ruby on Rails to bring more rapid development and ease to their developer communities. The Ruby language was designed to optimize programmer happiness. The Rails framework became the “Killer Application” for the Ruby language by continuing this optimization. Rails is used by organizations of all sizes and continues to revolutionize by bring a new and different perspective to web development.

Graduating from ‘Application Programming’ to ‘Framework Architectures’

Almost all conventional courses in programming begin by teaching you “Hello World” and then other incrementally complex applications. ‘Application’ being a software which performs a specific pre-decided task. Thus we become intuitively trained to think applications when we think software. It is usually only after few years of practical experience that one starts to understand how to write extensible and pluggable frameworks and platforms…i:e software which not only perform some core specific tasks, but also provide the foundation for other software’s to build on top of.

The talk is intended to take a very simple example to motivate the idea of framework architectures, and how one could easily conceive and build frameworks without much effort. The latter part extrapolates the above concepts to explain the eclipse architecture, and also explains how the eclipse framework actually is intuitively a “framework of frameworks”.