Isn't this an anti-pattern? I mean, Lambda is suppose to eliminate the need for servers and server admin work. However, working with their services, like Lambda, are so tedious that solutions like Apex and Serverless have to be put on top of them. So now you have to learn to use a "Serverless Framework" to abstract the complexity of a serverless service?

In my view, they got it wrong. If the service is too cumbersome to use and requires these extra frameworks to actually use them effectively, then there's a fundamental problem with the service it relies on.