New answers tagged

0

Joachim Sauer already did a good job answering you question but only hinted at something I regard as important. Since Lambdas are no classes they are also not compiled as such. All anonymous inner classes result in the creation of a .class file which in turn has to be loaded by the ClassLoader. So using Lambdas instead does not only make your code more ...


1

Architecturally, it makes sense to deploy such a shared component separately so that its concerns were properly isolated from the others. Instead of calling it as an internal component, you would issue a (potentially fire and forget) call to another "function" for system-level logging. This also makes sense for scalability because as your system scales out ...


0

AWS and maybe others provide a built-in service for logging that you are invited to use. If you don't want to use it, you probably have to push an object to a cloud storage instead. In a classic lambda function architecture, your service is launched on call, ressources are allocated for the duration of the program, then fred. You typically don't have ...



Top 50 recent answers are included