lazywinadmin / 25-days-of-serverless

Repository responsible for 25 days of Serverless challenges

25 Days of Serverless

Contents

• Contents 25 days of Serverless
  • Main Goal 🎯
  • Rules 🎫
  • Suggested Resources 📑
  • Azure For Students Account ⭐️
  • How Submit Your Solution 🔥
  • Challenges 💻
  • Discord Channel 💬
  • Solutions 💡
    • Solutions Week-1
  • Contributing 🚩
  • Contributors Hall of Fame 🏆
  • Awesome - Azure Functions & Serverless 📚

Main Goal

There is no better way to learn a new technology than with gamification. And we're here to help you learn Serverless once and for all with 25 daily challenges: 25 days of Serverless! Come join!

Rules

1. Solve each coding challenge in the first 25 days of December.

2. Tweet your progress during the challenge period using the hashtag #25DaysOfServerless.

3. Submit the code of your solution as a PR to this repository before the sample solution gets published (usually 24h after the challenge is published).

4. You may get picked for a mention during our weekly wrap-up video. If you submit a PR you agree that we mention your name and/or nicknames (GitHub, Twitter) publicly in the context of 25 Days of Serverless.

Suggested Resources

• Visual Studio Code
• Azure Account
• Azure Functions Extension

Azure For Students Account

If you are a student at a College or University, you can create your Azure for Students account. This account will give you the benefit of having a $ 100 credit to use the Azure Services for free, without having a credit card and free developer tools as well. To activate this account, just access the link HERE.

Submit your solution as a custom ISSUE to our repository

🚨 Submission Process Change: Starting Dec 3, 2019 🚨

We've been blown away at the interest and engagement around this challenge! The previous process used Pull Requests. The new process uses Issues. We hope this change makes it easier for you to send us your amazing work, and for us to highlight your contributions. New PRs after Dec 4, 2019 may not be processed.

Be among the first contributors and solve the challenge within 24 hours of publishing. To have your contribution acknowledged, follow our CONTRIBUTING.md guidelines. The short version:

1. Create a Github repo with your solution for that challenge
2. Fill in the details for the Challenge Solution Submission issue and submit.

Have questions or comments? Submit a regular ISSUE here with details.

Discord Channel

Discussion Channels are available on Discord: Permanent Link to Server We ask everyone to be fair and helpful and to not spoil the challenges by publishing solutions prominently. The Microsoft Open Source Code of Conduct applies to all discussion channels.

Solutions

Here all the link solutions of each challenges published in dev.to

Solutions Week-1

Challenges	Description	Important Resources	Responsible	Solution
Webhooks (#1)	Implement a webhook using serverless - create a new repo for the daily challenges, listen to new PRs events and send out a celebratory tweet	Azure Functions - Webhooks	Jen Looper	Serverless Dreidel
Task Scheduler (#2)	Implement a cron job using serverless - send a daily reminder via text (use twilio) about the current challenge	Azure Functions - Cron Job	Jen Looper	Lucy's Dilemma
Webhooks (#3)	Create a webhook with serverless that GitHub sends commit data	Azure Functions Docs	Christian Nwamba	Github Commit (Push) Webhook
API Endpoint (#4)	Implement a function that connects to a database and returns data in a http response	Azure Functions - HTTP Trigger	Glaucia Lemos	Ezra's Potluck
Smart Apps (#5)	Implement a function that calls the Cognitive Services text analytics API and translates/analyses sentiment for a given text	Text Analytics API Documentation	Chris Noring	Naughty Or Nice
Durable Pattern (#6)	Implement a function that schedules a message to be sent on Slack/Teams	Azure Functions - Durable Functions	Christian Nwamba	Ada's Gifts
Smart Apps (#7)	Build an application that takes text as an input and returns an image found on unsplash or another image platform.	Azure Functions w/ Java	Sandra Ahlgrimm	Miguel needs our help

Solutions Week-2

Challenges	Description	Important Resources	Responsible	Solution
Status Page (#8)	Build a method to communicate the current status and running log of service disruptions to a global audience.	SignalR	Jason Hand	Santa, we have a problem

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [e-mail] with any additional questions or comments.

(documentation under development)

Contributors

Thanks goes to these wonderful people (emoji key):

Ernesto Cárdenas 💻

This project follows the all-contributors specification. Contributions of any kind welcome!