search

dougmoscrop / serverless-plugin-split-stacks

A plugin to generate nested stacks to get around CloudFormation resource/parameter/output limits
297 stars 68 forks source link

CloudFormation template is invalid: Number of resources, 207 #47

Open harleyguru opened 6 years ago

harleyguru commented 6 years ago

Hello,

I've used this plugin to split my big AppSync service stack. But it's not splitting my stack.

Getting same error: resource limit issue of CFN.

I've used perType mode for splitting. But it just migrated some Lambda versions only to nested stack. (only 4 resources)

Can you help me and guide how to use this plugin with appsync-serverless-plugin? Thanks

kristiankyvik commented 6 years ago

Experiencing the same!

harleyguru commented 6 years ago

Hi @kristiankyvik I've found out this plugin won't solve this issue because AppSync plugin generates CFN template based on custom.appsync of main serverless.yml.

The best solution will be split your AppSync service into multiple ones. For example, you might create multiple service endpoints for each role in your system.

One for administrators, another one for normal users.

The key point is to reduce the number of resolvers.

The core of serverless architecture is to split the entire system into multiple independent microservices. We should do this for our AppSync service too.

dougmoscrop commented 6 years ago

Hmm it could be due to the order of the plugins. I've never heard of appsync. Is there an example repo I could see?

On Wed, Aug 22, 2018, 6:07 PM Анатолий Бурлаков notifications@github.com wrote:

Hi @kristiankyvik https://github.com/kristiankyvik I've found out this plugin won't solve this issue because AppSync plugin generates CFN template based on custom.appsync of main serverless.yml.

The best solution will be split your AppSync service into multiple ones. For example, you might create multiple service endpoints for each role in your system.

One for administrators, another one for normal users.

The key point is to reduce the number of resolvers.

The core of serverless architecture is to split the entire system into multiple independent microservices. We should do this for our AppSync service too.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dougmoscrop/serverless-plugin-split-stacks/issues/47#issuecomment-415197340, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjzFL22ma_-Jy1YjPvMbpDBiVYvZJC-ks5uTdYJgaJpZM4WGwsW .

harleyguru commented 6 years ago

Hi @dougmoscrop You can refer to this example: https://github.com/serverless/serverless-graphql

If this plugin will work on the output template generated after all plugins have been executed, it will be great.