vendredi 1 mai 2009

Veille technologique semaine 18

En cette veille de week-end prolongé, je vous propose les sujets suivants :
  • quelles sont les conséquences du rachat de SUN par ORACLE ?
  • un article qui propose la réunion des architectures orientées services (SOA) et des architectures orientées événements (EDA). Cette réunion permet de décrire complètement l'architecture logique de nos systèmes d'une manière complètement indépendante du socle technique : l'industrie parle de séparation des préoccupations et propose le terme de middlware agnostique. Il est donc essentiel de capitaliser cette architecture logique de nos systèmes, au niveau de la phase d'analyse et non du design. BEA, ORACLE et IBM propose le terme de EDSOA pour réunir ces deux styles d'architectures, qui ne sont pas liées aux solutions technologiques (le middleware, ou socle technique par exemple).
  • La deuxième partie de l'interview de quelques guru dans le domaine du logiciel.
  • Un article technique sur les "extension méthodes" en C# 3.0.
  • Un résumé le l'évolution de l'asynchronisme dans les architecture Web.
  • La sortie de la version 1.0.12 de JFreeChart avec encore plus de graphique : il faut aller vous la démo.
  • Le top 10 des fonctionnalité les moins utilisé du JDK : on peut noter que CORBA est un candidat à sortir du JDK depuis plusieurs années.
  • La préparation de l'update 14 du JDK 6 propose des évolutions importante.
Bonne lecture

What will Oracle's Planned Acquisition of Sun Mean for Java
Whilst Sun Microsystems and Oracle are hailing Oracle's purchase of Sun as a huge boost for Java many in the community are not so sure, wondering what kind of control Oracle will seek to exert over the platform.

How EDA extends SOA and why it is important
Many people think of SOA as synchronous RPC (mostly over Web services). Others say EDA is SOA. And there are people who say that the best of EDA and SOA is combined in SOA 2.0. But an architectural distinction can be made between a request-and-reply pattern and a publish-and-subscribe pattern. Both patterns are an inverse of each other. Because of the completely different nature and use of the two patterns, it is necessary to be able to distinguish between the both and to name them. You might say making such a distinction is a universal architectural principle. Combining both of the patterns into an increment of the version number of one of them is not a very clever act. It is appropriate and desirable to use the acronyms SOA and EDA to make this distinction, because SOA and EDA are both positioned in the same architectural domain; SOA focusing on (the decomposition of) business functions and EDA focusing on business events. This article explains the differences between the two patterns, when to use the one or the other and how to combine them.

The Developer Insight Series, Part 2: Code Talk
Over the years, I've heard noted developers talk about their favorite code, funniest code, most beautiful code, how to write code, how not to write code, the obstacles to writing good code, what they love and hate about writing code, and so on. In Part One of the Developer Insight Series, three Java Champions responded favorably to Brian Goetz's advice to write "dumb" code.
In Part Two, we hear code advice from five distinguished developers: Joshua Bloch and Masood Mortazavi echo Goetz's advice to keep code simple. Jaron Lanier and Victoria Livschitz want to radically change the way code is created. And renowned bug fixer Brian Harry provides tips on bug fixing while emphasizing what the process can teach us.

Skinning with Extension Methods
One of the new language features introduced with C# 3.0 and Visual Basic.Net 9.0 is Extension Methods. Extension methods enable new behaviors to be invoked on otherwise closed types. One application of extension methods that will be discussed here is their use in class library development for enabling multiple styles of interfaces for components. This might be thought of as "skinning" an API.

What is the Asynchronous Web ?
Legacy web applications are synchronous in nature. The user interacts with the web interface presented in the browser, the browser makes requests back to the server based on that user interaction, and the server responds to those requests with new presentation for the user - fundamentally a synchronous process. This means that the presentation delivered to the user represents a snapshot in time of what is a dynamic system.

JFreeChart 1.0.12 :

The Top 10 Unused Features in Java
This API would probably win the vote among developers on "which API do you want to remove from Java?".

JDK 6u14 almost ready at b05; Making Java load faster and lighter

Aucun commentaire: