Higress is a cloud‑native API gateway built on Istio and Envoy that adds AI capabilities, supports Go/Rust/JS Wasm plugins, and offers a web console; the article explains its architecture, core components, deployment via Helm, plugin development, and how developers can contribute to the open‑source project.
This article presents a comprehensive microservice architecture roadmap, explaining why microservices are chosen over monoliths, outlining essential concerns such as Docker, orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, tracing, data persistence, caching, and cloud providers, and recommending suitable tools for each.
This article explains why microservice architecture is preferred over monolithic applications, outlines a learning roadmap, and details essential concerns such as Docker, container orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, distributed tracing, data persistence, caching, and cloud providers, with recommended tools for each.
This article presents a comprehensive roadmap for adopting microservice architecture, explaining its benefits, core concepts, and the essential tools such as Docker, container orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, distributed tracing, data persistence, caching, and cloud providers.
This article explains why microservice architecture is preferred over monolithic applications, outlines a detailed learning roadmap covering core concerns such as Docker, container orchestration, API gateways, load balancing, service discovery, event buses, logging, monitoring, tracing, persistence, caching, and cloud providers, and recommends suitable tools for each component.
This article describes the motivation, architecture, technology choices, and operational practices of building a lightweight Node.js middleware layer that acts as an API gateway for a data platform, covering its positioning, NestJS selection, Kubernetes deployment, health probes, and logging strategies.
Discover the most popular Java open‑source repositories on GitHub for May, including high‑performance API gateways, design‑pattern libraries, cloud‑native messaging platforms, multi‑language algorithm collections, data‑integration tools, and blockchain implementations, each with star counts and brief overviews.
This article provides a comprehensive overview of microservice architecture, covering its definition, history, comparison with monolithic and SOA approaches, core characteristics, practical implementation steps, common design patterns, advantages, challenges, and the mindset shift required for successful adoption.
This article provides a comprehensive overview of microservices architecture, contrasting it with monolithic designs, explaining its core principles, advantages, challenges, communication patterns, governance, containerization, DevOps impact, and real‑world case studies, while also offering practical guidance for adoption.
This article provides a comprehensive overview of microservice architecture, covering its definition, historical development, differences from monolithic systems, design patterns, implementation challenges, advantages, disadvantages, and the mindset shift required for successful adoption.
This article outlines the critical backend components required for building robust Java services, covering API gateways, MVC/IOC/ORM frameworks, caching, databases, search engines, message queues, file storage, unified authentication, configuration, service governance, scheduling, logging, data pipelines, and monitoring strategies.
The article reviews common microservice deployment options, cross‑cutting concerns such as configuration, logging and health checks, explains API gateways, service discovery, circuit breakers, discusses data‑ownership strategies, and lists typical anti‑patterns to avoid when building cloud‑native backend systems.
This article explains the fundamentals of microservices architecture, contrasting it with monolithic systems, and covers design principles, messaging patterns, integration methods, API‑gateway usage, and data decentralization to help developers build scalable, maintainable backend services.
This article outlines the essential backend infrastructure components and best‑practice patterns—such as API gateways, service frameworks, caching, databases, search engines, message queues, authentication, configuration, service governance, scheduling, logging, and monitoring—required to build stable, scalable, and maintainable internet applications.
