<?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[FundsCorner Engineering - Medium]]></title>
        <description><![CDATA[On a mission to enable fast accessible credit to India’s Kirana Stores - Medium]]></description>
        <link>https://medium.com/fundscornertech?source=rss----41da5bd4e41---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>FundsCorner Engineering - Medium</title>
            <link>https://medium.com/fundscornertech?source=rss----41da5bd4e41---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:35:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/fundscornertech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Top best practices for architecting Cloud Native applications with confidence]]></title>
            <link>https://medium.com/fundscornertech/top-best-practices-for-architecting-cloud-native-applications-with-confidence-732baba24d1?source=rss----41da5bd4e41---4</link>
            <guid isPermaLink="false">https://medium.com/p/732baba24d1</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[jeyabalaji]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Jeyabalaji Subramanian]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 04:15:10 GMT</pubDate>
            <atom:updated>2021-08-02T11:18:19.412Z</atom:updated>
            <content:encoded><![CDATA[<h4>A summary of our experiences building Cloud Native applications across 18 months</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ALy8nZEEUhvCPtn8" /><figcaption>Photo by <a href="https://unsplash.com/@danist07?utm_source=medium&amp;utm_medium=referral">贝莉儿 NG</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>At <a href="http://www.fundscorner.com/">FundsCorner</a>, we embraced Cloud Native from day one to conceive, architect and deliver an end to end digital supply chain lending platform in record time.</p><p>Cloud Native is the answer to the software industry’s relentless search in the current decade for a set of tools and practices that makes your software easily deployable, modular, maintainable, robust, reliable, scalable, portable and observable — all at once.</p><p>This post is a detailed account of our learnings and best practices with building applications with Cloud Native architecture (and mindset).</p><p>Under the hood, a Cloud Native architecture is supported by these key architecture patterns and processes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*_7jSu3lNP7SwrEZ6yJ41MQ.png" /><figcaption>Architecture Patterns and processes that support Cloud Native, as per <a href="https://pivotal.io/">Pivotal</a>. See <a href="https://pivotal.io/cloud-native">here</a></figcaption></figure><p>Below we take a critical look at how we embraced these pillars, <strong>from the perspective of the benefits they bring in.</strong></p><h3>Agility:</h3><p>In the software world, <em>immaterial of what you do under hood</em>, agility is measured by how fast you bring in value to business through software. There are a number of question that beg answer from agility:</p><ul><li>How fast can your application respond change in Business Requirements?</li><li>Can you confidently deploy a change into production, just by pushing a commit into <a href="https://git-scm.com/">git</a>, knowing that the fix is isolated to a particular service and it would work?</li><li>And, when the fix DOES NOT work, how fast can you rollback this change without disrupting Production?</li></ul><p>For you to answer these questions with confidence, you must embrace the three pillars of Microservices, DevOps and Continuous Delivery.</p><blockquote>At FundsCorner, any software we have written ever, is a microservice.</blockquote><p>This forces us to isolate related, cohesive pieces of functionality into a logical unit; and allows us to change <strong>specific parts of the functionality with ease, without disrupting the whole product</strong>.</p><blockquote>We use <a href="https://nvie.com/posts/a-successful-git-branching-model/">Git flow</a> workflow model to isolate changes into branches and <a href="https://docs.gitlab.com/runner/">GitLab runners</a> to trigger builds when software is pushed into Git. We use <a href="https://docs.pytest.org/en/latest/">pytest</a> to write unit and module tests.</blockquote><p>This model enables us to create <strong>small and purpose driven branches</strong>, test them thoroughly and then merge into the master.</p><blockquote>Most of our services are automatically deployed onto the Cloud using <a href="https://github.com/Miserlou/Zappa">Zappa</a>. We also do use Docker to push out changes into a Docker registry, which then is pulled and rolled out based on Kubernetes deployment configuration.</blockquote><p>With the aforementioned tools, we are NOT anymore dealing directly with the infrastructure. We just modify the deployment instructions in a JSON or a YAML file (i.e. Infrastructure as Code) and the DevOps tool takes care of the rest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pKsIUpIzyMzr4s0Y" /><figcaption>Photo by <a href="https://unsplash.com/@gautamlakum?utm_source=medium&amp;utm_medium=referral">Gautam Lakum</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a> (Be agile, ship fast!)</figcaption></figure><p>Note that I had intentionally italicized “immaterial of what you do” in the opening of the section. Because, you cannot do whatever you want to do just for the sake of agility. In the long run, this practice is going to make you less and less agile, as the business requirements evolve… That brings our focus onto modularity…</p><h3>Modularity:</h3><p>Modularity measures how well the application is structured into cohesive units, <strong><em>abstracting away the complexities under the hood. </em></strong>For example, a loan management system will have to manage a lot of complexities under the hood in terms of the interest &amp; penalty computation — but still may expose a clean, user — understandable contracts to the end users &amp; other sub-systems alike.</p><p>The following are the questions that are typically answered by Modularity:</p><ul><li>Has the application been broken down into small, self sustaining &amp; cohesive pieces?</li><li>Has the functionality been sufficiently abstracted away for the end consumer (be it another service or end user) with meaningful data contracts?</li><li>How easy it is to introduce a new feature into the module with isolated impact surface? put in the other way, how <em>plastic/flexible</em> is the module?</li></ul><p>Microservices are the modern answer to the above questions. However, this approach of fine grained chopped microservices brings on challenges around <em>controlling and monitoring the overall business flow as a whole</em>.</p><p>There are patterns to solve these challenges. Peer to peer choreography and Orchestration are two predominant patterns among these.</p><p>At FundsCorner, we have developed an in-house serverless workflow manager, which orchestrates distributed microservices to fulfil a singular objective. (Side note: See <a href="https://medium.com/@jeyabalaji.subramanian/open-source-serverless-workflow-manager-dddd5801720c">here</a> for a detailed account on our approach and solution)</p><p>With the workflow manager approach, we were able to <em>standardize </em>services across multiple workflows, thus making the overall architecture more modular and extensible.</p><p>For example, we have a microservice dedicated for managing human tasks. With this service, you can configure &amp; control:</p><ul><li><em>how</em> a human is notified (SMS, Email or App Push Notification)</li><li><em>who </em>is supposed to fulfil this task (role based access control)</li><li><em>whether</em> the task is a gateway task (i.e. more than one choices possible, to enable approve / reject flows)</li></ul><p>When a new requirement for OTP based approval came in, <em>we were able to extend this service with ease</em> to fulfil this requirement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v0CDU-HrCxl1hTYQ" /><figcaption>Photo by <a href="https://unsplash.com/@dreamevile?utm_source=medium&amp;utm_medium=referral">Raphael Koh</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a>(Be modular, Ship with confidence!)</figcaption></figure><h3>Portability:</h3><p>A portable software is <strong>agnostic to the environment under which it is deployed</strong>.</p><p>A few questions that are <em>important &amp; relevant for portability:</em></p><ul><li>How easy it is to deploy your software onto a different Cloud Provider?</li><li>Have you made database as a <em>detachable service</em>? How easy it is to point your microservices to a different instance of a database?</li><li>What about secrets? Is there a <em>central, secure repository from </em>where your secrets are being served? Or are they attached to the environment? (which in turns brings down the portability quotient)?</li></ul><p><a href="https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/">Kubernetes</a> is a portable, extensible, open-source platform for managing containerized workloads and services, that facilitates both declarative configuration and automation.</p><blockquote>At FundsCorner, almost all of our services are deployed on the cloud, either as a serverless function on <a href="https://aws.amazon.com/lambda/">AWS Lambda</a> (or) as containers in Kubernetes.</blockquote><blockquote>We use <a href="https://aws.amazon.com/secrets-manager/">AWS Secrets Manager</a> to <strong>secure and audit our secrets centrally</strong>. You may want to look at other alternatives such as <a href="https://www.vaultproject.io/?ref=stackshare">Vault</a> to manage secrets <strong>centrally and on cloud.</strong></blockquote><p>Conforming to <a href="https://12factor.net/backing-services">12 factor apps</a>, we treat backing services as attached resources. I.e. the database is just a URL which can easily be changed at run time at a Centralized Secrets Manager, <strong><em>without modifying any source code.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6l7SxiYHCjvOpFys" /><figcaption>Photo by <a href="https://unsplash.com/@frankiefoto?utm_source=medium&amp;utm_medium=referral">frank mckenna</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a> (Be portable, Ship with ease!)</figcaption></figure><h3><strong>Resiliency, Monitoring &amp; Exception Handling:</strong></h3><p>The inherent modular and distributed nature of cloud native applications make it all the more difficult to identify and trace issues.</p><p>There is minimal room for error. More often, there is NO box you can look into to see the logs.</p><p>Resiliency is the ability to recover from faults. So, you build an application knowing that there would be faults &amp; you <em>create services which are equipped to correct these faults.</em></p><blockquote><em>At FundsCorner, our in-house workflow manager serves as the monitoring tool for identifying failed micro services &amp; they are duly retried. The microservices </em>have also been written with the assumption<em> that they may get invoked multiple times.</em></blockquote><blockquote>We also we have a set of core integrity checkers &amp; retry agents. They ensure that the data integrity is maintained at all times.</blockquote><blockquote>We use <a href="https://sentry.io/welcome/">Sentry</a> for identifying crashes on time. We have also developed an in-house solution through <a href="https://api.slack.com/incoming-webhooks">Slack webhooks</a> to get notified of critical crashes as they occur.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JilVuJg_UHiiy40X" /><figcaption>Photo by <a href="https://unsplash.com/@yunmai?utm_source=medium&amp;utm_medium=referral">i yunmai</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a> (Build resilience into the system, intentionally)</figcaption></figure><h3>Conclusion:</h3><p>Our 18 months of building and running cloud native applications has provided us a number of benefits.</p><ul><li>Beyond the buzz, fully embracing cloud native practices has enabled us to <strong>look up to a true north for building a reliable, scalable and maintainable system</strong>.</li><li>We are more tolerant to failures because we have built or embedded controls to <strong>identify faults on time and recover to the correct state fast</strong>.</li><li>It has provided the team <strong>the joy of owning self-sufficient, cohesive services fully &amp; embrace agility</strong>.</li><li>We are addicted to <strong>building and shipping fast with Continuous Integration and DevOps tools</strong>.</li></ul><p>Hope this detailed account helps you in your journey of building great usable cloud native applications fast!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=732baba24d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fundscornertech/top-best-practices-for-architecting-cloud-native-applications-with-confidence-732baba24d1">Top best practices for architecting Cloud Native applications with confidence</a> was originally published in <a href="https://medium.com/fundscornertech">FundsCorner Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>