There are some services as part of the infrastructure to support microservices Read More »

When you make architecture decisions on how to communicate between service to service, chances are you want to use the event-driven approach instead of the request/response approach. It gives you flexibility, reliability, and scalability. To leverage the full potential of Light, you should use different frameworks for different services. Some of the services serve the application API calls from SPA and mobile applications, then these services will be built on top of light-rest-4j, light-graphql-4j or light-hybrid-4j to serve clients synchronously. Read More »

Light follows a security-first design. Given the complexity of microservices architecture, there is no existing OAuth 2.0 provider on the market that is suitable for microservices. Most commercial products focus on the perimeter and don’t have solutions for service to service communication inside the corporate network. This is the reason we have provided an OAuth 2.0 provider light-oauth2, which is based on light-4j and light-rest-4j frameworks. The light-oauth2 consists of 7 microservices that can be deployed in one cluster with multiple instances of token and code services and one instance of other services. Read More »