Light-4j is the main component in Light. It contains a client, a server and all common HTTP cross-cutting concerns implemented in the request/response chain as middleware handlers. An embedded gateway is established in the same server process by injecting these middleware handlers between the client and server in the HTTP channel via configuration in the DevOps process to gain higher performance and a lower memory footprint. This allows developers to focus only on business logic to achieve higher productivity. Read More »

Beside Restful API, the platform supports other styles of API Read More »

Light provides a plugin architecture and dozens of middleware handlers to address cross-cutting concerns in general. When you decide to build an API or service, you have to choose from different styles and the corresponding frameworks. Chances are you are building a public Web API and want to follow RESTful style to make sure everyone can understand and consume it. The light-rest-4j is a framework that is designed to speed up RESTful API development and deployment. Read More »

Recently, one big customer asked if we can integrate light-4j middleware handlers to address cross-cutting concerns to Spring Boot applications. They want to leverage the light-4j middleware handlers as they are faster, smaller and easier to implement and customize. Most importantly, these handlers are working with Light infrastructure to form an ecosystem to support microservices architecture. In this way, they can migrate their existing Spring Boot applications to Light without changing the controllers and business logic. Read More »

GraphQL is a new style of protocol open-sourced by Facebook, and it is getting popular, especially in Mobile and Single Page Application as the front end. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools. Light-graphql-4j is a framework that is designed to work with GraphQL. Read More »

When building an application based on microservices architecture, there are two major patterns for service to service communication. Serivce to Service communication Synchronous, Request/Response Communication In light-4j, this means to use Client module to call other services in the request/response fashion regardless light-rest-4j, light-graphql-4j or light-hybrid-4j is used. Asynchronous, Message-Based Communication The eventual consistency framework light-eventuate-4j is designed to facilitate asynchronous communication between services built on top of light-rest-4j, light-grahpql-4j and light-hybrid-4j. Read More »