awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
serverless avatar

serverless/event-gatewayArchived

0
View on GitHub↗
1,647 stars·97 forks·Go·Apache-2.0·18 viewswww.serverless.com/event-gateway↗

Event Gateway

The Event Gateway is a unified routing layer designed to connect HTTP requests and cloud events to serverless functions across multiple providers and infrastructure environments. It functions as a centralized platform for managing event-driven architectures, enabling developers to register, map, and trigger remote functions in response to incoming web traffic or asynchronous system events.

The platform distinguishes itself through a plugin-based middleware pipeline that allows for custom logic execution during the request lifecycle, enabling developers to intercept, validate, or transform events before final delivery. It supports schema-based routing to ensure data consistency and utilizes resource-isolated namespaces to organize functions and subscriptions into logical sandboxes, preventing naming collisions across organizational boundaries.

The system provides a comprehensive suite of capabilities for API management, including request authorization, cross-origin resource sharing, and parameter extraction. It facilitates high-throughput traffic management through horizontal scaling of stateless instances, while maintaining routing state across service restarts via an external key-value store. Observability is built into the core, with support for exporting operational metrics and system lifecycle events to external monitoring tools.

Developers can manage the gateway using a command-line interface that supports local development and testing. Standardized configuration templates are available to automate deployment and management within containerized and cloud environments.

Features

  • Serverless API Gateways - Exposes serverless logic as standard web endpoints while handling request validation, authorization, and cross-origin resource sharing policies.
  • Remote Function Invocation - Connects external compute resources and remote HTTP endpoints to a unified interface for seamless function invocation.
  • Synchronous Request-Response - Maps incoming HTTP requests directly to backend function invocations and returns the resulting output to the original caller.
  • Cloud Function Orchestrators - Functions as a centralized orchestrator for registering, mapping, and triggering remote functions in response to web traffic or system events.
  • Serverless Function Invokers - Executes registered functions by triggering them via standard HTTP requests to specific paths.
  • Serverless Function Management - Directs incoming HTTP requests and cloud events to specific serverless functions across multiple providers and regions.
  • HTTP Request Routing - Dispatches incoming HTTP requests and cloud events to backend destinations including serverless functions and message queues.
  • Pub-Sub Messaging - Decouples event producers from consumers by broadcasting messages to multiple subscribers without requiring direct service-to-service connections.
  • Event-Driven Architectures - Connects disparate services and cloud functions through a unified gateway to enable reactive, decoupled communication patterns.
  • Event Subscriptions - Routes incoming HTTP requests and cloud events to specific functions by matching them against defined path and subscription patterns.
  • Composable Middleware Pipelines - Executes custom logic hooks during the request lifecycle to intercept, validate, or transform events before final delivery.
  • Event Schema Validators - Validates incoming event payloads against registered structural schemas to ensure data consistency across distributed services.
  • Persistent Configuration Stores - Stores routing rules and event subscriptions in an external key-value database to ensure system state remains intact across service restarts.
  • Distributed Key-Value Stores - Synchronizes routing rules and subscription state across multiple gateway instances using an external persistent data store.
  • Container Instance Scaling - Deploys stateless gateway instances within a cluster environment to distribute traffic load and increase total system throughput.
  • Plugin Systems - Supports registering custom plugins to execute logic in response to internal system events, allowing developers to block or process event flows.
  • Cloud Event Orchestration - Ingests data streams from external message queues and cloud providers to react to activities originating from various external services.
  • Cloud Infrastructure Deployment - Provides standardized configuration templates to automate deployment and management of services within container orchestration clusters and managed cloud environments.
  • Cloud Service Integrations - Links external compute resources, message queues, and cloud services into a single interface for consistent event processing.
  • Resource Isolation - Groups functions and subscriptions into logical sandboxes to prevent naming collisions and organize resources across different teams or environments.
  • Traffic Distribution - Supports horizontal scaling by distributing incoming traffic across multiple instances in a shared configuration cluster.
  • Cross-Origin Resource Sharing (CORS) Policies - Manages security policies for API endpoints to control cross-origin browser interactions.
  • Custom Authorization Logic - Validates incoming requests against security policies and custom authorizer functions to ensure permitted access.
  • CloudEvent Routing Meshes - Parses and routes events formatted according to standard specifications or raw HTTP requests to trigger appropriate downstream functions.
  • Namespace Isolation Policies - Groups functions and subscriptions into logical sandboxes to prevent naming collisions and enforce organizational boundaries across deployments.
  • Value-Based Event Routing - Matches incoming event payloads against registered structural definitions to determine the appropriate downstream function or service destination.
  • Distributed Observability Systems - Monitors performance metrics and event traffic across a cluster of gateway instances to ensure system health and reliability.
  • Performance Visualization - Provides pre-configured dashboard templates to visualize aggregated performance metrics and request traffic.
  • Observability Metrics Exporters - Exports system performance data and event processing statistics in standardized formats for external monitoring tools.
  • Distributed Event Emission - Dispatches custom event payloads to trigger associated functions asynchronously, enabling decoupled communication between services without shared state.
  • Route Parameter Extraction - Captures dynamic segments from URL paths and passes them as variables to backend functions.

Star history

Star history chart for serverless/event-gatewayStar history chart for serverless/event-gateway

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Frequently asked questions

What does serverless/event-gateway do?

The Event Gateway is a unified routing layer designed to connect HTTP requests and cloud events to serverless functions across multiple providers and infrastructure environments. It functions as a centralized platform for managing event-driven architectures, enabling developers to register, map, and trigger remote functions in response to incoming web traffic or asynchronous system events.

What are the main features of serverless/event-gateway?

The main features of serverless/event-gateway are: Serverless API Gateways, Remote Function Invocation, Synchronous Request-Response, Cloud Function Orchestrators, Serverless Function Invokers, Serverless Function Management, HTTP Request Routing, Pub-Sub Messaging.

Which projects share features with serverless/event-gateway?

Projects with overlapping indexed features include: inngest/inngest — Inngest is a durable execution framework and event-driven automation engine designed to orchestrate background… doocs/advanced-java — This project is a comprehensive Java backend engineering guide and technical reference focused on high-concurrency… quarkusio/quarkus — Quarkus is a Kubernetes-native Java framework designed for building high-performance, memory-efficient applications.… nats-io/nats-server — NATS Server is a high-performance, lightweight messaging system designed for cloud-native applications, edge… threedotslabs/watermill — Watermill is a Go library for building event-driven applications. It provides a framework for implementing… knative/serving — Kubernetes-based, scale-to-zero, request-driven compute.

Curated searches featuring Event Gateway

Hand-picked collections where Event Gateway appears.
  • Serverless Function Deployment Frameworks
  • Function calling interface

Projects sharing features with Event Gateway

These projects share indexed features with Event Gateway. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • inngest/inngestinngest avatar

    inngest/inngest

    5,499View on GitHub↗

    Inngest is a durable execution framework and event-driven automation engine designed to orchestrate background workflows. It enables developers to build resilient, stateful processes by memoizing function steps, ensuring that long-running tasks can automatically resume from the last successful operation after failures, timeouts, or infrastructure restarts. The platform distinguishes itself through its event-driven architecture, which uses a schema-validated bus to trigger functions and coordinate complex, multi-step logic. It employs an onion-model middleware approach for cross-cutting concer

    Go
    View on GitHub↗5,499
  • doocs/advanced-javadoocs avatar

    doocs/advanced-java

    78,987View on GitHub↗

    This project is a comprehensive Java backend engineering guide and technical reference focused on high-concurrency design, distributed systems, and microservices architecture. It provides detailed strategies for decomposing monolithic applications, managing service discovery, and implementing the architectural patterns required for scalable backend environments. The repository distinguishes itself through an extensive collection of big data algorithmic references and database scaling strategies. It covers memory-efficient techniques for analyzing massive datasets, such as Top-K element extrac

    Javaadvanced-javadistributed-search-enginedistributed-systems
    View on GitHub↗78,987
  • quarkusio/quarkusquarkusio avatar

    quarkusio/quarkus

    15,479View on GitHub↗

    Quarkus is a Kubernetes-native Java framework designed for building high-performance, memory-efficient applications. It utilizes ahead-of-time native compilation to transform Java code into standalone, optimized binaries that eliminate the need for a virtual machine, enabling rapid startup and reduced memory consumption. By performing code augmentation during the build phase, it shifts heavy processing tasks away from runtime, ensuring that applications are optimized for cloud-native environments. The framework distinguishes itself through a unified approach to reactive and imperative program

    Javacloud-nativehacktoberfestjava
    View on GitHub↗15,479
  • nats-io/nats-servernats-io avatar

    nats-io/nats-server

    20,076View on GitHub↗

    NATS Server is a high-performance, lightweight messaging system designed for cloud-native applications, edge computing, and distributed microservices. It functions as a distributed publish-subscribe broker that routes messages using hierarchical, dot-separated subject strings, enabling decoupled communication between services without requiring centralized broker lookups. The system supports core messaging patterns including asynchronous publish-subscribe, request-reply, and load-balanced queue processing. The platform distinguishes itself through a decentralized architecture that eliminates t

    Gocloudcloud-computingcloud-native
    View on GitHub↗20,076
Compare all 30 related projects→