Skip to content
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

Setup API Gateway #64

Closed
daltonfury42 opened this issue Jul 13, 2020 · 8 comments
Closed

Setup API Gateway #64

daltonfury42 opened this issue Jul 13, 2020 · 8 comments

Comments

@daltonfury42
Copy link
Collaborator

No description provided.

@rahulkrishnan221
Copy link

rahulkrishnan221 commented Dec 7, 2020

I am curious why you cloudformation or cdk are not being used?
Are you creating these resources manually? If once, setup CI/CD will be much better.
Let me know if it is not already existing, I can contribute on that.

@daltonfury42
Copy link
Collaborator Author

Hi @rahulkrishnan221 would love to know your thoughts on this...

Since we are still in the hobby project / prototype phase, and I have no plans on monetising, I want to stay within free tier limit as much as possible. I have set up CICD via TravisCI+CodeDeploy, and code is just the jar running on a ec2 machine.

The develop -> push -> deploy workflow is pretty smooth.

For this setup, I thought that cloudformation would be an overkill, and hence did not bother to learn or set it up. What do you have in mind?

@rahulkrishnan221
Copy link

CDK/cloudformation makes life much easier once setup due to following reasons.

  1. In case if you are migrating this project to some other aws account or it became big with lot of resources and you have Cloudformation/cdk in place it will be 2 -3 line of command and all your resources will be created/deployed again easily.
  2. I am seeing issues such as adding NLB/API gateway or setting cloudwatch logs/alarms those thing will become part of your stack, from that I am seeing a huge possibility that at some point your service will be eating lot of resources and at that case resource management will become a big issue.
  3. Cloudformation/cdk is in free-tier, these services provide to you by aws out of box solution for easy creation and manitainence of resources.
  4. SimplQ is pretty good idea and it is possible that many developer will contribute in future so in that case it will be difficult for them to replicate the stack in case if you don't have Cloudformation/cdk not in place.

@rahulkrishnan221
Copy link

Hi @daltonfury42 let me know if can contribute by introducing cdk ?

@daltonfury42
Copy link
Collaborator Author

daltonfury42 commented Dec 18, 2020 via email

@rahulkrishnan221
Copy link

How could we connect could you provide your email or discord id or anything else?

@daltonfury42
Copy link
Collaborator Author

Lets connect on linkedin then I can send you a google meet link.

https://www.linkedin.com/in/navaneeth-kishore/

@daltonfury42
Copy link
Collaborator Author

@rahulkrishnan221 you can create more specific issues as we discussed. I'll close this one for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants