some work on first paper

source/db2-presentation.tex

@@ -52,6 +52,16 @@ Usually \textbf{concurrency control} protocols are necessary because we want to
 Mixing this with a distributed scenario means the necessity to introduce complex algorithms (such as 2PC) that coordinate the various entities involved in the transactions, introducing latency. Coordination also means that we cannot exploit all the parallel resources of a distributed environment, because we have a huge overhead introduced by the coordination phase.
 \end{frame}
 
+\begin{frame}
+\frametitle{The Starting Problem}
+Usually we pay coordination overhead in term of:
+\begin{itemize}
+  \item Increased latency \pause
+  \item Decreased throughput \pause
+  \item Unavailability (in case of failures)
+\end{itemize}
+\end{frame}
+
 \begin{frame}
 \frametitle{Invariant Confluence}
 The authors of the paper discuss this new technique (or better analysis framework) that if applied, it will reduce in a considerable way the need of coordination between the Database entities, reducing the cost in terms of bandwidth and latency, increasing considerably the overall throughput of the system.
@@ -59,12 +69,19 @@ The authors of the paper discuss this new technique (or better analysis framewor
 
 \begin{frame}
 \frametitle{Invariant Confluence}
-The main idea here is not to introduce some new exotic way to improve the coordination task, but instead the authors predicate on the fact that there is a set of workloads that do not require coordination, and that can be executed in parallel. The programmer at the application level can then state in an explicit way the \emph{invariants}, special attributes of the tables that need coordinate in the case of concurrent operations executing on them. 
+The main idea here is not to introduce some new exotic way to improve the coordination task, but instead the authors predicate on the fact that there is a set of workloads that do not require coordination, and that can be executed in parallel. The programmer at the application level can then state in an explicit way the \emph{invariants}, special attributes of the tables that need coordinate in the case of concurrent operations executing on them.
 \end{frame}
 
 \begin{frame}
-\frametitle{Template}
-Template text
+\frametitle{The Model}
+The main concepts introduced:
+\begin{itemize}
+  \item Invariants
+  \item Transactions
+  \item Replicas
+  \item (\emph{I-})Convergence
+  \item Merging
+\end{itemize}
 \end{frame}
 
 \begin{frame}