Files
papers/crowdstart-commerce/crowdstart-commerce.tex
zeekay 0d1d121451 papers: cover-consistency + build pass on Hanzo Tier-2/3 catalogue
Fix shared/ include paths to ../shared/ for 55 subdirectory papers so
that hanzocover.sty and lstlang.tex resolve when building from each
paper's own directory (the build pattern used by latexmk per paper).

Build fixes:
- hanzo-operative/sections/03-screen-understanding-pipeline.tex: move
  \COMMENT from after \FOR{...} onto the \STATE line so the algorithmic
  env doesn't mis-parse.
- hanzo-network-architecture (abstract + sections 04, 12, 13): escape
  unicode mu (U+03BC) as $\mu$ for pdflatex.
- ntt-transform/sections/08-benchmark-results.tex: same mu escape.

All 55 Tier-2/3 papers now build clean with latexmk -pdf.
2026-05-13 01:11:04 -07:00

51 lines
1.7 KiB
TeX

\documentclass[11pt,twocolumn]{article}
\usepackage{../shared/hanzocover}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb}
\usepackage{graphicx}
\usepackage{hyperref}
\usepackage{cite}
\usepackage{algorithm}
\usepackage{algorithmic}
\usepackage{listings}
\input{../shared/lstlang}
\usepackage{xcolor}
\lstset{
basicstyle=\ttfamily\small,
keywordstyle=\color{blue},
commentstyle=\color{gray},
stringstyle=\color{red},
breaklines=true,
frame=single
}
\title{Crowdstart: A Cloud-Native E-Commerce Platform}
\author{Zach Kelling\\
Hanzo Industries\\
\texttt{[email protected]}}
\date{March 2014}
\begin{document}
\hanzocoverpage
\begin{abstract}
We present Crowdstart, a cloud-native e-commerce platform designed from first principles for horizontal scalability and operational simplicity. Built on Google App Engine with Go as the primary implementation language, Crowdstart demonstrates that commerce infrastructure can achieve both developer ergonomics and production reliability without the operational burden of traditional deployments. Our architecture leverages eventual consistency, idempotent operations, and stateless request handling to enable automatic scaling from zero to millions of transactions. We describe the system design, evaluate performance characteristics, and discuss lessons learned from production deployments serving over 500 merchants.
\end{abstract}
\input{sections/01-introduction}
\input{sections/02-background-and-motivation}
\input{sections/03-system-design}
\input{sections/04-implementation}
\input{sections/05-evaluation}
\input{sections/06-lessons-learned}
\input{sections/07-related-work}
\input{sections/99-conclusion}
\end{document}