Tyk
reference-architecture
Our great sponsors
Tyk | reference-architecture | |
---|---|---|
6 | 11 | |
9,172 | 1,638 | |
1.2% | 1.0% | |
9.6 | 9.2 | |
6 days ago | 3 months ago | |
Go | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Tyk
-
5 Ways to Improve Your API Reliability
Tyk: An open-source API Gateway that is fast and scalable, running on either its own standalone server or alongside your existing nginx installation.
-
I want to contribute to open source but don't know where to start
We're a friendly bunch at https://github.com/TykTechnologies/tyk - I'll gladly pick up onboarding contributors for some meaningful tasks, if you'd like to ease into it. Lots of tech debt to address, so it's more maintenance work, testing, introducing DDD, etc.
- Open source webhook service
-
Microservices Design - API Gateway Pattern
Amazon API Gateway AWS provides fully managed service for creating, publishing, maintaining, monitoring, and securing REST, HTTP, and WebSocket where developers can create APIs that access AWS or other web services, as well as data stored in the AWS Cloud. Kong API Gateway Kong Gateway is an open-source, lightweight API gateway optimized for microservices, delivering unparalleled latency performance and scalability. If you just want the basics, this option will work for you. It is scalable easily horizontally by adding more nodes. It supports large and variable workloads with very low latency. Other API Gateways Apigee API Gateway MuleSoft Tyk.io Akana SwaggerHub Azure API Gateway Express API Gateway Karken D Choosing the right API gateway Some of the common baseline for evaluation criteria include simplicity, open-source vs propriety, scalability & flexibility, security, features, community, administrative (support, monitoring & deployment), environment provisioning(installation, configuration, hosting offering), pricing, and documentation. API Composition / Aggregation Some API requests in API Gateway map directly to single service API which can be served by routing request to the corresponding microservice. However, in the case of complex API operations that requires results from several microservices can be served by API composition/aggregation (a scatter-gather mechanism). In case of dependency of one another service where synchronous communication is required, the chained composition pattern has to be followed. The composition layer has to support a significant portion of ESB/integration capabilities such as transformations, orchestration, resiliency, and stability patterns. A root container is deployed with the special distributor and aggregator functionalities (or microservices). The distributor is responsible for breaking down into granular tasks and distributing those tasks to microservice instances. The aggregator is responsible for aggregating the results derived by business workflow from composed microservice. API Gateway and Aggregation API gateway with added features results in overambitious gateways that encourage designs that continue to be difficult to test and deploy. It is highly recommended to avoid aggregation and data transformation in the API Gateway. Domain smarts are better suited to be done in application code that follows the defined software development practices. Netflix API Gateway, Zuul 2 removed a lot of the business logic from Gateway that they had in Zuul to origin systems. For more details, refer here. Service Mesh and API Gateway Service mesh in microservices is a configurable network infrastructure layer that handles interprocess communication. This is akin to what is often termed as sidecar proxy or sidecar gateway. It provides a lot of functionalities such as:
reference-architecture
-
Slack’s Migration to a Cellular Architecture
Delighted to be part of this conversation on cell-based architecture. As the author of the cell-based reference architecture https://github.com/wso2/reference-architecture/blob/master/r..., I'm here to share insights on this exciting approach.
Cell-based architecture introduces modular 'cells' into software systems, each with distinct APIs. This design fosters loose coupling and scalability – key for today's dynamic software landscape. Particularly, for those intrigued by microservices, cells align seamlessly with the independent, scalable components that power microservices architectures.
Curious to dive deeper? If you're keen to explore the nitty-gritty technicalities, I invite you to check out the architecture paper https://github.com/wso2/reference-architecture/blob/master/r... for an in-depth understanding. Let's kick-start this dialogue on the potential of cell-based architecture and its impact on modern software design. Feel free to join the conversation!
No, it is not written by AI :). You can look at the Reference Implementations section of the spec to find who is using the spec https://github.com/wso2/reference-architecture/blob/master/r...
-
Cell-Based Architecture
A collection of cells called a virtual application https://github.com/wso2/reference-architecture/blob/master/r...
-
Microservices Design - API Gateway Pattern
References: https://microservices.io/index.html https://docs.microsoft.com/en-us/azure/architecture/ https://github.com/wso2/reference-architecture/blob/master/api-driven-microservice-architecture.md https://tsh.io/blog/design-patterns-in-microservices-api-gateway-bff-and-more/ https://www.infoq.com/articles/service-mesh-ultimate-guide/ https://samnewman.io/patterns/architectural/bff/ https://netflixtechblog.com/
What are some alternatives?
KrakenD - Ultra performant API Gateway with middlewares. A project hosted at The Linux Foundation
Kong - 🦍 The Cloud-Native API Gateway and AI Gateway.
Postwoman - 👽 Open source API development ecosystem - https://hoppscotch.io
Pizzly - The simplest, fastest way to integrate your app with an OAuth API
API Platform - Create REST and GraphQL APIs, scaffold Jamstack webapps, stream changes in real-time.
apisix-docker - the docker for Apache APISIX
DreamFactory - DreamFactory API Management Platform
Vue Storefront - Alokai is a Frontend as a Service solution that simplifies composable commerce. It connects all the technologies needed to build and deploy fast & scalable ecommerce frontends. It guides merchants to deliver exceptional customer experiences quickly and easily.
Hapttic - :fast_forward: Hapttic is a simple HTTP server that forwards all requests to a shell script.
Endpoint
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
apisix - The Cloud-Native API Gateway