papers/crowdstart-commerce/sections/06-lessons-learned.tex

\section{Lessons Learned}


\subsection{Embrace Constraints}

App Engine's constraints initially seemed limiting: no local filesystem, no long-running processes, no persistent connections. These constraints forced architectural decisions that improved the system:
\begin{itemize}
\item Statelessness enabled effortless scaling.
\item Task queues provided durability for critical operations.
\item Managed services eliminated operational burden.
\end{itemize}

\subsection{Eventual Consistency Requires Careful Design}

Eventual consistency introduces complexity in user-facing flows. Users expect immediate feedback when adding items to cart. We addressed this through:
\begin{itemize}
\item Optimistic UI updates with background synchronization.
\item Read-your-writes consistency for authenticated users.
\item Clear communication of processing status.
\end{itemize}

\subsection{Monitoring is Non-Negotiable}

Distributed systems fail in distributed ways. We instrumented every service boundary:
\begin{itemize}
\item Request tracing with correlation IDs.
\item Structured logging with JSON output.
\item Custom metrics for business events.
\end{itemize}