New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SAM, Amplify, Cloud Development Kit (CDK), etc? #703

Closed
0xdevalias opened this Issue Sep 13, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@0xdevalias
Copy link

0xdevalias commented Sep 13, 2018

This is more of a pondering/question.. but how does (or do you see) SAM, Amplify, Cloud Development Kit (CDK), etc playing together?

In a lot of ways it feels like that there is a fair bit of crossover between all of the tools (at least in the CLI area), and that they would work pretty synergistically together (or outright replace each other)

For example, from my little experience playing with/reading about them:

Amplify seems nice for quickly generating some common 'stack features' for a project, but seems less nice when it comes to customising those things later on, and since it (currently) seems to only generate CloudFormation json, and doesn't appear as though it has any SAM features, it all feels pretty verbose.

SAM is nice and relatively quick for implementing the various little things it supports, but very quickly degenerates into having to manually wire together a bunch of CloudFormation yaml directly, and has a few interesting quirks/similar with regards to file uploads, stacksets, etc.

Cloud Development Kit (CDK) sounds like it will be a good toolset for tying together features and functions, and in a lot of ways feels like it could encapsulate or almost replace the others. In particular, I get the feeling that everything Amplify currently does could be done in a simpler/more maintainable way with CDK (or perhaps Amplify could use CDK's functionality under the hood)

If I had to guess.. I would say that a combination of CDK + SAM's translations would make for the 'nicest' end result.. but this is all high level pondering/speculation. Ultimately it comes down to what is going to make my life easier/quicker/less boilerplatey as a developer, and which of these is likely to be hanging around in the long run.

Ref:

@eladb

This comment has been minimized.

Copy link
Contributor

eladb commented Dec 17, 2018

Thanks for bringing this up. This is definitely a story we'd like to improve for customers, and we are working on it.

@eladb eladb closed this Dec 17, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment