LIGHT

  • News
  • Docs
  • Community
  • Reddit
  • GitHub

What is light-4j

light-4j is a platform or ecosystem for building and running cloud native microservices. The design goal is higher throughput, lower latency and smaller memory footprint to lower production costs.

It contains the following:

Cross-cutting concerns

All light-4j frameworks are built on top of an embedded gateway to address cross-cutting concerns for cloud native services within the request/response chain. These plugins or middleware handlers are wired in with IoC service during server startup and can be enabled or disabled or change behaviors via configurations. One of the design goals is to allow developers to only write business logic.

For more info please refer to cross-cutting concerns

Interaction Style

In microservices architecture, services need to interact with each other. There are several frameworks to help build services with certain interaction styles.

Synchronous (Request/Response over HTTP):

light-rest-4j - Building restful API and supporting Swagger 2.0 and OpenAPI 3.0 specification

light-graphql-4j - Generating GraphQL service with IDL

light-hybrid-4j - RPC and Serverless framework that takes advantages of both monolithic and micorservices.

Asynchronous (Event Driven):

light-tram-4j - Transactional messaging to ensure delivery of message, event or command.

light-eventuate-4j - Event sourcing and CQRS framework

light-saga-4j - Distributed transaction orchestration across microservices.

Infrastructure service

To support microservices, the initial infrastructure services must be implemented first. It includes:

light-oauth2 - An OAuth 2.0 provider implemented as microservices.

light-portal - An API management portal and marketplace (Work in progress)

ELK - Centralized logging

InfluxDB and Grafana - Centralized metrics

Consul - Service registry and discovery

Kafka and Zookeeper - Message Broker

Tool Chain

light-codegen - Code generator for all frameworks.

openapi-parser - A light weight and fast OpenAPI 3.0 parser and validator

swagger-bundler - Bundles multiple swagger files together and validate the final result.

light-bot - Devops pipeline for microservices.

  • About Light
    • Overview
    • Testimonials
    • What is Light
    • Features
    • Principles
    • Benefits
    • Roadmap
    • Community
    • Articles
    • Videos
    • License
    • Why Light Platform
  • Getting Started
    • Get Started Overview
    • Environment
    • Light Codegen Tool
    • Light Rest 4j
    • Light Tram 4j
    • Light Graphql 4j
    • Light Hybrid 4j
    • Light Eventuate 4j
    • Light Oauth2
    • Light Portal Service
    • Light Proxy Server
    • Light Router Server
    • Light Config Server
    • Light Saga 4j
    • Light Session 4j
    • Webserver
    • Websocket
    • Spring Boot Servlet
  • Architecture
    • Architecture Overview
    • API Category
    • API Gateway
    • Architecture Patterns
    • CQRS
    • Eco System
    • Event Sourcing
    • Fail Fast vs Fail Slow
    • Integration Patterns
    • JavaEE declining
    • Key Distribution
    • Microservices Architecture
    • Microservices Monitoring
    • Microservices Security
    • Microservices Traceability
    • Modular Monolith
    • Platform Ecosystem
    • Plugin Architecture
    • Scalability and Performance
    • Serverless
    • Service Collaboration
    • Service Mesh
    • SOA
    • Spring is bloated
    • Stages of API Adoption
    • Transaction Management
    • Microservices Cross-cutting Concerns Options
    • Service Mesh Plus
    • Service Discovery
  • Design
    • Design Overview
    • Design First vs Code First
    • Desgin Pattern
    • Service Evolution
    • Consumer Contract and Consumer Driven Contract
    • Handling Partial Failure
    • Idempotency
    • Server Life Cycle
    • Environment Segregation
    • Database
    • Decomposition Patterns
    • Http2
    • Test Driven
    • Multi-Tenancy
    • Why check token expiration
    • WebServices to Microservices
  • Cross-Cutting Concerns
    • Concerns Overview
  • API Styles
    • Light-4j for absolute performance
    • Style Overview
    • Distributed session on IMDG
    • Hybrid Serverless Modularized Monolithic
    • Kafka - Event Sourcing and CQRS
    • REST - Representational state transfer
    • Web Server with Light
    • Websocket with Light
    • Spring Boot Integration
    • Single Page Application
    • GraphQL - A query language for your API
    • Light IBM MQ
    • Light AWS Lambda
    • Chaos Monkey
  • Infrastructure Services
    • Service Overview
    • Light Proxy
    • Light Mesh
    • Light Router
    • Light Portal
    • Messaging Infrastructure
    • Centralized Logging
    • COVID-19
    • Light OAuth2
    • Metrics and Alerts
    • Config Server
    • Tokenization
    • Light Controller
  • Tool Chain
    • Tool Chain Overview
  • Utility Library
  • Service Consumer
    • Service Consumer
  • Development
    • Development Overview
  • Deployment
    • Deployment Overview
    • Frontend Backend
    • Linux Service
    • Windows Service
    • Install Eventuate on Windows
    • Secure API
    • Client vs light-router
    • Memory Limit
    • Deploy to Kubernetes
  • Benchmark
    • Benchmark Overview
  • Tutorial
    • Tutorial Overview
  • Troubleshooting
    • Troubleshoot
  • FAQ
    • FAQ Overview
  • Milestones
  • Contribute
    • Contribute to Light
    • Development
    • Documentation
    • Example
    • Tutorial
“What is light-4j” was last updated: July 5, 2021: fixes #275 checked and corrected grammar/spelling for majority of pages (#276) (b3bbb7b)
Improve this page
  • News
  • Docs
  • Community
  • Reddit
  • GitHub
  • About Light
  • Getting Started
  • Architecture
  • Design
  • Cross-Cutting Concerns
  • API Styles
  • Infrastructure Services
  • Tool Chain
  • Utility Library
  • Service Consumer
  • Development
  • Deployment
  • Benchmark
  • Tutorial
  • Troubleshooting
  • FAQ
  • Milestones
  • Contribute