<?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 Rahul Xavier Singh on Medium]]></title>
        <description><![CDATA[Stories by Rahul Xavier Singh on Medium]]></description>
        <link>https://medium.com/@xingh?source=rss-73aa8c5e47e0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AiYcUaVoA8Pu8HwO2xTd4w.png</url>
            <title>Stories by Rahul Xavier Singh on Medium</title>
            <link>https://medium.com/@xingh?source=rss-73aa8c5e47e0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:34:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@xingh/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[Transforming to Serverless Managed Architecture]]></title>
            <link>https://medium.com/vorto/transforming-to-serverless-managed-architecture-cde5a5710e6e?source=rss-73aa8c5e47e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/cde5a5710e6e</guid>
            <category><![CDATA[cassandra]]></category>
            <category><![CDATA[zeit]]></category>
            <category><![CDATA[digitalocean]]></category>
            <category><![CDATA[datastax]]></category>
            <category><![CDATA[netlify]]></category>
            <dc:creator><![CDATA[Rahul Xavier Singh]]></dc:creator>
            <pubDate>Mon, 20 Apr 2020 17:35:02 GMT</pubDate>
            <atom:updated>2020-04-20T17:35:02.140Z</atom:updated>
            <content:encoded><![CDATA[<p>Our team at <a href="https://www.anant.us/">Anant </a>has been working on migrating our leaves.api which is powered by docker containers running Python, Node &amp; PHP based applications against a managed <a href="https://www.mysql.com/">MySQL</a> Database. So far this application has worked well. It has powered our internal knowledge base as well as some of our public knowledge bases published on <a href="https://cassandra.link/">Cassandra.Link</a> and <a href="https://www.cassandra.tools/">Cassandra.Tools</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_GEF-U9VjBeflgGjTeoyQQ.png" /><figcaption>Rough Architecture of Leaves</figcaption></figure><p>Currently we are in the midst of a transformation to make everything “serverless” because we don’t want to waste our precious time managing servers, containers, etc. We love working with these things but it’s time now that we move on. We’ll continue developing on them locally, but when it comes to managing applications that are being used by people and need to be up and running all the time, we don’t have the time of day to be monitoring servers. We do that for clients that pay us. :)</p><p><strong>Our current state / architecture is a combination of self-managed containers on self-managed hosts with some managed data services.</strong></p><p>Interface / UI</p><ul><li>AngularJS (old one) (containerized)</li><li>React on Next (containerized)</li></ul><p>Software / API</p><ul><li>Python / Flask API (containerized)</li><li>Node / Express API (containerized)</li><li>nginx / reverse proxy (containerized)</li></ul><p>Database / Index</p><ul><li>MariaDB (containerized)</li><li>Apache Cassandra 3.11 (containerized)</li><li>Managed Solr on <a href="https://www.searchstax.com/">SearchStax</a></li></ul><p>Systems / Infrastructure</p><ul><li>Self-Managed Terraform / Ansible / Docker</li><li>Self-Managed Ubuntu <a href="http://www.digitalocean.com/">DigitalOcean</a></li></ul><p><strong>Our next ideal state / architecture will not have any servers whatsoever for us to manage. The only dependencies left to transition is our APIs and our data store.</strong></p><p>Interface / UI</p><ul><li>Serverless Reverse Proxy (to be determined)</li><li>AngularJS (old one) on Netlify</li><li>React on Next (containerized) on Zeit</li></ul><p>Software / API</p><ul><li>Python / Flask API on Zeit</li><li>Node / Express API on Zeit</li><li>Serverless Reverse Proxy on Zeit</li></ul><p>Database / Index</p><ul><li>Managed Cassandra as a Service on <a href="https://astra.datastax.com/">Datastax Astra</a></li><li>Managed Solr on <a href="https://www.searchstax.com/">SearchStax</a> (may consider other options)</li><li>Managed MySQL on <a href="http://www.digitalocean.com/">DigitalOcean</a> (will eventually phase this out)</li></ul><p>Systems / Infrastructure</p><ul><li>None</li></ul><p>The Interface / UI layer has already been ported to <a href="https://zeit.co/">Zeit </a>/ <a href="https://www.netlify.com/">Netlify </a>and we’re slowly migrating our API and Database layers. Our team has started migrating, developing, and testing on the Datastax Astra backed API.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cde5a5710e6e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vorto/transforming-to-serverless-managed-architecture-cde5a5710e6e">Transforming to Serverless Managed Architecture</a> was originally published in <a href="https://medium.com/vorto">vorto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Platforms and APIs]]></title>
            <link>https://medium.com/vorto/business-platforms-and-apis-36bec16c70cc?source=rss-73aa8c5e47e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/36bec16c70cc</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[cassandra]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[platform]]></category>
            <dc:creator><![CDATA[Rahul Xavier Singh]]></dc:creator>
            <pubDate>Tue, 14 Apr 2020 16:54:51 GMT</pubDate>
            <atom:updated>2020-04-14T16:54:51.537Z</atom:updated>
            <content:encoded><![CDATA[<p>Our team has been working with various platforms over the years have seen several trends emerge in technology and business.</p><p>Number of devices that need to work with business platforms grow at an exponential rate. There are more users through growing software available on smart phones, growing skills available on home assistant devices like Alexa/ Google Home, and in general more devices that are connecting to the Internet.</p><p>The audience are a combination of people across demographics in a business social graph (customers, vendors, employees, contractors) and things across industries and use cases. Technically things aren’t an audience, but when we are talking about the performance of a business platform, things have the same data responsiveness needs as users to do their jobs. In the future these things will be robots, and maybe the term “audience” will actually be more appropriate.</p><p>Business platforms for any given firm are collections of different categories of platforms across those that impact paying customers (Customer Experience ), participating staff (Information Systems), participating devices (Internet of Things), integrated partners (Partner / API Ecosystems), and the fabric that ties them together and provides intelligence (Data &amp; Analytics Platforms).</p><p>In enterprise architecture, this is the classic “Business Silos” problem where different groups have different platforms that need to be stitched together. The first step towards efficiency is to get to a “Standardized Platform.” This could mean to choose .NET or Java, or make sure everyone is using the same coding ninja style in all their PHP or Ruby. It could also be a much bigger architecture standardization. This is ambiguous endeavor which each company tends to decide what they want to do.</p><p>Software vendors are trying to help people get to a “Standardized Platform” with solutions that vary from orchestration, devops, databases, and more than I care to list. One thing is certain, APIs are the nerve endings of the central nervous system of a business. This is how systems talk to each other. These days if a platform is being added to an existing platform, it’s a foregone conclusion that it needs an API.</p><p>One type of standardization that companies will often do is to standardize how they play to develop, deploy, and scale their APIs so that at least there is one way to communicate with all of the components. As early as 2002, nearly two decades ago, a forward thinking Jeff Bezos famously <a href="https://medium.com/slingr/what-year-did-bezos-issue-the-api-mandate-at-amazon-57f546994ca2">mandated </a>all of their business units could only <a href="https://api-university.com/blog/the-api-mandate/">integrate with APIs</a>.</p><blockquote>1) All teams will henceforth expose their data and functionality through service interfaces.</blockquote><blockquote>2) Teams must communicate with each other through these interfaces.</blockquote><blockquote>3) There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network.</blockquote><blockquote>4) It doesn’t matter what technology is used. HTTP, Corba, Pubsub, custom protocols — doesn’t matter.</blockquote><blockquote>5) All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.</blockquote><blockquote>6) Anyone who doesn’t do this will be fired.</blockquote><blockquote>— JEFF BEZOS</blockquote><p>Making APIs is an inevitable part of making new software to add to a business platform or to make a new one from scratch as a startup would. There are more ways to create APIs then there are the number of <a href="https://solarsystem.nasa.gov/moons/overview/">moons and planets in our solar system</a>.</p><p>We’ve not been religious about how to make APIs. We’ve made APIs in every major programming language and every major database that is out there. We’ve designed and built APIs in no-code, low-code, and complete frameworks coded from the ground up.</p><p>One such API that we use internally at <a href="https://anant.us/">Anant </a>powers a knowledge base that is used to publish public facing knowledge sites such as <a href="https://cassandra.link./">Cassandra.Link</a>. No, we didn’t build it on Cassandra because we wanted to pilot it internally and see if it was of use before investing more time into it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yydpQqT7-zwLw0Ne7BolhA.jpeg" /><figcaption><a href="https://cassandra.link/">Cassandra.Link</a> on 04/15/2020</figcaption></figure><p>Until we started publishing Cassandra.Link, we didn’t really have a need to make this API scalable ore make it available to other people is because only a handful of people in our team used it. It didn’t matter if the database powering it would topple (mysql), or the containers and proxies were overloaded on one machine (docker), or if the software itself couldn’t execute more threads without having to make more containers (php).</p><p>This summer we are going to be porting our API to be infinitely scalable. We’ll be sharing our journey as we migrate the data layer for our knowledge base platform to run on top of mostly server-less if not 100% completely server-less technologies. At the same time, we believe that one shouldn’t be locked into any particular platform, so we’re currently evaluating different tools that will run on any cloud.</p><p>We’re looking at using some variant of Cassandra, either Node or Python for the API layer, and some more python to help migrate data and do data operations. We’ll keep you updated as we go along.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36bec16c70cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vorto/business-platforms-and-apis-36bec16c70cc">Business Platforms and APIs</a> was originally published in <a href="https://medium.com/vorto">vorto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business in realtime. Technology of now.]]></title>
            <link>https://medium.com/vorto/business-in-realtime-technology-of-now-c1d0cb043b19?source=rss-73aa8c5e47e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1d0cb043b19</guid>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[business-platform]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[realtime]]></category>
            <dc:creator><![CDATA[Rahul Xavier Singh]]></dc:creator>
            <pubDate>Mon, 13 Apr 2020 17:04:03 GMT</pubDate>
            <atom:updated>2020-04-13T17:04:03.286Z</atom:updated>
            <content:encoded><![CDATA[<p>Today’s businesses need to look beyond what the forefathers of silicon valley saw and delivered on. They said we will have “information at your fingertips.” We’re here. What’s next?</p><p>This publication will provide business platform leaders, technical architects, data scientists, engineers, and analysts the why, the what, and the how of creating modern realtime business platforms best practices, design patterns, tools, and testimony of our own experiments in realtime.</p><p>Even though we have been using realtime technology for the last decade, we recognize that the amount of knowledge available has expanded exponentially. We’re always learning so I’m happy to share our journey with you. Join us by following us.</p><p>Rahul Singh</p><p>Cover Photo by <a href="https://unsplash.com/@jeremythomasphoto?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jeremy Thomas</a> on <a href="https://unsplash.com/s/photos/data?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1d0cb043b19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vorto/business-in-realtime-technology-of-now-c1d0cb043b19">Business in realtime. Technology of now.</a> was originally published in <a href="https://medium.com/vorto">vorto</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>