The majority of the sections in this site are about how to build, deploy and manage services. This section will address microservices architecture and the best practices from a consumer perspective.

Unlike monolithic JavaEE web services with only one client and one server, there are many microservices involved in one external request, and client to server communication efficiency is very important to overall latency. The definition of client vs server or consumer vs provider is blurred as one service can be the server for another service. At the same time it can be a client for another service. The following contains architecture, design and best practices. → The following contains architecture, design and best practices:

The following contains architecture, design and best practices.

• Client Module
  • Which Jar Files
  • TLS Connection
  • HTTP 2.0
  • Security
    • Subject Token
    • Access Token
    • Customized Grant Type
    • Get Token in Startup
    • Long Lived Token
    • Key Distribution
    • Secret Encryption
    • SPA Stateful
    • SPA Stateless
    • SPA CSRF Prevention
    • SPA XSS Prevention
    • SPA BFF
  • Traceability
    • Traceability Id
    • Correlation Id
  • Circuit Breaker
  • CompletableFuture
• light-consumer-4j
• Service Discovery
  • Registry
    • Standalone
    • Docker
    • Kubernetes
  • Discovery
    • Consul
    • Zookeeper
  • SPA and Mobile
• Load Balance
  • Round Robin
  • Local First
  • Consistent Hash
• Light Router
  • Use Cases
  • Location and Ownership
• Single Page Application
  • React
  • React-schema-form
  • React-schema-form-rc-select
    • Developer Guide
  • Vue
  • Angular