I understand that using CF makes things easier for the severless framework. However, this also means serverless’ limits are directly tied to the limitations of CF. Since serverless makes creating APIs easier, developers are going to want to create complicated APIs with serverless. This means developers will most likely hit the limits of CF; specifically the max 200 resources limit.
Since the developer is creating an API, using multiple serverless projects isn’t going to work (if it would work then please let me know how). The only potential solution I can see is the use of nested CF stacks. It doesn’t appear that serverless supports this out-of the-box. I need to use the Resources section of the serverless file. Would it be possible to provide some documentation on the best practices to accomplish this task? I think it is worth some documentation since it seems to me many users of serverless will hit this problem if they are developing any meaningful API.