This is a self-hosted, free image hosting service (Telegraph-Image) built as a serverless application on Cloudflare Pages. It provides image upload, storage (Telegram Bot API or Cloudflare R2), serving with optional moderation (Workers AI or moderatecontent.com), and an admin dashboard (Vue-based) for managing images (list, block, delete, whitelist, edit names, toggle likes). The architecture follows a clean provider pattern for storage and moderation modules, uses middleware chaining via Cloudflare Pages Functions, and includes features like short links (KV-backed), anti-hotlinking, and deployment self-checks. The frontend is hybrid: a dependency-free modern homepage and an older Nuxt.js SPA for the admin panel. The codebase is well-tested with unit and e2e tests, but has technical debt from a legacy Nuxt frontend, deprecated `document.execCommand` usage, and reliance on external CDN resources for admin UI.
This repository, microsoft/WhatTheHack, is a comprehensive collection of hackathon challenge content focused on Microsoft Azure technologies. It contains over 70 individual 'hacks' covering topics such as Kubernetes, AI, DevOps, serverless, infrastructure-as-code, and more. Each hack includes student challenge instructions, coach solutions, and often starter code and infrastructure templates. The repository serves as a reusable library for running hands-on workshops and self-paced learning. While not a single application, it provides a structured framework for creating and delivering technical training events. The code quality varies across challenges, but the overall organization and documentation are strong, with reusable patterns like GitHub Actions workflows and hack authoring templates.
This repository contains a collection of AWS Lambda extension examples and demonstrations across multiple programming languages (Go, Python, Node.js, Java, C#, Rust) and wrapper scripts (Bash, Python, Ruby). Each example illustrates how to build a Lambda extension that integrates deeply with the Lambda execution environment using the Extensions API for lifecycle event registration, and the Logs API/Telemetry API for observability data processing. The extensions perform tasks such as forwarding logs to external destinations (S3, Kinesis, Firehose, Elasticsearch, etc.), collecting and sending telemetry data, implementing custom runtime behavior via wrapper scripts, and caching data from AWS services like DynamoDB and Parameter Store. The repository serves as a practical guide for developers to understand and implement Lambda extensions for observability, security, and governance use cases.
This repository implements a serverless document chat application that allows users to upload PDF documents and ask natural language questions. The backend is composed of AWS Lambda functions orchestrated by Amazon API Gateway, S3, SQS, and DynamoDB. PDF processing uses LangChain with FAISS for vector embeddings and Amazon Bedrock (Claude Sonnet) for LLM inference. The frontend is a React SPA with TypeScript, TailwindCSS, and AWS Amplify authentication. Architecture follows an event-driven serverless pattern: upload triggers S3 event → Lambda extracts PDF metadata, stores in DynamoDB, sends SQS message → another Lambda generates embeddings and stores FAISS index in S3. Chat requests invoke a Lambda that loads the FAISS index, retrieves relevant context, and uses a ConversationalRetrievalChain with DynamoDB-backed memory. The code is clean and follows AWS best practices with Powertools logging, but lacks tests and hardcodes the Bedrock region to us-east-1. It is a solid reference implementation for building a RAG-based Q&A system on AWS.
SST is a full-stack deployment framework and CLI tool for building and deploying serverless applications on AWS and Cloudflare. It uses Pulumi for infrastructure as code, provides a rich set of high-level components (Functions, Buckets, Queues, Databases, Auth, etc.), and supports multiple runtimes (Node.js, Python, Go, Rust) and frontend frameworks (Next.js, Remix, Astro, SvelteKit, SolidStart, etc.). The CLI offers live development mode with hot-reload, a terminal multiplexer, and SSH tunneling for VPC resources. The codebase is a monorepo with a Go CLI, TypeScript platform components, and SDKs in JavaScript, Python, Rust, and Go. While it demonstrates solid engineering patterns like a typed event bus, component transform system, and resource linking, it suffers from some deprecated components, code duplication across framework-specific SSR site components, and a high maintenance surface due to the sheer number of providers and examples.
The Uniswap Routing API is a serverless AWS Lambda service that provides swap quotes across Uniswap V2, V3, V4, and mixed protocols on 20+ EVM chains. It is deployed via AWS CDK with API Gateway, DynamoDB for route/pool caching, S3 for token lists and pool snapshots, and CloudWatch for monitoring. The core quote handler (`lib/handlers/quote/quote.ts`) validates inputs, selects protocols, and delegates to the `@uniswap/smart-order-router` engine. A sophisticated RPC provider layer (`UniJsonRpcProvider`, `SingleJsonRpcProvider`) manages multi-provider failover, health checks, and latency-based selection. Traffic switching experiments (`TrafficSwitcher`) enable gradual rollouts of new implementations with shadow sampling. The system also includes cron-based pool caching, GraphQL-based token fee fetching, and extensive CloudWatch dashboards. While primarily an application, it incorporates data pipeline elements for caching and token list management. The codebase shows signs of deprecation (DECOMMISSION_FAILURE_RATE = 1 in the quote handler) and contains several hardcoded configurations and temporary workarounds, but overall demonstrates solid engineering with reusable abstractions.
This repository is a serverless application that dynamically generates SVG cards (stats, top languages, pinned repos, gist stats, WakaTime stats) for GitHub profile READMEs. It is designed to be deployed on Vercel and uses the GitHub GraphQL API and WakaTime REST API as data sources. The architecture consists of stateless API endpoints that fetch data, apply caching and access control, and render SVG images using a custom Card class and layout system. The codebase is well-structured with extensive unit tests, benchmarks, and a theme system supporting 60+ color themes. However, the project is explicitly deprecated and no longer maintained, with the README pointing to a successor. Despite this, the code demonstrates solid engineering practices, including a reusable retry mechanism with token rotation, an internationalization module, and a flexible SVG layout engine. The main entry points are the API handlers in `api/` and the card renderers in `src/cards/`.
This repository is a large collection of tutorial lessons (numbered 006 to 281) focused on DevOps, cloud infrastructure, and backend development. It contains example applications in multiple languages (Go, Rust, Python, Node.js, Java, etc.) demonstrating common patterns like CRUD APIs, database integration, caching, and monitoring. The infrastructure-as-code examples cover Kubernetes (deployments, RBAC, ingress, service meshes), Terraform (AWS, GCP, Azure), Ansible, Helm, and CI/CD with ArgoCD. A significant portion is dedicated to observability with Prometheus, Grafana, and custom exporters. The repository serves as a companion to video tutorials and is not a single production application but a learning resource. It exhibits high duplication across lessons and some pseudo-code, but contains several reusable components for monitoring, infrastructure provisioning, and performance benchmarking.
This repository provides a Rust runtime for Vercel Serverless Functions, allowing developers to write Vercel Functions in Rust instead of JavaScript/TypeScript. It consists of several components: a TypeScript builder module that interfaces with Vercel's build system to compile Rust code, Rust crates implementing the runtime functionality (vercel_runtime, vercel_runtime_macro, vercel_runtime_router, vercel_axum), and examples showing usage patterns. The system works by compiling Rust functions during deployment and executing them in Vercel's serverless environment using AWS Lambda runtime under the hood. The architecture is modular with separate concerns: the builder handles compilation and packaging, the runtime manages request/response conversion and function execution, and specialized crates handle routing and framework adapters. Key features include route bundling to optimize cold starts by combining multiple routes into a single function, and support for various routing patterns (static, dynamic, catch-all). Importantly, the repository includes a deprecation notice stating that this community runtime is now deprecated in favor of the official Vercel Rust runtime implementation, and users should migrate to the official solution for continued support.
This repository functions as a meta-repository or container for the Fly.io ecosystem rather than a standalone application. Analysis of the source files reveals no executable logic, API endpoints, or data processing pipelines. The .gitmodules file indicates this project serves primarily to manage submodules, specifically flyctl (the CLI) and example projects. The README.md confirms this role, directing users to external repositories for actual functionality. There are no reusable components within this codebase. The absence of source code means there are no patterns, abstractions, or algorithms to extract. Engineers seeking to reuse logic should navigate to the linked flyctl repository. This repo provides no value for code reuse, only for understanding the project structure of the Fly.io monorepo or submodule organization. The repository is maintained, as indicated by recent commit activity, but the content remains static configuration and documentation. It does not suffer from technical drift as it contains no dependencies or code to become outdated. However, its utility is strictly limited to navigation and submodule management.
This repository is a personal portfolio and link aggregation page for Anton Babenko, a well-known figure in the Terraform and AWS DevOps community. It contains no source code, application logic, or data pipelines. The sole content is a README.md file that lists links to the author's social media profiles, media projects (YouTube channel, newsletter), major open-source projects (terraform-aws-modules, pre-commit-terraform, serverless.tf, compliance.tf), utilities, and abandoned projects. It serves as a central directory for discovering the author's work, but it is not a functional software repository. There are no executable files, tests, configuration files, or any code that can be run or reused. The repository is essentially a static documentation page with no technical depth.