<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Srinivas Bada on Medium]]></title>
        <description><![CDATA[Stories by Srinivas Bada on Medium]]></description>
        <link>https://medium.com/@srinivas-bada?source=rss-27b4b31ed976------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2LBT8pyMnZoH9A8K</url>
            <title>Stories by Srinivas Bada on Medium</title>
            <link>https://medium.com/@srinivas-bada?source=rss-27b4b31ed976------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:49:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@srinivas-bada/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Free team to create better applications with Feature Flagging]]></title>
            <link>https://srinivas-bada.medium.com/free-team-to-create-better-applications-with-feature-flagging-1f0f9496f814?source=rss-27b4b31ed976------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f0f9496f814</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[feature-flags]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continous-integration]]></category>
            <dc:creator><![CDATA[Srinivas Bada]]></dc:creator>
            <pubDate>Sun, 30 May 2021 14:59:19 GMT</pubDate>
            <atom:updated>2021-05-30T14:59:19.246Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQZEfPbaU534dnedUsLTgQ.png" /></figure><p>When I got my first couple of development projects, in small teams working on small applications, developers felt that the best way to control slightly larger features was through some global <em>config file</em> or <em>environment file</em>. This was not seen as a method but rather a convenience to prevent over-complicating things. You’ve probably seen this approach used in your views with, let&#39;s say, a new shopping cart that you want to try out:</p><blockquote><strong>{{#if config.showNewFeature}}<br> {{&gt; newFeature}}<br>{{else}}<br> {{&gt; Feature}}<br>{{/if author criteria meet}}</strong></blockquote><p>… or maybe you recently changed your payment gateway or shipping vendor. In your controller code you create a decision point. In the development environment, you use vendor but on the production environment, you still use existing vendor. Hopefully, you have tests and if you do they will continue to test the old vendor.</p><blockquote><strong>if(config.useOpenBanking) {<br> this.sendTransactionOpenBanking(…);<br>}<br>else {<br> this.sendTransactionPayPal(…);<br>}</strong></blockquote><p>All of this makes sense right? When all is tested and working the config is updated and <em>push a button</em>: new feature is released. Feature flags are still the same conceptually, except that a lot more has happened with them in last couple of decades. Complete open-source libraries have been written just to manage feature flags. There are now SaaS products out there that allow turning certain code paths on and off at run-time.</p><p>using them not just to show and hide features but to also increase productivity, mitigate risk, target their audience, A/B test their traffic, and for various other use cases.</p><h3>Working with Feature Flags</h3><p>So let’s say you’re convinced that working with feature flags is going to bring you all the benefits that many claim to say they bring. What are some of the best practices when using feature flags.</p><p>One of the main concerns that developers with feature toggles is the idea of having toggles everywhere in code. Let’s face it, having <strong>if / else</strong> logic everywhere in your code does not look elegant at all. It’s also fairly easy to misuse and make your implementation a lot more difficult than it should be. Below are some common best practices that you should consider.</p><h3>Types of Feature Flags</h3><p>There are few types of feature flags and types can be categorized by a couple of main characteristics: <em>longevity</em> and <em>dynamism</em>.</p><p>To explain these categories further, I will list a few common ones that are often talked about. I’m sure you might have some of your own use cases too.</p><ul><li><strong><em>Release toggles</em></strong>: More often than not these are on/off switches that are used to control whether a feature is enabled or not. They are short-lived and removed after the feature is released.</li><li><strong><em>Operational toggles</em></strong>: Typically used to control flow on the back end. An example could be algorithm changes, upgrading or retiring old APIs, etc. These are also short-lived and ought to be removed after task is complete.</li><li><strong><em>Experimental Toggles</em></strong>: These are typically used for A/B or multivariate testing and are typically longer-lived flags that can be removed once we no longer need to collect user testing data.</li><li><strong><em>Permission Toggles</em></strong>: This is commonly talked about and is used to control product experience users have. I think doing this is actually a bad use case for feature flags and personally don’t recommend it. This sort of information would be coming from your user properties</li></ul><p>Along with side FF also helps with</p><p>Feature flags make development faster and safer || Continuous Delivery</p><p>Separate deploy from release || Progressive Delivery</p><p>Target users without sharing private data || A/B Testing or Test in Production</p><p>Manage your blast radius — roll out in stages || Trunk-Based Dev<br>Never roll back again</p><blockquote>Covered for optimized solutions for front(end), back(end), and mobile</blockquote><h3>To Summarize …</h3><ul><li>Feature flags have been around for a long time because they are simple to use and developers felt productive when using them. We’ve introduced sophisticated tools and processes to improve velocity and quality. With this we’ve also added complexity. It might be a time to simplify and bring the flags back.</li><li>Feature flags can work well for companies but in general, it’s best to keep feature flags short-lived and small in number. Too many flags or long-lived flags add complexity and are deliberate tech debt. Cleaning up feature flags is important to keep a codebase sane.</li><li>Using feature flags can help companies to ship more often, minimize risk, increase productivity, and even help with targeting users and A/B test features. Evaluating a company’s branching strategy with feature flags can be very powerful, especially if you need to ship frequently.</li><li>Keep coupling with feature flags service to a minimum, create a config abstraction layer and try to avoid having flags in your core.</li></ul><p><strong>References</strong>:</p><p>Free your team to create better software<br><a href="https://www.split.io/product/feature-flags/">https://www.split.io/product/feature-flags/</a></p><p>Feature Flagging for Back-End &amp; Microservices<br><a href="https://launchdarkly.com/blog/feature-flagging-for-back-end-and-microservices/">https://launchdarkly.com/blog/feature-flagging-for-back-end-and-microservices/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f0f9496f814" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Solutions Architect Associate (SAA-C02): my learnings & path to success]]></title>
            <link>https://srinivas-bada.medium.com/aws-solutions-architect-associate-saa-c02-my-learnings-path-to-success-87ac4b194bf3?source=rss-27b4b31ed976------2</link>
            <guid isPermaLink="false">https://medium.com/p/87ac4b194bf3</guid>
            <category><![CDATA[aws-solutions-architect]]></category>
            <category><![CDATA[saa-c02]]></category>
            <category><![CDATA[recommendations]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws-certification]]></category>
            <dc:creator><![CDATA[Srinivas Bada]]></dc:creator>
            <pubDate>Thu, 25 Feb 2021 16:03:44 GMT</pubDate>
            <atom:updated>2021-02-25T17:55:26.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="AWS Solutions Architect Associate (SAA-C02) : my learnings &amp; path to success" src="https://cdn-images-1.medium.com/max/876/1*uRdekyQIOuK2vn7DxTeG4A.png" /></figure><p>Hello there! Are you looking to crack the AWS Certified Solution Architect — Associate Exam in 2021 here are few learnings I would like to share as it might help others to prioritize as AWS is a big spaghetti bowl with 300+ AWS services with interconnected service, hopefully, this guide will give one a head start. I attended SAA-C02 certification in Feb 2021 and got a score of 870/1000 (passing required is 72%)</p><p>Before I start, earning any certification needs the 2 most powerful tools in investing are <strong>PATIENCE and DISCIPLINE</strong>.</p><p><strong>Where do I start my certification?<br></strong>If you lost which AWS certification is more relevant to your-set this is a short video that might help to pick the right path.</p><p>AWS Certification Recommendations<br><a href="https://learn.cantrill.io/p/aws-certification-recommendations">https://learn.cantrill.io/p/aws-certification-recommendations</a></p><p><strong>What is SAA-C02 is about?<br></strong>The AWS Certified Solutions Architect — Associate examination is intended for individuals who perform a solutions architect role and have one or more years of hands-on experience designing available, cost-efficient, fault-tolerant, and scalable distributed systems on AWS.</p><p>Earners of this certification have a comprehensive understanding of AWS services and technologies. They demonstrated the ability to build secure and robust solutions using architectural design principles based on customer requirements. Badge owners are able to strategically design well-architected distributed systems that are scalable, resilient, efficient, and fault-tolerant.</p><p><strong>Abilities Validated by the Certification</strong></p><ul><li>Effectively demonstrate knowledge of how to architect and deploy secure and robust applications on AWS technologies</li><li>Define a solution using architectural design principles based on customer requirements</li><li>Provide implementation guidance based on best practices to the organization throughout the life cycle of the project</li></ul><p><strong>Recommended Knowledge and Experience</strong></p><ul><li>Hands-on experience using compute, networking, storage, and database AWS services</li><li>Hands-on experience with AWS deployment and management services</li><li>Ability to identify and define technical requirements for an AWS-based application</li><li>Ability to identify which AWS services meet a given technical requirement</li><li>Knowledge of recommended best practices for building secure and reliable applications on the AWS platform</li><li>An understanding of the basic architectural principles of building on the AWS Cloud</li><li>An understanding of the AWS global infrastructure</li><li>An understanding of network technologies as they relate to AWS</li><li>An understanding of security features and tools that AWS provides and how they relate to traditional services</li></ul><p><strong>Ground reality checks -</strong></p><p><strong><em>Is this certificate recommended for Backend Engineers? <br></em></strong>Absolutely YES! It covers services you need for the backend development like Kinesis, SQS, DynamoDB, RDS/Aurora, Elasticache, CloudWatch, Lambda, S3, EC2, IAM, ECS… What’s more, the exam is based on the AWS Well-Architected Framework. This is an official AWS guideline that teaches you how to drive your architectural decisions based on reliability, security, efficiency, and cost-effectiveness.</p><p><strong><em>What about Frontend Engineers?<br></em></strong>Absolutely YES! You’ll learn about Cloudfront, S3, Route53, Lambda, Cognito, IAM, CloudWatch. Again, with emphasis on reliability, security, efficiency, and cost-effectiveness.</p><p><strong><em>What about Data Engineers/Scientists?<br></em></strong>This exam touches a few of AWS core data services useful for Data Engineers/Scientists<br>AWS Glue, EMR, S3, Athena, Redshift</p><p><strong><em>What about DevOps/SysOps?<br></em></strong>Yes! You’ll learn:</p><ul><li>How to set up a VPC from scratch.</li><li>How to create private/public subnets with high availability. Setting up internet gateway, NAT gateway, route tables.</li><li>How to connect two VPCs with VPC peering.</li><li>How to enable private connection from services inside a VPC to AWS services without going through the internet with VPC endpoints.</li><li>How to monitor VPC with Flow Logs.</li><li>How to connect on-premise data center with VPC: VPN, DirectConnect, TransitGateway, CloudHub.</li><li>How to manage larger organizations in AWS with multiple accounts and cross-account access using AWS Organizations. How to easily globally restrict access to certain services.</li><li>How to use Route53 to set up the domain(s) and hosted zone(s) with different routing policies.</li></ul><p><strong><em>What about Engineering Managers/Leaders?</em></strong></p><p>Absolutely YES!! However, the exam is very technical and will require you to study all of the mentioned above. If you’re an Engineering Manager, the Solutions Architect exam will help get have a better overview of how to use AWS to meet compliance, Optimize cost requirements, and what are its auditing capabilities.</p><p>You’ll be exposed to industry-specific solution architectures and to trade-offs those architectures come with. This might be interesting for you to understand them and see what are the other options. This will help you work with engineering teams more productively. You can find example solutions architectures here: <a href="https://aws.amazon.com/solutions/">https://aws.amazon.com/solutions/</a>.</p><p><strong>How to prepare?</strong></p><p>I took the Udemy course by <strong>Stéphane Maarek</strong> (From the sweet country of France) and I totally recommend it. It puts emphasis on understanding rather than cramming with full hands-on for each AWS service required for the exam. Stéphane has covered all the latest test data, exhaustive hand-on, and cover each topic in both breadth and depth. I really enjoyed it. Udemy offers an unlimited reply so as you can listen on the go, practice hands-on once you are back at the home. The best part is the Quiz at the end of each chapter tests your learnings to make sure you have understood it thoroughly.</p><p>I took those six preparation exams by <strong>Jon Bonso</strong>. [I felt tests from Jon seems to be much easier, but they are good ]<br>They resemble the questions you’ll see in the exam, although they’re obviously not the same. This is a good learning opportunity for you and the ultimate way to consolidate your knowledge after the course</p><p>I took another six preparation exams by <strong>Neal Davies</strong>. [Neal had covered the right size of questions like you will get in real test ]<br>it’s also a good learning opportunity.</p><p>Apart from this — Read [ just google it you will find these pdf’s as they are constantly updated ]<br>- AWS Well-Architected Framework whitepaper.<br>- AWS Cost Optimization Pillar<br>- Using Amazon Web Services for Disaster Recovery<br>- Overview of Amazon Web Services: AWS Whitepaper — DO NOT MISS THIS</p><p><strong>How long does it take to prepare?<br></strong>In my case, it was 2 months. I studied intensively from the beginning of Jan to Mid-Feb 2021. Started with mock tests for 2 weeks [replayed a few to make sure I have consistent 85% scores] once I felt confident I booked the test and attended the next day.</p><p>I have prepared my notes up to 149 pages on Google doc [YES, YES, YES] so as I can revise them before I pop in the test room.</p><p><strong>Test Hall: <br></strong>It was quite well organized, they let you in with an identity-check and start your test in 10-min once you are done you will see your results instantly once you answer all 65 followed by a survey.</p><p>Detailed report scores and certificates will come in a few day&#39;s time.</p><p><strong>Few other tips:</strong></p><p>1. Pick answers by eliminating the ones you are confident so as you narrow to the right answers</p><p>2. Avoid examtopics as I found sometimes you land in incorrect answers as it completely community-driven, you might lose marks in the actual exam.</p><p><a href="https://www.examtopics.com/exams/amazon/aws-certified-solutions-architect-associate-saa-c02/view/">https://www.examtopics.com/exams/amazon/aws-certified-solutions-architect-associate-saa-c02/view/</a></p><p>3. Practice as many mock tests you can, until you get a consistent 85% pass rate</p><p>practice test covers the following domains:<br>- Design Resilient Architectures <br>- Define Performant Architecture<br>- Specify Secure Applications and Architectures<br>- Design Cost-Optimized Architectures<br>- Define Operationally-Excellent Architecture</p><p>4. Read a lot of AWS Faq: as you might get a few questions from here <br><a href="https://aws.amazon.com/faqs/">https://aws.amazon.com/faqs/</a></p><p>5. Follow this mindmeister — I loved this mind map</p><p><a href="https://www.mindmeister.com/1179061789/aws-certified-solutions-architect-associate?fullscreen=1#">https://www.mindmeister.com/1179061789/aws-certified-solutions-architect-associate?fullscreen=1#</a></p><p>6. Use reviewnprep to validate your self, it handy <a href="https://reviewnprep.com/">https://reviewnprep.com/</a></p><p>7. AWS Certifications recommendations by Cantrill — I love these too <br><a href="https://learn.cantrill.io/p/aws-certification-recommendations">https://learn.cantrill.io/p/aws-certification-recommendations</a></p><p>8. AWS Practice Test<br><a href="https://aws.psiexams.com/#/dashboard/test-details/AADBJCZT;testCode=BMY5NAC6">https://aws.psiexams.com/</a></p><p>9. TutorialDojo (<a href="https://tutorialsdojo.com/comparison-of-aws-services/">https://tutorialsdojo.com/comparison-of-aws-services/</a>) has this amazing cheatsheet where they had summarized the key difference between the services of AWS which was very useful for me.</p><p>10. Finally, Keep Calm and Carry On — I know its a lot</p><p><strong>Summary</strong></p><p>That’s it! I hope this gave you a better understanding of why you’d consider attending this certification over the others and what are the possible ways of preparation and get ahead of curve in cloud computing.</p><p>Please post any questions you might have, I’m happy to help, and good luck with your prep.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87ac4b194bf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Cost Optimization Best Practices / Reducing Your Amazon Bill]]></title>
            <link>https://srinivas-bada.medium.com/aws-cost-optimization-best-practices-reducing-your-amazon-bill-4c13a8edbef0?source=rss-27b4b31ed976------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c13a8edbef0</guid>
            <category><![CDATA[aws-billing]]></category>
            <category><![CDATA[aws-instance]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[aws-cost-optimization]]></category>
            <category><![CDATA[return-on-investment]]></category>
            <dc:creator><![CDATA[Srinivas Bada]]></dc:creator>
            <pubDate>Fri, 27 Nov 2020 10:15:43 GMT</pubDate>
            <atom:updated>2020-11-27T10:15:43.980Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElqKvD-vFI8eJw-qty4Sgg.png" /></figure><p>Moving to the cloud gives everyone access to enterprise-class technology. It also allows smaller businesses to act faster than big, established competitors. Pay-as-you-go service and cloud business applications mean small outfits can run with the big boys and disrupt the market, all while remaining lean and nimble.</p><p>One of the advantages of cloud computing is its ability to <strong>fit the infrastructure to your needs, you only pay for what you really use</strong>. That is how most hyper-growth startups have managed their incredible ascents.</p><p>Users of Amazon Web Services are likely familiar with some AWS cost optimization best practices, but probably here are a few tips and tricks to save yours/your organizational costs on AWS infrastructures if you are new to AWS or probably thinking to optimize.</p><p><strong>1. Rightsizing EC2 Instances <br></strong>It&#39;s always ideal to resize instances when there is a growing demand of users and scale down as the demands drop. Ex: Once the peak season is over moving from large/xlarge to medium will save to make sure you manage demand and supply resources</p><p>The purpose of rightsizing is to match instance sizes to their workloads.</p><p><strong>2. Scheduling on/off times on rolling build deployments<br></strong>It’s worth scheduling on/off times especially for non-production instances / internal test env such as those used for developing, staging, testing as you will save around 55% of running these instances if you apply an “on” schedule of 8.00 a.m. to 8.00 p.m. Monday to Friday. However, it’s possible to save a lot more — especially if development teams work in irregular patterns or at irregular hours.</p><p><strong>3. Delete obsolete snapshots<br></strong>Snapshots are an efficient way to back up data on an EBS volume to S3 storage, however, one does not need a backup of more than 50 prior snapshots therefore keep them optimal as every snapshot occupies memory on S3 storage leading to a huge bill.</p><p><strong>4. Purchasing Reserved Instances<br></strong>Purchasing Reserved Instances is an easy way to reduce AWS costs. It can also be an easy way to increase AWS costs if you don’t utilize the Reserved Instance as much as you expected to, purchase the wrong type of Reserved Instance, or purchase a “standard” Reserved Instance only to find AWS prices fall over the term of your reservation by more than the reservation “saves”.</p><p>The two major avenues for discounts on AWS are committing in advance to a reserved instance for 1–3 years.</p><p><strong>5. Terminate zombie/unused assets<br></strong>This is the most common problem in pouring millions of dollars to AWS just because engineers who have used the assets for experiments or left the company, his assets will be billed to the Group. Therefore make sure every owner of Assets has an approver and contributor thereby you got a backup to bring the instances those unused.</p><p><strong>6. Move infrequently-accessed data to lower-cost tiers / Move cold data to cheaper storage tiers<br></strong>Things like the Past 2 years&#39; data can be easily moved to Cold storage as they reduce storage costs per GB from $0.023 to as low as $0.00099. Generally, customers tend to use recent and past 6–8 months of data frequently.</p><p>There is a very guide from AWS Ref: <a href="https://d1.awsstatic.com/whitepapers/architecture/AWS-Cost-Optimization-Pillar.pdf?ref=wellarchitected">AWS Well-Architected Framework</a> its a worth a read especially your apps are in Data / Analytics / Storage / Messaging etc</p><p>Here are few <a href="https://github.com/search?q=org%3Akeen+AWS+Cost&amp;type=topics">tools</a> on GitHub to quickly set up to know costs on your running instances.</p><p><a href="https://github.com/trackit/trackit">trackit</a> [ Go] | <a href="https://github.com/dnavarrom/aws-cost-explorer">aws-cost-explorer</a> [ JavaScript ] | <a href="https://github.com/dnavarrom/grafana-aws-cost-explorer-backend">grafana-aws-cost-explorer-backend</a> [ JavaScript ]</p><p>If you like this article gives a thumbs up and have similar stuff to share please do.</p><p>Thanks for reading, hope you enjoyed it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c13a8edbef0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Agile Teams can be successful?]]></title>
            <link>https://srinivas-bada.medium.com/how-agile-teams-can-be-successful-ff4bb694d944?source=rss-27b4b31ed976------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff4bb694d944</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[constant-learning]]></category>
            <category><![CDATA[speed-to-market]]></category>
            <dc:creator><![CDATA[Srinivas Bada]]></dc:creator>
            <pubDate>Sat, 21 Nov 2020 07:01:35 GMT</pubDate>
            <atom:updated>2020-11-21T07:01:35.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Agile Team" src="https://cdn-images-1.medium.com/max/750/1*lLlISHx172hzfmksJJSdrw.jpeg" /></figure><p>Market pressure and the need for increased competitiveness tend to bring a shift in the mindset of Agile Software Development where teams and overall culture in an organization transform to put things faster onto the customer’s hands.</p><p>Here are a few practical facts that worked well in my work that enabled teams to deliver faster with Agile Development.</p><ul><li>Always motivate the team and Product Managers by incremental delivery by increasing client satisfaction</li><li>Protect the team, especially when working with cross Geo / Cross distributed teams those contribute to the same code base</li><li>Act as Servant/leader when the team needs assistance</li><li>Act as a mediator between Teams and Product Management on alignment on roadmap and delivery of stories</li><li>Facilitate Pre-planning/backlog grooming/planning / Track progress and action on blockers that teams work depends with</li><li>Constantly improve a process with retrospective and learn from prior mistakes by improving teams velocity and confidence every iteration and upping the bar</li><li>Empower teams with responsibility equals accountability equals ownership therefore teams wins together</li></ul><p>True scrum values are to facilitate a team to keep the pace of moving parts using agile techniques.</p><p>To fulfill the prerequisites and attaining the necessary knowledge to lead an agile team in a self-serviced please refer to a very good guide on Agile Coaching<br><a href="https://medium.com/@Yodiz/agile-coaching-c2707ed54af3">https://medium.com/@Yodiz/agile-coaching-c2707ed54af3</a></p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff4bb694d944" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>