vijaybiradar / aws-real-time-use-cases

Repo of quick starts for real time AWS use cases 🎓

AWS Real Time Use Cases

Repo containing quick starts for real time AWS use cases.

Who should use this repo

1. If you have a scenario or an issue that you faced in your work and think it is interesting enough to share with the community. Go ahead and raise a pull request. All we require a short brief description of your issue. If you already know the solution, do add to it.

2. If you are looking for learning real life AWS Scenarios, then go ahead and look at this repo. The repo follows a very simple naming convention

DIFFICULTY-LEVEL-AWS-DOMAIN-BRIEF-SCENARIO-TITLE

Generic Guidance

A very broad guidance on the difficulty level on the topics. These are not written on stone, more like lines on shifting sands, can be very subjective depending upon the audience and the ecosystem.

• 100: Introductory and overview.
• 200: Intermediate level, requires specific details about the topic.
• 300: Advanced level, requires in-depth understanding of features.
• 400: Expert level requires expert-to-expert interaction & coverage of specialized deep-dives into specific topics.
• 500: Thought Leadership
• Anything more than should be Zen Mode or God Mode what do you say?

✏️ Tips on writing good use-cases

• Titles - Make your titles succinct, informative, compelling, and written with the audience in mind
  • Keep it to a single line
  • Use Keywords(not jargons) and verbs
• Structure your use-case into 3 segments
  • Beginning
    • Introduce who (or your organisation) you are
    • Describe the business challenge
    • Explain the impact of the challenge
  • Middle/Solution
    • Describe the technical challenge
    • Describe the plan
    • Explain(if possible) what were the choices and trade-offs
  • End/Conclusion
    • Give usecase examples
    • Describe technical & business benefits
    • Explain how this solution can be extended or future roadmap
• Use fewer than 35 words per sentence.
  • Instead of, due to the fact that use because
  • Instead of, totally lacked the ability to use could not
• Replace adjectives with data
  • Instead of, We made the performance much faster use We reduced server side latency from 10mn to 1ms
• Quantify success criteria; Eliminate vague/opaque words
  • Instead of, nearly all customers use 83% of the premium members
  • Instead of, significantly better use NPS 6.5 (+25% YoY)
• Does your use-case clear the so what check?

Check out this sample template

💡 Help/Suggestions or 🐛 Bugs

Thank you for your interest in contributing to our project. Whether it is a bug report, new feature, correction, or additional documentation or solutions, we greatly value feedback and contributions from our community. Start here

👋 Buy me a coffee

Buy me a coffee ☕.

🏷️ Metadata

Level: 300