Hi IH community, I build a scalable waitlist/lineup app using AWS, does it look useful to you?

I've had detailed this idea of AWS templates a while back. Here are some thoughts.

Launch Stack Button
Something like a button to deploy will be greatly helpful. (There is a AWS post for creating your own stack url - https://aws.amazon.com/blogs/devops/construct-your-own-launch-stack-url/ ). I hope this still works.
Cloudformation templates
This would mean that you create cloudformation templates for all your stacks. You can opensource some stacks and measure people's interests (by the number of Github stars maybe)
Cost of Stack
Can your provide what will be the approx. cost of using each stack? Something like the mini AWS pricing calculator for this stack (the variables might just be expected number of requests, bandwidth etc). I think that will be a great value add. Maybe people will be interested in stacks that are very low-cost, say AWS lambda
AWS Lambda
I'm particularly interested in serverless, as I think it will mature as a solution in the coming years and might offer lower cost stacks and startup time might gradually reduce to acceptable levels. I think this is a great area to explore in the future.

Here are some interesting posts:

Monetization
If you are planning to monetize this, I think, you should identify your target market. Currently it looks like you are trying to sell to developers. With a 'Launch Stack' button (as in [1]), it may be possible to sell to other markets, as deploying is as easy as clicking a button.

a) Monetize infra code: Create a library of cloudformation stacks, some free and some paid. (An example is https://gruntwork.io/infrastructure-as-code-library/), diversify into AWS stack creation training etc.

b) Monetize application code: You can create complete applications that offers value to the enduser. Say for example - launch an ecommerce site in AWS by just clicking a button and everything will get deployed to AWS.

I'm trying to build a similar solution but more based on application code. Lets talk, and maybe we can work something out.

Say something nice to coderecipe…

2

How does Code Recipe differ from Cloudcraft?

zencephalon

·
7 years ago
·
1. 1
  
  Cloudcraft is doing great things to allow content publishers to create 3d diagrams, CodeRecipe caters to developers so that you can take what’s available and directly consume it. What you see now is only our first phase, I would love to collect more feedback from you and other people to see how we can be more useful to you!
  
  CodeRecipe.ai
  
  ·
  7 years ago
  ·
1
I've had detailed this idea of AWS templates a while back. Here are some thoughts.
1. Launch Stack Button
  Something like a button to deploy will be greatly helpful. (There is a AWS post for creating your own stack url - https://aws.amazon.com/blogs/devops/construct-your-own-launch-stack-url/ ). I hope this still works.
2. Cloudformation templates
  This would mean that you create cloudformation templates for all your stacks. You can opensource some stacks and measure people's interests (by the number of Github stars maybe)
3. Cost of Stack
  Can your provide what will be the approx. cost of using each stack? Something like the mini AWS pricing calculator for this stack (the variables might just be expected number of requests, bandwidth etc). I think that will be a great value add. Maybe people will be interested in stacks that are very low-cost, say AWS lambda
4. AWS Lambda
  I'm particularly interested in serverless, as I think it will mature as a solution in the coming years and might offer lower cost stacks and startup time might gradually reduce to acceptable levels. I think this is a great area to explore in the future.
Here are some interesting posts:
- https://medium.com/@amiram_26122/the-hidden-costs-of-serverless-6ced7844780b
- https://medium.freecodecamp.org/how-i-cut-my-aws-bill-by-90-35c937596f0c
1. Monetization
  If you are planning to monetize this, I think, you should identify your target market. Currently it looks like you are trying to sell to developers. With a 'Launch Stack' button (as in [1]), it may be possible to sell to other markets, as deploying is as easy as clicking a button.
a) Monetize infra code: Create a library of cloudformation stacks, some free and some paid. (An example is https://gruntwork.io/infrastructure-as-code-library/), diversify into AWS stack creation training etc.

b) Monetize application code: You can create complete applications that offers value to the enduser. Say for example - launch an ecommerce site in AWS by just clicking a button and everything will get deployed to AWS.

--

I'm trying to build a similar solution but more based on application code. Lets talk, and maybe we can work something out.
awin

·
7 years ago
·
1. 1
  
  Loving your insights! Let me schedule a time to learn more from you :)
  
  CodeRecipe.ai
  
  ·
  7 years ago
  ·