PAR 2012

Cours PAR (Distributed Software Engineering)

The goal of this course is to be an introduction to the problems, the foundation, the technologies and the engineering of distributed software

References

Distributed Systems by George Coulouris, Jean Dollimore, Tim Kindberg and Gordon Blair Fifth Edition, published by Addison Wesley, May 2011
Software Engineering 9 by Ian Sommerville

Readings from the series Back to Basics from Werner Voegel (Amazon CTO)

On the Naming and Binding of Network Destinations J. Saltzer - Request for Comments: 1498
The Emperor’s Old Clothes By C.A.R. Hoare Communications of the ACM, 1981

I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies.

Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency Cary G. Gray and David R. Cheriton, Proceedings of the Twelfth ACM Symposium on Operating Systems Priciples (SOSP), December 1989, Litchfield Park, AZ, USA.

Some other ressources

A new approach to the three tier architecture for API

Cours (10h)

Cours	Lectures notes	Reférences
Engineering Distributed Applications	Lecture 1 & 2
Distributed Objects and Components	Lecture 3
EJB	Lecture 4
Indirect Communication	Lecture 5
Data Management	Lecture 6
Service Oriented Architecture	Lecture 7
The Cloud	Lecture 8

Very Good Discussion between Jeff Bezos Wener Vogels. A must see

Cloud Computing by Armando Fox at UC Berkeley

Above the Clouds: A Berkeley View of Cloud Computing A Berkeley View of Cloud Computing
Street view in a Google Data Center

<strong> High Performance Web Applications </strong> from <strong>Amazon Web Services</strong>

TP

Consigne pour les TPs

Pour l'ensemble des séances de TP, vous allez créer un projet sur la forge ESIAL comme sous projet de TP PAR 2012. Le nom de votre projet, sera votre identifiant (login) ESIAL précédé du préfix par2012-. Pensez à ajouter les intervenants du module (F. Charoy et G. Oster) comme membre de votre projet. Il vous est demandé de committer vos résultats (au minimum) à la fin de chaque séance de TP (pensez à mettre des messages de commit significatifs). Cela nous servira pour suivre l'évolution de votre travail.

TP RMI (4h)

TP EJB (4h)

TP persistence (2h)

TP Persistence n° 1

TP noté (2h)

Resources

Distributed Systems Courses (Google) Distributed Systems : Concept and Design - 5th Edition