diff --git a/week1/community-contributions/day2 Exercise_RHK.ipynb b/week1/community-contributions/day2 Exercise_RHK.ipynb index ffd2f4f..85ab4f2 100644 --- a/week1/community-contributions/day2 Exercise_RHK.ipynb +++ b/week1/community-contributions/day2 Exercise_RHK.ipynb @@ -215,7 +215,7 @@ }, { "cell_type": "code", - "execution_count": 6, + "execution_count": null, "id": "402d5686-4e76-4110-b65a-b3906c35c0a4", "metadata": {}, "outputs": [], @@ -239,73 +239,16 @@ }, { "cell_type": "code", - "execution_count": 9, + "execution_count": null, "id": "cca8ae91-ad1e-4239-951f-e1376a5ec934", "metadata": {}, - "outputs": [ - { - "name": "stdin", - "output_type": "stream", - "text": [ - "Please complete the verification in the browser and press Enter to continue... \n" - ] - }, - { - "data": { - "text/markdown": [ - "This article discussing Serverless architecture is a comprehensive overview of the concept, its benefits, and challenges. Here's a summary of the main points:\n", - "\n", - "**What is Serverless Architecture?**\n", - "\n", - "Serverless computing allows developers to run their applications without managing servers or provisioning resources upfront. Instead, they pay only for the compute time used.\n", - "\n", - "**Key Techniques:**\n", - "\n", - "1. **Function as a Service (FaaS)**: Ephemeral function instances that can be executed with specific inputs and outputs.\n", - "2. **Background Services**: Tightly integrate third-party remote application services directly into the frontend of an app.\n", - "\n", - "**Benefits:**\n", - "\n", - "1. Reduced operational and development costs\n", - "2. Easier management and scaling\n", - "3. Reduced environmental impact\n", - "4. Faster time-to-market\n", - "\n", - "**Challenges:**\n", - "\n", - "1. Debugging and monitoring complexity\n", - "2. Limited control over server-side code execution\n", - "3. High dependencies on cloud providers\n", - "\n", - "**Serverless Landscape:**\n", - "\n", - "The author expects the Serverless community to grow, with upcoming conferences, meetups, and online groups.\n", - "\n", - "**Conclusion:**\n", - "\n", - "Serverless architecture offers significant advantages but also presents challenges. It's essential to weigh the pros and cons carefully before adopting a Serverless approach. Despite its \"slightly awkward teenage years,\" Serverless is expected to continue evolving and maturing in the near future.\n", - "\n", - "Key Takeaways:\n", - "\n", - "1. Understand the basics of Serverless computing.\n", - "2. Be-aware of the trade-offs between scalability, control, and cost.\n", - "3. Consider your use case before adopting a Serverless architecture.\n", - "4. Stay updated with the latest developments and best practices in the Serverless community." - ], - "text/plain": [ - "" - ] - }, - "metadata": {}, - "output_type": "display_data" - } - ], + "outputs": [], "source": [ "headers = {\n", " \"User-Agent\": \"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36\"\n", "}\n", "\n", - "PATH_TO_CHROME_DRIVER = \"/Users/rakeshhk/Rakesh/softwares/chromedriver-mac-arm64/chromedriver\"\n", + "PATH_TO_CHROME_DRIVER = \"/path/to/chromedriver\"\n", "\n", "class Website:\n", "\n",