fixes #102 add more documents

Author: stevehu

README.md

@@ -73,5 +73,15 @@ software.amazon.awssdk.services.lambda.model.ResourceNotFoundException: Function
 	at java.base/java.lang.Thread.run(Thread.java:829)
 ```
 
+## Lambda Native Proxy
+
+### [About](doc/about.md)
+### [Benefit](doc/benefit.md)
+### [Limitation](doc/limitation.md)
+### [Architecture](doc/architecture.md)
+### [Design](doc/design.md)
+
+## Middleware Handlers
+
 ### [AuditMiddleware](doc/audit.md)
 ### [LambdaProxyMiddleware](doc/proxy.md)

doc/about.md

@@ -0,0 +1,5 @@
+Light Lambda Native Proxy Pattern is a new pattern for addressing Cross-Cutting Concerns(CCC) for Lambda functions deployed on AWS.
+
+The new pattern will allow users to take advantage of the Light API Platform without an http-sidecar container on Kubernetes or a standalone light-gateway. It is a pure Lambda function that addresses all Cross-Cutting Concerns and then invokes the downstream business Lambda function that can be built with any language.
+
+Although both http-sidecar and light-gateway can be used to address Cross-Cutting Concerns for Lambda functions, they add additional servers/services alongside native AWS services. For a team that is working with a Serverless environment, managing an HTTP sidecar container or a light gateway EC2 instance would be cumbersome and costly.

doc/architecture.md

@@ -0,0 +1,7 @@
+The Native Lambda Proxy is implemented as a native Lambda function to address cross-cutting concerns for one or more business Lambda functions. It brings the business Lambda functions to the light-ecosystem as HTTP Rest API endpoints.
+
+* Ingress:
+
+
+
+* Egress:

doc/benefit.md

@@ -0,0 +1,7 @@
+* Full Serverless: No need to manage containers on Kubernetes or standalone gateways.
+* Avoid Lock-In: Java Middleware Handlers can integrate with proprietary services and can be ported between cloud vendors.
+* Open Source: Cross-cutting concerns are supported by the Light-4j open-source community.
+* Code Generation: Scaffold a project based on the OpenAPI 3 specification with SAM template.
+* Configuration Driven: Lambda Native Proxy is deployed based on the configuration from the deployment pipeline for values.yml
+* Segregation of Concerns: Light Native Lambda will implement API CCC and the Lambda function API will implement business logic. Therefore, only Authentication and Authorization requests will invoke Business Lambda functions.
+* Friendly URL: Map AWS ALB auto-gen static DNS to friendly alias URL for VPC and Lambda Function URLs for the public cloud.

doc/limitation.md

@@ -0,0 +1,2 @@
+* Requires one extra Lambda function (~40ms overhead for CCC handlers non-cold start)
+* Requires Application Load Balancer(ALB) or AWS API Gateway or Lambda Function URLs.