<?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 Ravindu Sachintha on Medium]]></title>
        <description><![CDATA[Stories by Ravindu Sachintha on Medium]]></description>
        <link>https://medium.com/@ravindusachintha?source=rss-dbb858205c4e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FrplTQIMBseMSY9jE_CeZg.jpeg</url>
            <title>Stories by Ravindu Sachintha on Medium</title>
            <link>https://medium.com/@ravindusachintha?source=rss-dbb858205c4e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:03:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ravindusachintha/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[Is your project commit history a mess?]]></title>
            <link>https://medium.com/@ravindusachintha/is-your-project-commit-history-a-mess-d4859e4b315c?source=rss-dbb858205c4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4859e4b315c</guid>
            <category><![CDATA[squash]]></category>
            <category><![CDATA[git-rebase]]></category>
            <category><![CDATA[commit]]></category>
            <category><![CDATA[git-history]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Ravindu Sachintha]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 09:40:46 GMT</pubDate>
            <atom:updated>2020-09-01T09:40:46.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*azxbeMZ5Aw-an3KO" /><figcaption>Photo by <a href="https://unsplash.com/@yancymin?utm_source=medium&amp;utm_medium=referral">Yancy Min</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>Git is a wonderful tool for version controlling without a doubt. But we are not so wonderful people to handle it properly, clearly, and beautifully.</blockquote><p>When there is a bug, we make it fix and commit as “X bug is fixed”. Then after we push it to GitHub/GitLab(or somewhere you prefer), we get to know that due to that changes another bug has occurred. Then again we fix that one too and commit it as “X changes are updated for fixing Y bug”. And this way, we start an endless long journey for each of our projects.</p><p>After some time, when we look back on the things we have gone through so far (git commit history/logs), usually, we are disappointing. We feel that we can make it more beautiful if we can combine some useless things (commits) to make a single useful-one. So here, I try to tell you a way to do it.</p><h4>Basically it is rebasing and squashing…</h4><p>Before doing much, let&#39;s understand the rebasing is what.</p><blockquote>Rebasing is the process of moving or combining a sequence of commits to a new base commit.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*HQU3AXarjPeiLmasMrcSVQ.png" /></figure><p>As the above diagram, rebasing is changing the base of your branch from one commit to another making it appear as if you’d created your <strong>branch from a different commit</strong>. The primary reason for rebasing is to maintain a linear project history.</p><blockquote>Squashing is not a git command. It is a technique of combining multiple commits to a single one.</blockquote><p>By using rebase and squash you can easily make a clean, clear, and beautiful git commit history. Even it is an easy task, <strong>you should highly careful if you are working collaboratively with others on the project</strong>. This process might make things harder in that case. Even though the “Squash and Rebase workflow” helps make the collaboration process more efficient and a hell of a lot less painful. We are not talking about that workflow here.</p><h4>So let’s do it…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KQMgt0TokvHVcCrOA48msQ.png" /></figure><pre>git log --pretty=oneline --graph</pre><p>Let’s consider the above commit history. Our final goal is, combine all the commits after the initial commit(at the bottom) into a single commit as “X bug is fixed”.</p><p>We know that we need to combine only the top 5 commits. By default, a rebase will simply drop merge commits. So we actually need to rebase only 3 commits. So as the first step, we will execute the below command from the master branch.</p><pre>git rebase --interactive HEAD~3</pre><p>Then it will open a terminal editor(usually nano-editor) for the <strong>git-rebase-todo</strong> file. You need to change the word pick into <strong>squash</strong> or <strong>s</strong> of the list of commits except the top one. In that file, the commits are ordered old to new from top to bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*6u6KYaBZbIOUJn_53QQj_g.png" /></figure><p>Then save (ctrl + o) and exit (ctrl + x). Then, there will open another file named as <strong>COMMIT_EDITMSG</strong>. In this file, we are going to add the commit message for the combined commit. Usually, I delete all the things in that file except the commit message for picked commit in the last step. If you want, you can change it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*GmUZwlIoz_DMDOsw76_7ug.png" /></figure><p>Again save and close the file. That’s it. Now you have successfully rebased and squashed your project local git history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*KRGrajTZ_JXMfPSG29KtLQ.png" /></figure><p>But there is a thing. If you check the git status, you will see that it says your branch and the remote branch have diverged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*899i1r09PZa8s5hEGWK5KQ.png" /></figure><p>This is normal. You have completely rewrite your local git master branch. Still, nothing changed on the remote master branch. So they have diverged. Now we need to push these changes to the remote master branch. Before doing that, you shouldn’t make a <strong>git pull</strong>. At this point, by executing a git pull command with the rebase option, you can revert all the changes so far we did (if something goes wrong, do it before pushing to the remote master branch).</p><p>For pushing the rebase related changes, you will have to use some force.</p><pre>git push --force-with-lease origin master</pre><p>Now, everything is okay. You have a clear, clean, and beautiful commit history. To keep it that way, I encourage you to use the “Squash and Rebase workflow”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*RMWrlqOGJW2WICkkKXXeFg.png" /><figcaption>Github commit history and network</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4859e4b315c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript, please call me back ☎️  - for a better understanding]]></title>
            <link>https://medium.com/@ravindusachintha/javascript-please-call-me-back-%EF%B8%8F-for-a-better-understanding-29550aaae97a?source=rss-dbb858205c4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/29550aaae97a</guid>
            <category><![CDATA[iranvsusa]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[callback]]></category>
            <dc:creator><![CDATA[Ravindu Sachintha]]></dc:creator>
            <pubDate>Thu, 09 Jan 2020 05:23:24 GMT</pubDate>
            <atom:updated>2020-01-09T09:29:49.301Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TabxVFaAlzZITouQZ49W_w.jpeg" /><figcaption>image by <a href="https://medium.com/@ankitkamboj18"><strong>Ankit Kamboj</strong></a></figcaption></figure><p>You know that JavaScript is a wonderful language. You may be an expert of it or may be a novice. However, you should definitely heard about the wonder of JavaScript, the <strong>Asynchronous Functions.</strong> 😍</p><p>To easily understand something, it’s good to map theories with real world scenarios. Now let’s try that one. 😇</p><p>As our scenario , let’s take the hottest topic these days which is WW3. We can consider a real world action as a JavaScript function. So … 🙊🙈</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*Z1winNbq1E7JafgSWe8qrA.jpeg" /><figcaption>image by <a href="https://theweek.com/cartoons"><strong>THE WEEK</strong></a></figcaption></figure><pre>function trumpsAction() {<br>  console.log(“Trump killed Iranian military general.”);<br>  console.log(“Trump took the first step for WW3.\n”);<br>}</pre><pre>function iraniansAction() {<br>  console.log(“Iranians attacked US military bases on Iraq.”);<br>  console.log(“Iranians are on fire.\n”);<br>}</pre><p>Now we have 2 functions. Let’s try to run them as the way below.</p><pre>trumpsAction();<br>iraniansAction();</pre><p>What would be the output do you think? 🤔</p><pre><strong>Output :</strong><br>Trump killed Iranian military general.<br>Trump took the first step for WW3.</pre><pre>Iranians attacked US military bases on Iraq.<br>Iranians are on fire.</pre><p>You know the history. But these military scenes take some times. So let’s change our functions as below and run it again to see the output.</p><pre>function trumpsAction() {<br>  setTimeout(function() {<br>    console.log(“US forces take some time to prepare for a war.”);<br>    console.log(“Trump killed Iranian military general.”);<br>    console.log(“Trump took the first step for WW3.\n”);<br>  }, 3000);<br>}</pre><pre>function iraniansAction() {<br>  setTimeout(function() {<br>    console.log(“Iran forces take some time to prepare for a war. But they are more faster than US.”);<br>    console.log(“Iranians attacked US military bases on Iraq.”);<br>    console.log(“Iranians are on fire.\n”);<br>  }, 1000);<br>}</pre><pre>trumpsAction();<br>iraniansAction();</pre><pre><strong>Output :<br></strong>Iran forces take some time to prepare for a war. But they are more faster than US.<br>Iranians attacked US military bases on Iraq.<br>Iranians are on fire.</pre><pre>US forces take some time to prepare for a war.<br>Trump killed Iranian military general.<br>Trump took the first step for WW3.</pre><p>Even we called the functions in correct order, the story was completely changed. It’s because the asynchronous way of JavaScript. It tried to execute “trumpsAction” at first. But it took some times. So JavaScript didn’t wait. It executed the “iranianAction” too and Iran was more faster than the US. 😜</p><p>But do we need to happen it in this way? Can we change the history? Definitely we can’t. So JavaScript comes to save us with a golden gift, the <strong>Callback Functions.</strong></p><p>Callback is something like return method. But it’s not exactly the same and the way of using it completely different. In TypeScript you will find something called “Promises” which is more similar to this. Let’s map the callback to above scenario to rescue the history. 😇</p><p>To make things correct, what we need to be happen? It should be execute “trumpsAction” before the “iranianAction” all the time.</p><pre>function trumpsAction(<strong>callback</strong>) {<br>  setTimeout(function() {<br>    console.log(“US forces take some time to prepare for a war.”);<br>    console.log(“Trump killed Iranian military general.”);<br>    console.log(“Trump took the first step for WW3.\n”);<br>    <strong>callback()</strong>;<br>  }, 3000);<br>}</pre><pre>function iraniansAction() {<br>  setTimeout(function() {<br>    console.log(“Iran forces take some time to prepare for a war. But they are more faster than US.”);<br>    console.log(“Iranians attacked US military bases on Iraq.”);<br>    console.log(“Iranians are on fire.\n”);<br>  }, 1000);<br>}</pre><pre>trumpsAction(<strong>function() {<br>  </strong>iraniansAction();<strong><br>}</strong>);</pre><pre><strong>Output :<br></strong>US forces take some time to prepare for a war.<br>Trump killed Iranian military general.<br>Trump took the first step for WW3.</pre><pre>Iran forces take some time to prepare for a war. But they are more faster than US.<br>Iranians attacked US military bases on Iraq.<br>Iranians are on fire.</pre><p>“callback” is not a function. It’s just a value/variable. “callback()” is the function which will return that value. If you want, you can pass a value/variable in between brackets to return after “trumpsAction” finished. (In our case, we did return nothing.) The amazing thing is, we get that at the place of calling to that function like above. Not only that, if we wish, we also can change the function calling part as below.</p><pre>trumpsAction(iraniansAction);</pre><p>Remember, the callback is not a function. So we cannot call the second function as “iraniansAction()”.</p><p>Callback is a simple concept. But very powerful. You can make things happen in-order inside the JavaScript using it. This is called as <strong>“Synchronization”</strong>. JavaScript is a synchronous language. But some times, there are some functions and situations which will work asynchronous way. In here, we re-synchronized a that kind of asynchronous situation. 😃</p><p>Hope you got something from this. Keep touch on my stories and make some appreciation. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29550aaae97a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A trick to develop huge resource consuming applications with a less powerful PC]]></title>
            <link>https://medium.com/@ravindusachintha/a-trick-to-develop-huge-resource-consuming-applications-with-a-less-powerful-pc-47f24e3209b1?source=rss-dbb858205c4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/47f24e3209b1</guid>
            <category><![CDATA[tricks]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[remote-server]]></category>
            <dc:creator><![CDATA[Ravindu Sachintha]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 05:42:59 GMT</pubDate>
            <atom:updated>2020-01-07T05:42:59.615Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_983d-Bikc3yyHwGX1CRvQ.png" /></figure><p>Today, many people have powerful PCs with top generation cores and high RAMs for doing their personal stuffs. This article is not for them. (Even if it is, reading make you perfect 😉) Still there are some developers like me who have to used less powerful PCs for huge resource consuming application development such as multiple angular projects at same time.</p><p>The trick is very simple. So I will briefly explain it here. After that, for further understanding, I will guide you to setup the development environment for a angular project using that trick.</p><ol><li>Setup a virtual machine(server) with the required resource requirements for the development.</li><li>Create a new system user with ssh key pairs and store relevant key in a PEM file locally.</li><li>Install docker and docker-compose to the server.</li><li>Install required development applications/tools to the server such as node, npm, etc.</li><li>Install VS-code editor to the local machine. Then install <strong>Remote-SSH</strong> plugin to VS-code.</li><li>Ta-dah 👐 👐… Now you have everything you need. You can initialize the project in the server, connect to it via VS-code, start dev-server using docker, open the relevant IP address from a browser to view it and finally make code changes from VS-code. Then you will see the updated result on your browser.</li></ol><p>No need to run any heavy application in your PC. You just need the VS-code with Remote-SSH plugin and a good internet connection.</p><p>Now let’s dive to deep with a sample project of Angular.</p><h3>1. Setup a virtual machine (server)</h3><p>This is not free. But as a developer, you have to work with servers. There are many providers ( Ex:- <a href="https://aws.amazon.com/">AWS</a>, <a href="https://cloud.google.com/">GCP</a>, <a href="https://www.digitalocean.com/">Digital Ocean</a> ) who provide web services such as virtual machines. You can setup a server according to your requirements.</p><p>If you are doing the project for a company or a university, you can reimburse the cost for server by them. Otherwise, many of web service providers also provide free tiers and you can use that for your project development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WzyjBOhprakH5VSh" /><figcaption>Photo by <a href="https://unsplash.com/@aligns?utm_source=medium&amp;utm_medium=referral">Jordan Harrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For this sample, I used AWS with free-tier. I created a EC2 instance of <strong>Ubuntu 18.04 </strong>and ran the apt-update and apt-upgrade commands on it.</p><h3>2. Create a new system user with ssh key pairs</h3><p><a href="https://letswp.io/remote-development-visual-studio-code-amazon-ec2/">Remote Development with Visual Studio Code on Amazon EC2 - Let&#39;s WP</a></p><p>Above tutorial provide a better explanation of how to create a user and connect it to VS-code. In here, we consider only first part. Follow the tutorial to create a new system user with SSH key pair.</p><h3>3. Install docker and docker-compose</h3><p>After that, you should install the docker and docker-compose to your server. Below links will provide you the guidance for that.</p><ul><li><a href="https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-18-04">How To Install and Use Docker on Ubuntu 18.04 | DigitalOcean</a></li><li><a href="https://docs.docker.com/compose/install/"></a></li></ul><p>After you have successfully installed both docker and docker-compose, you should add the <strong>docker</strong> group to the newly created system user. For that execute below command.</p><p>sudo usermod -a -G docker exampleusername</p><h3>4. Install required development applications/tools</h3><p>These things are very general. You know that you have to install NodeJS, Npm and Angular CLI if you are going to develop an Angular project. You can setup your server as you need for the development by installing relevant and required tools and packages such that.</p><h3>5. Install VS-code editor and <strong>Remote-SSH</strong> plugin</h3><p>Then to connect with your project on server from your PC, you need to install VS-code and Remote-SSH plugin to your PC. That task is a piece of cake. After installing both of them, you have to change the ssh configuration file as mentioned in the tutorial in 2nd section. After that you will be able to connect to the server via VS-code and open a folder. Then you can create new files &amp; folders, copy-paste and move files &amp; folders and execute commands on server. You will feel no difference in between a project on local and a remote server.</p><h3>6. Do the Magic !!!</h3><p>Now you have connect your server with VS-code with full power of controlling. But still we have to do a little more.</p><ol><li>Create a new Angular project and open the root folder using VS-code.</li><li>Create new files in that folder called “<strong>Dockerfile” </strong>and “<strong>proxy.conf.json”</strong>.</li><li>configure your “<strong>Dockerfile” </strong>and “<strong>proxy.conf.json” </strong>files as the content of this <a href="https://gist.github.com/RavinduSachintha/ef21f2ff2f5407b42f349a2a4259f55b">link</a>.</li><li>As the “<strong>proxy.conf.json” </strong>file, your backend should be run on port 3000. You can create that application and include another “<strong>Dockerfile”</strong> to that too.</li><li>finally create a <strong>“docker-compose.yaml”</strong> file in the root folder of all the applications. In there, make each applications as service and bind them to a same network. The content of this <a href="https://gist.github.com/RavinduSachintha/ef21f2ff2f5407b42f349a2a4259f55b">link</a> will guide you.</li></ol><p>And that’s all. Now you can execute the command to up the systems. Then it will up frontend, backend and database containers. Frontend will be a dev-server. So you can change your codes by VS-code. When you go to the [server IP]:4200 from your local browser, it will show your system with hot reloading functionality. By this way you can run multiple applications at the same time without thinking about your local machine performance.</p><p>To up and down the docker containers use the below commands at the root folder which has <strong>“docker-compose.yaml”</strong> file.</p><p>docker-compose up --build -d</p><p>docker-compose down</p><p>Thank you for reading this article and hope you able to get something from this. 😃 😃 😃</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47f24e3209b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Experience as an undergraduate  at API Asia conference 2019, Sri Lanka]]></title>
            <link>https://medium.com/@ravindusachintha/the-experience-as-an-undergraduate-at-api-asia-conference-2019-sri-lanka-eeac6cea1748?source=rss-dbb858205c4e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeac6cea1748</guid>
            <category><![CDATA[api-asia]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[undergraduate]]></category>
            <category><![CDATA[experience]]></category>
            <dc:creator><![CDATA[Ravindu Sachintha]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 03:44:17 GMT</pubDate>
            <atom:updated>2019-10-07T03:44:17.565Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Experience as an undergraduate at API Asia conference 2019, Sri Lanka</h3><p>As an undergraduate student, I was able to participate to the first ever API Asia conference on 2nd Oct 2019 at Shangri-La Hotel, Colombo organized by Federation of Information Technology Industry Sri Lanka (FITIS). It was a great opportunity to me for engaging with knowledgeable, industrial people in Sri Lanka.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K9kVc0wGFXI20tzmZiatsQ.jpeg" /></figure><p>This conference helped me to gain lots of technical and non-technical knowledge about APIs, their developments and the future of APIs. I’m writing this medium story to share those knowledge with you as much as possible.</p><p>The keynote speaker was Mr. <a href="https://www.linkedin.com/in/lummitsch/">Kay Lummitsch</a> who is a passionate digital catalyst at <a href="https://www.axway.com/en">Axway</a>. In his speech, discuss about how to develop APIs for the industry, thinking in various aspects such as <strong><em>mindset</em></strong><em>, </em><strong><em>behavior &amp; communication</em></strong><em>, </em><strong><em>technology &amp; structure</em></strong> and <strong><em>culture</em></strong>. And also, when developing, it should always give more priorities to <strong><em>API, analytics, documentation</em></strong> and <strong><em>customer</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*3Irj4WbPfMfX1dnAKKxwNA.jpeg" /><figcaption>Ballerina Programming Language by WSO2</figcaption></figure><p>There was another speech, conducted by a person from WSO2. In there, discussed about composable enterprise architecture for the APIs which is considering UBER as a better example. There was mentioned two main problems in current APIs which are <strong><em>centralized integration</em></strong> and <strong><em>integration gap</em></strong> among APIs, and introduced <strong><em>“</em></strong><a href="https://v1-0.ballerina.io/"><strong><em>Ballerina</em></strong></a><strong><em>”</em></strong> programming language as a solution for them. Ballerina is a native cloud programming language for developing network distributed applications which is implemented by WSO2. One of a main feature in Ballerina is the capability of interchanging between same data types. As the example, let’s think, two different applications are considered Dog and Puppy as their data types. Ballerina is capable to make interchanges among those data types which are actually same. And also in the speech, mentioned a nearly developed technique which is called as <strong><em>“cells”</em></strong>. WSO2 <a href="https://github.com/wso2-cellery"><strong><em>cellery</em></strong></a> provide that facility to reduce the high complexity on peer-to-peer integration in large scale products.</p><p>Another technical speech was about the types of APIs (private, partner, public) and the architecture (authentication, access control, rate limiting, versioning, scalability, etc). The speaker mentioned about the uses of <a href="https://microservices.io/"><strong><em>micro-services</em></strong></a> for APIs which is helped to maintain the scalability (up or down) in better way. And also discussed about <a href="https://graphql.org/"><strong><em>GraphQL</em></strong></a> which is a query language for APIs, and it’s uses in APIs development. Other than that, in this speech briefly discussed about the drawbacks of APIs, network orchestration products, revisioning and versioning, CI/CD, micro-gateways (docker, Kubernetes).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x182oyv6I7OgW7VV0vlLHA.png" /></figure><p>The final technical speech was about the future of APIs development. In there, discussed about the drawbacks of the REST APIs in <a href="https://martinfowler.com/articles/richardsonMaturityModel.html">hypermedia control level</a>, light-weight protocols such as <a href="https://grpc.io/"><strong><em>gRPC</em></strong></a><strong><em>, </em></strong><a href="http://mqtt.org/"><strong><em>MQTT</em></strong></a><strong><em> </em></strong>and the products which used MQTT protocol for their developments. In the speech, specially mentioned that the future of APIs will not be only just send the request and get the data. It will about understanding the context of the user. For this, the <a href="https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/"><strong><em>Streaming APIs</em></strong></a> will take a major role in the future. Streaming APIs are a new approach of old event-driven architecture.</p><p>The API Asia conference showed me a new path to think, study and drive myself. I wish you will also be able to find that path by reading this story.</p><p>Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeac6cea1748" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>