<?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 Swapnil Kulkarni on Medium]]></title>
        <description><![CDATA[Stories by Swapnil Kulkarni on Medium]]></description>
        <link>https://medium.com/@cloudnativehero?source=rss-c7d21ddfb13b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j90SzNR-mCNSuTUp4CInWg.jpeg</url>
            <title>Stories by Swapnil Kulkarni on Medium</title>
            <link>https://medium.com/@cloudnativehero?source=rss-c7d21ddfb13b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:27:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cloudnativehero/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[ Day 1 of 100: What Is FinOps and Why Should You Care?]]></title>
            <link>https://cloudnativehero.medium.com/day-1-of-100-what-is-finops-and-why-should-you-care-b947db2b4cc6?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b947db2b4cc6</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-finops]]></category>
            <category><![CDATA[gcp]]></category>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Fri, 01 Aug 2025 04:50:39 GMT</pubDate>
            <atom:updated>2025-08-01T04:50:39.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K-K5zWT5ejtzCXNT" /></figure><blockquote><em>“You can’t manage what you can’t see.” Peter Drucker</em></blockquote><p>That’s the heart of FinOps : bringing visibility and accountability to cloud spend so teams can make faster, smarter, and more cost-aware decisions.</p><p>FinOps, short for Cloud Financial Operations , is the practice of managing cloud spending across engineering, finance, and product teams. It’s not just about saving money. It’s about:</p><ul><li>Making informed trade-offs between speed, cost, and quality.</li><li>Creating shared accountability for cloud usage.</li><li>Turning cloud bills from surprises into strategic levers.</li></ul><p>In other words: FinOps helps you use the cloud like a grown-up.</p><p>Why FinOps Matters (and Who It’s For)</p><p>It’s not just for finance teams here’s how it lands across roles:</p><ul><li>Engineers see the real cost impact of their architecture and deployments.</li><li>Finance gets clarity into where spend is going down to the service, team, or feature.</li><li>Product &amp; Ops can make trade-off decisions in real time instead of waiting for end-of-month surprises.</li></ul><p>💸 Example 1: “Zombie” Resources</p><p>A fast-moving dev team spun up dozens of test environments in AWS. No one shut them down. Cost: $18,000/month in idle resources caught months later by accident.</p><p>FinOps Fix: Tagging + automated lifecycle policies + budget alerts. Result: 80% cost reduction on non-prod.</p><p>🧾 Example 2: Misaligned Commitments</p><p>The finance team bought 3-year Reserved Instances to “lock in savings.” The dev team migrated to containers 6 months later. Result: Unused reservations, wasted spend.</p><p>FinOps Fix: Collaborative forecasting + shared dashboards + gradual commitment strategies. Result: Real savings that actually stick.</p><p>🚀 Example 3: Scaling Without Overspending</p><p>A SaaS startup used auto-scaling on AWS but didn’t set max thresholds or right-size instances. A viral launch cost them 4x their usual monthly spend.</p><p>FinOps Fix: Right-sizing tools + cost-aware deployment patterns. Result: Controlled scaling + predictable spend.</p><p>What to Expect from This Series</p><p>Over the next 99 days, I’ll break down:</p><ul><li>🛠 Open source + commercial tools (Kubecost, Infracost, Apptio, and more)</li><li>☁️ Cloud-specific tips (AWS, Azure, GCP, Kubernetes, etc.)</li><li>🔄 Process and culture shifts that actually work</li><li>📉 Real savings stories from the trenches</li></ul><p>Whether you’re just starting or already deep in the FinOps trenches, there’s something here for you.</p><p>👉 Follow the tag #100DaysOfFinOps to stay in the loop</p><p>💬 What’s one cloud cost issue you’ve seen (or caused 😅)? Drop it in the comments, I might cover it in an upcoming post.</p><p>Subscribe to the <a href="https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=6940180331832446978&amp;trk=article-ssr-frontend-pulse_little-text-block">Cloud Native Hero! Newsletter</a> for regular updates.</p><p>Join the [Observability India LinkedIn Group] ( <a href="https://www.linkedin.com/groups/9899111/?trk=article-ssr-frontend-pulse_little-text-block">https://www.linkedin.com/groups/9899111/</a> )</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/day-1-100-what-finops-why-should-you-care-swapnil-kulkarni-fmxnf"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b947db2b4cc6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What It Really Takes to Get Compliance Certifications Like SOC 2, HIPAA, ISO 27001, and Beyond]]></title>
            <link>https://publish.cloudnativehero.com/what-it-really-takes-to-get-compliance-certifications-like-soc-2-hipaa-iso-27001-and-beyond-661d44ea5c33?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/661d44ea5c33</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[soc2]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[certification]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 04:35:51 GMT</pubDate>
            <atom:updated>2025-07-31T04:35:51.158Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re building or selling software especially in B2B compliance certifications aren’t optional. They’re the price of entry. Customers expect proof that your product is secure, your systems are resilient, and their data is handled responsibly.</p><p>Here’s what it takes to achieve major certifications like <strong>SOC 2</strong>, <strong>HIPAA</strong>, <strong>ISO 27001</strong>, and other industry-recognized frameworks such as <strong>PCI DSS</strong>, <strong>FedRAMP</strong>, <strong>GDPR</strong>, <strong>CCPA</strong>, and <strong>Cyber Essentials</strong>.</p><h3>🛡️ SOC 2 (System and Organization Controls)</h3><p><strong>Who it’s for</strong>: SaaS, cloud, and tech vendors</p><p><strong>Focus</strong>: Data security, availability, processing integrity, confidentiality, and privacy</p><p><strong>What to expect</strong>:</p><ul><li>Must define and implement security controls</li><li>Evidence collected over time (Type 2 is the gold standard)</li><li>Independent audit by a licensed CPA firm</li></ul><h3>🏥 HIPAA (Health Insurance Portability and Accountability Act)</h3><p><strong>Who it’s for</strong>: Any software handling PHI (Protected Health Information)</p><p><strong>Focus</strong>: Safeguarding health data via administrative, technical, and physical safeguards</p><p><strong>What to expect</strong>:</p><ul><li>Security risk assessments</li><li>Signed BAAs with third parties</li><li>Strong access controls and encryption</li></ul><h3>🌍 ISO/IEC 27001</h3><p><strong>Who it’s for</strong>: Global software vendors, especially those working with multinational clients</p><p><strong>Focus</strong>: Creating and maintaining an Information Security Management System (ISMS)</p><p><strong>What to expect</strong>:</p><ul><li>Documented risk assessments and treatment plans</li><li>Continuous improvement loop (Plan → Do → Check → Act)</li><li>Certification from an accredited ISO body</li></ul><h3>💳 PCI DSS (Payment Card Industry Data Security Standard)</h3><p><strong>Who it’s for</strong>: Any business that stores, processes, or transmits cardholder data</p><p><strong>Focus</strong>: Payment data security</p><p><strong>What to expect</strong>:</p><ul><li>Network segmentation, data encryption, vulnerability scans</li><li>Annual audits (for larger orgs), self-assessments (for smaller ones)</li><li>Non-compliance can lead to fines and losing card processing rights</li></ul><h3>☁️ FedRAMP (Federal Risk and Authorization Management Program)</h3><p><strong>Who it’s for</strong>: Cloud vendors selling to the U.S. federal government</p><p><strong>Focus</strong>: Standardized security assessment and authorization for cloud products</p><p><strong>What to expect</strong>:</p><ul><li>Must work with a sponsoring federal agency</li><li>Third-party assessment organization (3PAO) audit required</li><li>Very high bar for documentation, incident response, and access control</li></ul><h3>🛑 GDPR (General Data Protection Regulation)</h3><p><strong>Who it’s for</strong>: Any company handling EU residents’ personal data</p><p><strong>Focus</strong>: Privacy rights and data protection</p><p><strong>What to expect</strong>:</p><ul><li>Must collect consent, provide data access and deletion rights</li><li>Requires a Data Protection Officer (DPO) in some cases</li><li>Fines can reach €20M or 4% of annual global revenue</li></ul><h3>🕵️ CCPA / CPRA (California Consumer Privacy Act / Privacy Rights Act)</h3><p><strong>Who it’s for</strong>: Companies handling personal info of California residents</p><p><strong>Focus</strong>: Consumer data rights, transparency, and opt-outs</p><p><strong>What to expect</strong>:</p><ul><li>Disclose what data is collected and why</li><li>Allow users to opt out of selling personal info</li><li>Enforced by the California Privacy Protection Agency</li></ul><h3>✅ Cyber Essentials (UK)</h3><p><strong>Who it’s for</strong>: UK-based or UK-facing vendors (especially in public sector bids)</p><p><strong>Focus</strong>: Basic cybersecurity hygiene</p><p><strong>What to expect</strong>:</p><ul><li>Self-assessment or external audit of firewall, patching, malware protection, and access controls</li><li>Often required for UK government contracts</li></ul><h3>🔐 Common Across All Frameworks</h3><p>Whether it’s SOC 2, HIPAA, or PCI DSS, they all boil down to a few core practices:</p><ul><li><strong>Access control</strong>: Who gets in, what they can do, and how it’s logged</li><li><strong>Encryption</strong>: Data must be protected at rest and in transit</li><li><strong>Policies</strong>: You need to document everything from onboarding to incident response</li><li><strong>Monitoring</strong>: Set up alerting, audit trails, and review procedures</li><li><strong>Training</strong>: Employees must understand and follow your policies</li><li><strong>Proof</strong>: Screenshots, logs, tickets auditors need evidence, not promises</li></ul><h3>🛠 How to Get Started</h3><ul><li><strong>Use automation tools that</strong> can help you track controls, collect evidence, and prepare for audits.</li><li><strong>Start with what’s asked most</strong>: SOC 2 is the go-to for U.S. SaaS; ISO 27001 for global reach; HIPAA/PCI DSS for regulated verticals.</li><li><strong>Don’t fake it</strong>: Auditors know when controls exist only on paper. Build real, working systems.</li><li><strong>Assign an owner</strong>: Someone must be responsible for compliance or it won’t happen.</li></ul><h3>Bottom Line</h3><p>Compliance isn’t just a marketing badge it’s a commitment to doing things right. These frameworks help you earn trust, reduce risk, and unlock customers who care about data integrity. The sooner you bake compliance into your stack, the better positioned you’ll be for serious growth.</p><p>Subscribe to the<a href="https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=6940180331832446978"> Cloud Native Hero! Newsletter</a> for regular updates.</p><p>Join the [Observability India LinkedIn Group] (<a href="https://www.linkedin.com/groups/9899111/">https://www.linkedin.com/groups/9899111/</a>)</p><p><a href="https://www.linkedin.com/company/cloudnativehero/">LinkedIn</a> |<a href="https://twitter.com/cloudnativehero"> Twitter</a> |<a href="https://github.com/cloudnativehero"> GitHub</a> |<a href="https://cloudnativehero.github.io/"> Blog</a> |<a href="https://publish.cloudnativehero.com/"> Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=661d44ea5c33" width="1" height="1" alt=""><hr><p><a href="https://publish.cloudnativehero.com/what-it-really-takes-to-get-compliance-certifications-like-soc-2-hipaa-iso-27001-and-beyond-661d44ea5c33">What It Really Takes to Get Compliance Certifications Like SOC 2, HIPAA, ISO 27001, and Beyond</a> was originally published in <a href="https://publish.cloudnativehero.com/">Cloud Native Hero!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Native Hero Is Evolving: Now a Daily Newsletter ]]></title>
            <link>https://publish.cloudnativehero.com/cloud-native-hero-is-evolving-now-a-daily-newsletter-e12d18e24fc6?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e12d18e24fc6</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Wed, 30 Jul 2025 13:48:54 GMT</pubDate>
            <atom:updated>2025-07-30T13:48:54.081Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started writing with <a href="https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=6940180331832446978">Cloud Native Hero! Newsletter</a>, the goal was simple: cut through the noise and provide clear, valuable insights for professionals navigating the fast-changing world of cloud-native technology.</p><p>That mission hasn’t changed and to better serve our growing community, I’m excited to share that Cloud Native Hero! is now a daily newsletter.</p><h3>Why Go Daily?</h3><p>The cloud-native ecosystem doesn’t pause. Whether it’s the latest in Kubernetes, platform engineering, or the growing intersection of AI/ML and infrastructure, staying current is critical, not optional.</p><p>By publishing daily, I’ll be able to deliver faster, more focused coverage of the topics that matter most to practitioners, decision-makers, and teams building modern cloud systems.</p><h3>What You Can Expect</h3><p>Each edition will be concise, actionable, and relevant. Topics I’ll regularly cover include:</p><ul><li>Cloud Native Trends: key developments and what they mean</li><li>DevOps &amp; Platform Engineering: tools, workflows, and best practices</li><li>Security &amp; Compliance: evolving threats and practical strategies</li><li>FinOps: managing cloud costs with clarity</li><li>Observability: beyond monitoring to real insight</li><li>AI/ML in Cloud Native: practical use cases and emerging patterns</li></ul><p>I’ll also spotlight innovative open source projects, share expert perspectives, and explore how teams are scaling modern infrastructure successfully.</p><h3>Help Shape the Newsletter</h3><p>As the newsletter is evolving, I’d love your input in terms of What additional topics would you like to see covered? Please leave a comment with your suggestions.</p><p>Thank you for being part of this growing community. I’m excited for what’s ahead.</p><p>Subscribe to the <a href="https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=6940180331832446978">Cloud Native Hero! Newsletter</a> for regular updates.</p><p>Join the [Observability India LinkedIn Group] (<a href="https://www.linkedin.com/groups/9899111/">https://www.linkedin.com/groups/9899111/</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e12d18e24fc6" width="1" height="1" alt=""><hr><p><a href="https://publish.cloudnativehero.com/cloud-native-hero-is-evolving-now-a-daily-newsletter-e12d18e24fc6">Cloud Native Hero Is Evolving: Now a Daily Newsletter 🚀</a> was originally published in <a href="https://publish.cloudnativehero.com/">Cloud Native Hero!</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design for Observability]]></title>
            <link>https://cloudnativehero.medium.com/design-for-observability-3ca2830e2b50?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ca2830e2b50</guid>
            <category><![CDATA[observability]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Mon, 01 Apr 2024 11:09:46 GMT</pubDate>
            <atom:updated>2024-04-01T11:09:46.506Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design for Observability -Introduction</h3><p><strong>Observability</strong> is a fundamental concept in various fields such as engineering, computer science, and systems theory. It refers to the <strong>ability to understand the internal state of a system solely through its outputs</strong>, allowing for effective <strong>monitoring</strong>, <strong>troubleshooting</strong>, and <strong>optimization</strong>. In complex systems, especially those involving software, networks, or large-scale infrastructure, observability plays a crucial role in ensuring reliability, performance, and maintainability.</p><p>In the context of modern software development and system architecture, observability has become increasingly important as systems have grown more complex and distributed. The ability to observe and understand the behaviour of these systems in real-time is critical for ensuring their reliability, diagnosing issues, and optimizing performance.</p><p>Following are the primary components to observability platform:</p><ol><li><strong>Metrics</strong>: Metrics are quantitative measurements that provide insights into the performance, health, and behaviour of a system. These could include things like response times, error rates, CPU usage, or any other relevant data points that help us understand how the system is performing.</li><li><strong>Logs</strong>: Logs are records of events or activities that occur within a system. They provide a detailed chronological history of what has happened, including any errors or exceptions that occurred, user actions, system events, and more. Logs are invaluable for troubleshooting issues and understanding the sequence of events that led to a particular outcome.</li><li><strong>Traces</strong>: Traces are records of the flow of a specific request or transaction as it moves through a distributed system. They capture information about how the request traverses different components or services, including any network calls, database queries, or other interactions. Traces help us understand the end-to-end behaviour of a system and identify performance bottlenecks or issues with specific components.</li><li><strong>Events</strong>: Most modern distributed systems have the capability to generate events either themselves or with the help of orchestrator / cloud platform. This helps to create a trail or feed into other modules like Alerting or create custom metrics.</li><li><strong>Alerts</strong>: Monitoring all of your infrastructure in one place wouldn’t be complete without the ability to know when critical changes are occurring. Having an alerting mechanism to create the alerts and send notifications is an important part of the observability platform.</li></ol><p>To achieve observability, systems need to be properly instrumented with tools and techniques that collect and analyze metrics, logs, and traces. This often involves incorporating monitoring tools, logging frameworks, distributed tracing systems, and other observability solutions into the architecture of the system. By embracing observability principles and investing in the right tools and practices, organizations can gain valuable insights into the behaviour of their systems, enabling them to detect and diagnose issues quickly, optimize performance, and ultimately deliver better experiences for their users.</p><p>For more updates to subscribe to the <a href="https://www.linkedin.com/newsletters/6940180331832446978/">Cloud Native Hero! Newsletter</a></p><p><a href="https://www.linkedin.com/company/cloudnativehero/">LinkedIn</a> | <a href="https://twitter.com/cloudnativehero">Twitter</a> | <a href="https://github.com/cloudnativehero">GitHub</a> | <a href="https://cloudnativehero.github.io/">Blog</a> | <a href="https://meswapnilk.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ca2830e2b50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Architecture Series #5 — Application Architecture Best Practices]]></title>
            <link>https://cloudnativehero.medium.com/cloud-architecture-series-5-application-architecture-best-practices-92ecf3709483?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/92ecf3709483</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[application-architecture]]></category>
            <category><![CDATA[architecture-pattern]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Sun, 28 May 2023 11:06:30 GMT</pubDate>
            <atom:updated>2023-05-28T11:06:30.772Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Architecture Series #5 — Application Architecture Best Practices</h3><p>In the previous post <a href="https://medium.com/application-architecture-on-cloud/cloud-architecture-series-4-application-architecture-challenges-15c931e755db">Cloud Architecture Series #4 — Application Architecture Challenges</a>, we briefly looked at some of the challenges while choosing an application architecture on cloud. Today let’s have a look at some of the best practices that help you build a reliable, scalable and secure application in the cloud.</p><p>Best practices server as set of guidelines and tips for designing &amp; implementing well known, thought about mechanisms &amp; approaches for making the system more efficient and robust. The best practices are generally technology or platform agnostic. Following are some of the well known best practices in cloud application development,</p><ul><li>API based design, that is based on platform independence. It is designed and implemented based on standard protocols and well known data formats. This helps design to be technology agnostic and APIs serve as the contract that each service in the application adhere to.</li><li>Using content delivery network (CDNs) to efficiently deliver static web content to users is one of the commonly implemented best practices. With cloud service providers having dedicated managed services to support this features can be well utilized to overcome the challenges in deployment, versioning, security and resilience.</li><li>Caching, to improve performance of applications that heavily rely on stored data is another best practice to help the performance of the cloud applications.</li><li>Handling faults caused due to unavailability of underlying network or support services, creates a need for developers to have appropriate retry strategies. The important part is to avoid any anti-patterns that can be developed in the process. The usage of appropriate cloud SDKs can help in a systematic and robust approach for managing such issues with connections, operations and unavailability of dependent resources.</li><li>Use of messaging services for inter-service communication or exchange of information in an asynchronous method is an important design consideration and best practice. This involves choosing the right payload structure, encoding formats and serialization. It also works inline with the retry mechanism importance discussed in the previous point.</li><li>Autoscaling application to support allocation and deallocation of resources is an important performance requirement and is one of the key driver in running applications on the cloud. This not only helps performance but also reducing the cost of operating the cloud resources. The application development team needs to consider this during design &amp; implementation phase to take advantage of autoscaling capabilities and create notification/alerts that help trigger it.</li><li>Monitoring &amp; observability of system for its health, usage and performance is a critical requirement for application deployed on cloud. Detecting, alerting, correcting &amp; reporting the potential problems in the application deployment helps smooth operation and fulfilling some of the performance and auditing requirements. Also, it helps in the cost management of cloud resources which is a critical component in the deployment.</li></ul><p>The overall success of application deployment on cloud and its operation depends on the team capabilities and understanding of some of the best practices. Adhering to them depends on their current objectives and maturity level.</p><p>More updates to subscribe to the <a href="https://www.linkedin.com/newsletters/6940180331832446978/">Cloud Native Hero! Newsletter</a></p><p><a href="https://www.linkedin.com/company/cloudnativehero/">LinkedIn</a> | <a href="https://twitter.com/cloudnativehero">Twitter</a> | <a href="https://github.com/cloudnativehero">GitHub</a> | <a href="https://cloudnativehero.github.io/">Blog</a> | <a href="https://meswapnilk.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92ecf3709483" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Architecture Series #4 — Application Architecture Challenges]]></title>
            <link>https://cloudnativehero.medium.com/cloud-architecture-series-4-application-architecture-challenges-15c931e755db?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/15c931e755db</guid>
            <category><![CDATA[application-architecture]]></category>
            <category><![CDATA[architecture-pattern]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Sat, 27 May 2023 01:50:02 GMT</pubDate>
            <atom:updated>2023-05-27T01:50:02.123Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Architecture Series #4 — Application Architecture Challenges</h3><p>In the previous post <a href="https://medium.com/application-architecture-on-cloud/cloud-architecture-series-3-application-architecture-constraints-fb61f45f3bf9">Cloud Architecture Series #3 — Application Architecture Constraints</a> we briefly looked at some of the constraints while choosing an application architecture on cloud. Today let’s have a look at some of the known challenges while choosing an architecture pattern.</p><p>As constraints or guidelines provide us with well known characteristics and sometimes limitations of an application pattern, it also creates some challenges or trade-offs. It is important to understand these before we adapt any application architecture pattern. Here are some of the challenges,</p><ul><li>Does the complexity of the architecture pattern is justified for the application or the application domain? Will the delivery team able to handle the backlog of features? Will there be enough help to manage the dependencies?</li><li>How dependent components communicate with each other? Do we consider asynchronous communication to decouple services and increase reliability? How do we manage challenges in handling eventual consistency?</li><li>How do we manage scalability of services? Do we consider using cloud native services to address this challenge? Does it provide enough flexibility and assistance in both scale-up and scale-down events? Do we have enough information/capability to support scalability of home-grown or greenfield services?</li><li>Cloud application security is one of the most important part of application pattern. This needs to be thought about from the design phase as it can easily become one of the biggest challenge. We need to have well thought approach to ascertain &amp; implement security of the application deployed on cloud.</li><li>It may not be something we want to have but we need to consider scenarios which can lead to potential downtime of our application on cloud. Necessary measures need to be thought about and implemented to have guaranteed uptime and high performance of your cloud applications. You may want to create separate guardrails for cloud services and own managed services.</li><li>The ability to monitor the application, obtain trace information in case of failure events and provide easy update/upgrades is a one of key features we need to have as part of our application deployment on cloud.</li></ul><p>More updates to subscribe to the <a href="https://www.linkedin.com/newsletters/6940180331832446978/">Cloud Native Hero! Newsletter</a></p><p><a href="https://www.linkedin.com/company/cloudnativehero/">LinkedIn</a> | <a href="https://twitter.com/cloudnativehero">Twitter</a> | <a href="https://github.com/cloudnativehero">GitHub</a> | <a href="https://cloudnativehero.github.io/">Blog</a> | <a href="https://meswapnilk.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15c931e755db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Architecture Series #3 — Application Architecture Constraints]]></title>
            <link>https://cloudnativehero.medium.com/cloud-architecture-series-3-application-architecture-constraints-fb61f45f3bf9?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb61f45f3bf9</guid>
            <category><![CDATA[architecture-pattern]]></category>
            <category><![CDATA[application-architecture]]></category>
            <category><![CDATA[cloud-development]]></category>
            <category><![CDATA[cloud-application]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Thu, 25 May 2023 16:35:41 GMT</pubDate>
            <atom:updated>2023-05-25T16:35:41.676Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Architecture Series #3 — Application Architecture Constraints</h3><p>In the previous post <a href="https://medium.com/application-architecture-on-cloud/cloud-architecture-series-2-application-architecture-patterns-8b45b6b4f280">Cloud Architecture Series #2 — Application Architecture Patterns</a> we briefly looked at some of the patterns application architecture on cloud. Today let’s have a look at some of the known constraints and benefits of architecture patterns we discussed earlier.</p><p>Each architecture pattern is based on prior implementations that helped teams achieve their goals. This comes with a set of guidelines, that restrict teams from diverse architectural choices. Constraints also help architecture conform to a design, methodology and exert unique characteristics of the pattern.</p><p>By adherence to the constraints, the system has its own deployment methodology, way to release updates, create a roadmap for introducing new features or innovations. So it is essential that before we choose any architectural pattern for application we know the underlying design principles and constraints, else it can easily become an hurdle in getting complete advantage of using the pattern.</p><p>More updates to subscribe to the <a href="https://www.linkedin.com/newsletters/6940180331832446978/">Cloud Native Hero! Newsletter</a></p><p><a href="https://www.linkedin.com/company/cloudnativehero/">LinkedIn</a> | <a href="https://twitter.com/cloudnativehero">Twitter</a> | <a href="https://github.com/cloudnativehero">GitHub</a> | <a href="https://cloudnativehero.github.io/">Blog</a> | <a href="https://meswapnilk.medium.com/">Medium</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb61f45f3bf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Architecture Series #2 — Application Architecture Patterns]]></title>
            <link>https://cloudnativehero.medium.com/cloud-architecture-series-2-application-architecture-patterns-8b45b6b4f280?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b45b6b4f280</guid>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[architecture-pattern]]></category>
            <category><![CDATA[application-architecture]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Wed, 24 May 2023 13:39:51 GMT</pubDate>
            <atom:updated>2023-05-24T13:39:51.988Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Architecture Series #2 — Application Architecture Patterns</h3><p>In the previous post <a href="https://medium.com/application-architecture-on-cloud/cloud-architecture-series-1-application-architecture-fundamentals-30052acedbc0">Cloud Architecture Series #1 — Application Architecture Fundamentals</a> we briefly started with application architecture on cloud. Today let’s have a look at some of the well known patterns we can use based on the application architecture, service requirements and complexity.</p><p>Though architecture patterns have their own characteristics, it does not really tie to use of a particular technology. It generally provides recommendations for technologies that can be well-suited for a particular architecture.</p><p>Architecture pattern help identify the common ground for building the application as well as the guidance for post development efforts such as integration with cloud and/or third-party services, deployment considerations, operational support, customer onboarding, etc.</p><p>Some of the well known architectural patterns for designing applications on cloud are,</p><ul><li>Existing enterprise applications which have a layered stack of dependent components/services that built the complete application are generally for the N-tier application pattern. It is generally a natural fit while migrating existing applications to cloud. The highly-coupled components can help distinguish logical functions in an application but can be a challenge to manage frequent changes to the application.</li><li>Similar to enterprise applications, some of the domain specific, resource intensive applications design take advantage of messaging for communication across different components in an application. The Web-queue-worker pattern is suitable for such applications. It helps distribute the communication barrier in large enterprise applications but individual components can easily become large, monolithic silos and get challenges similar to N-tier applications.</li><li>If your application is complex and you are luxury to rearchitect it, moving to a Microservices architecture is for you. In this pattern, the application is composed of many small, independent, loosely-coupled services implementing a single business capability. This pattern is more complex to build than the previous patterns discussed and requires a mature development &amp; DevOps culture, but when done right can help with more resilient architecture.</li><li>Event-driven architecture or pub-sub model is a good pattern, when you have an applications which is built using highly distributed (in)dependent components, they generally rely on asynchronous communication and are generally data intensive.</li><li>For applications that run large batch processing tasks, work on a large data sets for analytics/reporting or are high-performance computing tasks are generally modeled after the big-data or big compute architecture pattern.</li></ul><p>Though this list can grow to accommodate any number of patterns based on use-case, it is generally recommended to understand the application design principles and constraints to use a particular pattern. It is also recommended to be pragmatic and relax on certain constraints or using mix-match approaches of known patterns than to insist on a architectural parity.</p><p>More updates to subscribe to the <a href="https://www.linkedin.com/newsletters/6940180331832446978/">Cloud Native Hero! Newsletter</a></p><p><a href="https://www.linkedin.com/company/cloudnativehero/">LinkedIn</a> | <a href="https://twitter.com/cloudnativehero">Twitter</a> | <a href="https://github.com/cloudnativehero">GitHub</a> | <a href="https://cloudnativehero.github.io/">Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b45b6b4f280" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Architecture Series #1 — Application Architecture Fundamentals]]></title>
            <link>https://cloudnativehero.medium.com/cloud-architecture-series-1-application-architecture-fundamentals-30052acedbc0?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/30052acedbc0</guid>
            <category><![CDATA[architecture-pattern]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[application-architecture]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Tue, 23 May 2023 12:57:16 GMT</pubDate>
            <atom:updated>2023-05-23T12:57:16.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cloud Architecture Series #1 — Application Architecture Fundamentals</h3><p>Writing applications compatible to the cloud is not new. This has moved considerably well in last 10–15 years. With the range of cloud services being added to the catalog, their integration scenarios, applicability to customer scenarios brings a new challenge every day.</p><p>We have constantly heard about patterns like decomposition, elasticity, polyglot, async processing, etc and some of the antipatterns which can be effective based on edge cases that find the best solution to cater to performance and cost effectiveness.</p><p>In this series, I would be talking about some of the well known architecture patterns in cloud. From application development, deployment, operations, security to discussing about technology choices, design consideration, best practices, case studies, etc.</p><p>More updates to subscribe to the <a href="https://www.linkedin.com/newsletters/6940180331832446978/">Cloud Native Hero! Newsletter</a></p><p><a href="https://www.linkedin.com/company/cloudnativehero/">LinkedIn</a> | <a href="https://twitter.com/cloudnativehero">Twitter</a> | <a href="https://github.com/cloudnativehero">GitHub</a> | <a href="https://cloudnativehero.github.io/">Blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30052acedbc0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft Certified Azure Fundamentals — Getting Started]]></title>
            <link>https://cloudnativehero.medium.com/microsoft-certified-azure-fundamentals-getting-started-25156bbf5f01?source=rss-c7d21ddfb13b------2</link>
            <guid isPermaLink="false">https://medium.com/p/25156bbf5f01</guid>
            <category><![CDATA[certified]]></category>
            <category><![CDATA[fundamentals]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[az900]]></category>
            <category><![CDATA[certification]]></category>
            <dc:creator><![CDATA[Swapnil Kulkarni]]></dc:creator>
            <pubDate>Sun, 10 Jul 2022 19:30:00 GMT</pubDate>
            <atom:updated>2022-07-20T16:10:09.225Z</atom:updated>
            <content:encoded><![CDATA[<h3>Microsoft Certified Azure Fundamentals — Getting Started</h3><p><a href="https://docs.microsoft.com/en-us/learn/certifications/exams/az-900">AZ-900 Azure Fundamentals</a> exam part of the requirements for <a href="https://docs.microsoft.com/en-us/learn/certifications/azure-fundamentals/">Microsoft Certified: Azure Fundamentals</a>.</p><p>This is an opportunity to prove knowledge of cloud concepts, Azure services, Azure workloads, security and privacy in Azure, as well as Azure pricing and support. Candidates should be familiar with the general technology concepts, including concepts of networking, storage, compute, application support, and application development.</p><p>Refer to the <a href="https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE3VwUY">course outline</a> and the exam tests candidate for following set of skills</p><ul><li>Describe cloud concepts (25–30%)</li><li>Describe Azure architecture and services (35–40%)</li><li>Describe Azure management and governance (30–35%)</li></ul><p>In the following posts we will discuss in detail related to each topic related to the certification exam.</p><p>Happy Learning!</p><p><em>Originally published at </em><a href="https://cloudnativehero.github.io/Microsoft-Certified-Azure-Fundamentals-Getting-Started"><em>https://cloudnativehero.github.io</em></a><em> on July 10, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25156bbf5f01" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>