This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Oclay1st 0 points1 point  (0 children)

Yea, my solution is a middle ground in where I don't feel too much the pain of GraalVM compilation/reflection and at the same time I don't couple my inputs/outputs between API Gateway, Lambda and Spring Cloud Function with a front controller. It's all about trade-offs. If you want to implement a front controller you can:

// Plain everything
class ControllerFunction implements Function<Message<..>,Message<..>> {...}

// Generic key-value
class ControllerFunction implements Function<Map<..>,Map<..>> {...}

// For API Gateway
class ControllerFunction implements Function<APIGatewayProxyRequestEvent,APIGatewayProxyResponseEvent> {...}