Hi!
Yes, I’ve considered them in the past but the problem is that you will add libraries that eventually you need to maintain. I know that boilerplate is boring and sometimes useless, but adding a library that affects your POJOS can significantly affect the evolution of your product. Your models, as I already mentioned, should always been as Plain Old Java (Kotlin?) Objects. In the last years that’s what people called vanilla, and that’s the main reason why in the case of Frontend (for instance) certain products such as Bootstrap or Foundation have lost their appealing, specially with experienced developers.
Finally, try to reduce any kind of library or tactic that potentially affect the performance of your code when you are using Serverless Architectures. This kind of libraries usually use introspection/reflection techniques that could make sense when you can cache or keep state of our backend. But even when in theory you can keep state with serverless, assuming that functions are always cold is the right way to go. Note: in some late articles, I’ll explain how the use this kind of libraries affected the performance of my functions in a scale of 1:3.
Thanks for the comment and I hope that you enjoyed it :)
