mirror of
https://github.com/hanzoai/papers.git
synced 2026-10-29 07:34:31 +00:00
zeekay
5a1289e458
Leadership and team cards, board and founding prose, an AI persona modelled on a named individual, contributor and partner entries, and personal correspondence addresses all named one person. The organisation carries them now. Other people keep their names. Where a card, a board list or a founding line named someone else alongside, they stay exactly as they were; only the one entry was removed, and prose that listed two names now reads with one. Sample and fixture data uses the placeholder name these tests already use elsewhere, so the IAM username defect the notes describe still reads as written. The zoo/yapp MIT notice names the foundation that publishes it.
69 lines
2.1 KiB
TeX
69 lines
2.1 KiB
TeX
\documentclass[11pt,a4paper]{article}
|
|
\usepackage{../shared/hanzocover}
|
|
|
|
% Packages
|
|
\usepackage[utf8]{inputenc}
|
|
\usepackage[T1]{fontenc}
|
|
\usepackage{amsmath,amssymb,amsthm}
|
|
\usepackage{graphicx}
|
|
\usepackage{hyperref}
|
|
\usepackage{algorithm}
|
|
\usepackage{algpseudocode}
|
|
\usepackage{booktabs}
|
|
\usepackage{listings}
|
|
\input{../shared/lstlang}
|
|
\usepackage{xcolor}
|
|
\usepackage[numbers]{natbib}
|
|
\usepackage{tikz}
|
|
\usetikzlibrary{arrows,shapes,positioning,calc}
|
|
|
|
% Theorem environments
|
|
\newtheorem{theorem}{Theorem}[section]
|
|
\newtheorem{lemma}[theorem]{Lemma}
|
|
\newtheorem{proposition}[theorem]{Proposition}
|
|
\newtheorem{definition}[theorem]{Definition}
|
|
\newtheorem{corollary}[theorem]{Corollary}
|
|
|
|
% Code listing style
|
|
\lstset{
|
|
basicstyle=\ttfamily\small,
|
|
keywordstyle=\color{blue},
|
|
commentstyle=\color{gray},
|
|
stringstyle=\color{red},
|
|
breaklines=true,
|
|
frame=single,
|
|
numbers=left,
|
|
numberstyle=\tiny\color{gray}
|
|
}
|
|
|
|
\title{\textbf{Hanzo API Gateway:\\Unified Commerce API Architecture}}
|
|
|
|
\author{
|
|
Hanzo AI Research\\
|
|
Hanzo Industries\\
|
|
\texttt{[email protected]}
|
|
}
|
|
|
|
\date{February 2019}
|
|
|
|
\begin{document}
|
|
|
|
\hanzocoverpage
|
|
|
|
\begin{abstract}
|
|
We present the Hanzo API Gateway, a unified commerce API architecture supporting both REST and GraphQL interfaces. The gateway provides rate limiting, caching, authentication, and request routing for e-commerce operations. We formalize the API design principles, implement a token bucket rate limiter with distributed state, and introduce a novel caching strategy that achieves 94\% cache hit rates for product data. The system handles 180,000 requests per second at P99 latency of 23ms. Production deployments serve 1,200+ merchants with 99.99\% availability over 18 months.
|
|
\end{abstract}
|
|
|
|
\input{sections/01-introduction}
|
|
\input{sections/02-api-design-principles}
|
|
\input{sections/03-gateway-architecture}
|
|
\input{sections/04-rate-limiting}
|
|
\input{sections/05-caching-architecture}
|
|
\input{sections/06-error-handling}
|
|
\input{sections/07-implementation}
|
|
\input{sections/08-evaluation}
|
|
\input{sections/09-related-work}
|
|
\input{sections/99-conclusion}
|
|
|
|
\end{document}
|