Yes here too, and I think it's great and it's the way forward, but as with anything it requires some changes in thinking and approach. Re-composing everything into small functions, queues, and asynchronous events takes some getting used to. And there are some patterns that can help (e.g. using "job queues" can sometimes be the answer, rather than having a different queue for every type of action), when to use FIFO vs unstructured queues, and lots more.
Books like https://www.manning.com/books/serverless-architectures-on-aw... might help. And of course many consultants, good and bad, will cash in on the new trend, and there will be some high-profile disasters which should never have chosen serverless in the first place.