<?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 Rafael Dias on Medium]]></title>
        <description><![CDATA[Stories by Rafael Dias on Medium]]></description>
        <link>https://medium.com/@rafaeldias_66509?source=rss-7a21cbde7c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eQ2_0yUGI1YQek5PiRTXCg.jpeg</url>
            <title>Stories by Rafael Dias on Medium</title>
            <link>https://medium.com/@rafaeldias_66509?source=rss-7a21cbde7c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:54:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rafaeldias_66509/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[What Is Serverless?]]></title>
            <link>https://medium.com/@rafaeldias_66509/what-is-serverless-4096d6b3f581?source=rss-7a21cbde7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4096d6b3f581</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Rafael Dias]]></dc:creator>
            <pubDate>Tue, 05 Feb 2019 08:21:28 GMT</pubDate>
            <atom:updated>2019-02-05T08:21:28.811Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*caEsd8dPAXveLTICndguLg.png" /></figure><h3>TL;DR</h3><p>Encapsulate your code in functions and let a cloud provider run it for you. No provisioning or managing servers required.</p><h3>Introduction</h3><p>Let’s start by the name itself, it wrongly suggests that there are no more servers involved, which is definitely not true. There are a lot of servers in the “Serverless” world, but you don’t need to worry about them anymore.</p><p>A third-party cloud provider is responsible for executing your piece of code on an ephemeral environment, charging only the dynamically allocated resources used to run it.</p><p>Because it abstracts the underlying infrastructure layer and provides the access to its features through a service, Serverless can be referred to as “Backend As A Service” or “BaaS”.</p><h3>Main characteristics</h3><ul><li><strong>Stateless</strong>: Given its dynamic quality, Serverless functions are inherently stateless.</li><li><strong>Event-Oriented</strong>: Serverless is event oriented by nature. The function can be triggered by a myriad of event sources like queue services, HTTP requests, alerting mechanisms, scheduled tasks, etc.</li><li><strong>Continuous Scaling</strong>: It automatically runs in parallel, scaling continuously as the demand increases.</li><li><strong>No Server Management</strong>: The infrastructure layer is out of sight.</li></ul><h3>Providers</h3><p>There is a good amount of options in the market with different levels of maturity and runtime (environment with a specific language executer) options, but basically, all of them offers the same core features.</p><p>Here is a list of some of the main providers:</p><h3><a href="https://aws.amazon.com/lambda">Amazon AWS Lambda</a></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeOBq__h4OJ4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeOBq__h4OJ4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeOBq__h4OJ4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1bb75bccf9a10c05af683623012d5442/href">https://medium.com/media/1bb75bccf9a10c05af683623012d5442/href</a></iframe><p>The market leader, has initially launched its Serverless platform supporting just a handful of runtimes, now officially supports Node JS, Go, Java, C#, Ruby, and since November 2018 it introduced a feature called Layers, that provides the ability to run virtually any language.</p><h3><a href="https://cloud.google.com/functions">Google Cloud Serverless Computing</a></h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1r3vMYywNLk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1r3vMYywNLk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1r3vMYywNLk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/20277feba5cb38e8fb9316004a140793/href">https://medium.com/media/20277feba5cb38e8fb9316004a140793/href</a></iframe><p>The giant is also in the Serverless game but offering a much smaller range of runtimes, NodeJS, and Python (in beta).</p><h3><a href="https://azure.microsoft.com/en-us/services/functions/">Microsoft Azure Functions</a></h3><p><a href="https://channel9.msdn.com/Blogs/Azure/Azure-Functions-overview">Azure Functions overview</a></p><p>Microsoft offers middle ground in terms of runtime options. Production-ready is C#, NodeJS, F#, Java, and in experimental status are Python, Typescript, PHP, Batch, Bash, Powershell.</p><h3><a href="https://www.ibm.com/cloud/functions">IBM Cloud Functions</a></h3><p>IBM Cloud Functions is based on Apache Openwhisk an open source, distributed Serverless platform. Natively supports Node.js, Java, Python, serverside Swift, and PHP. But also allows you to use Docker containers, permitting virtually any language.</p><h3>Pros &amp; Cons</h3><h3>Pros</h3><ul><li><strong>Initial development time</strong>: To get a project up and running that is reliable and scalable is incredibly fast, especially if you choose to integrate with existing products from the chosen vendor.</li><li><strong>Operational overhead</strong>: A lot of the overhead is taken away from you with Serverless, but it does not mean that everything is done out of the box.</li><li><strong>Scalability</strong>: It is made from the ground up to provide highly scalable infrastructure for your application.</li></ul><h3>Cons</h3><ul><li><strong>Vendor lock-in</strong>: Since you rely on third parties to abstract all the underlying complexity, you end up increasing dependency. There are ways to minimize coupling but once functions get more complex, switching from one vendor to another may not be a trivial task.</li><li><strong>Hard to predict costs</strong>: You pay as you grow, but it can be difficult to plan your costs, particularly if you are starting out without hard data to base your calculations on. In any case tools such <a href="http://serverlesscalc.com/">this</a> can help a lot!</li><li><strong>Tooling</strong>: It is a fairly new paradigm, so at this stage mature tooling is still a problem to find.</li></ul><h3>Use cases</h3><p>This kind of architecture is by no means suitable for every scenario, Serverless is definitely not ideal for long-running tasks, on the other hand, everything that is event-driven or is short lived can be a good match for Serverless, for example:</p><ul><li>Chatbots</li><li>IoT</li><li>Integrating services</li><li>Microservices</li><li>Execute actions for static websites</li><li>Voice assistants</li><li>CI/CD pipelines</li></ul><h3>Case Studies</h3><h4><a href="https://www.entrepreneur.com/article/293668">How We Bootstrapped Our Startup by Skipping Half the Work</a></h4><p><strong>Company</strong>: <a href="https://www.moo.do/">Moo.do</a><br><strong>Provider</strong>: Google</p><p>Jay Meistrich co-founder and CEO of Moo.do explains how the choice of going Serverless helped him and his partner to launch their project by themselves.</p><h4><a href="https://aws.amazon.com/serverless/videos/video-lambda-coca-cola/">Coca-Cola: Running Serverless Applications with Enterprise Requirements</a></h4><p><strong>Company</strong>: <a href="https://us.coca-cola.com/en/home/">Coca-Cola</a><br><strong>Provider</strong>: AWS</p><p>A nice presentation from Patrick Brandt about the <a href="https://us.coca-cola.com/vending/">Vending Pass program</a>, the product is for rewards for buying in vending machines.</p><h4><a href="https://customers.microsoft.com/en-us/story/hotailors-travel-transportation-azure">Travel technology startup goes to market three times faster with Microsoft Azure and Node.js</a></h4><p><strong>Company</strong>: <a href="https://hotailors.com/">Hotailors</a><br><strong>Provider</strong>: Azure</p><p>The article shows how the company using Serverless reduced service integration times by 30 to 50 percent.</p><h3>Conclusion</h3><p>Serverless is not a magic solution that will solve each and every one of your infrastructure problems. That being said I need to point out that in my personal opinion it will be increasingly hard to find reasons to not use it.</p><p>It breaks a lot of the barriers that slows down changes, improvements and new projects, while still being able to offer a lot of flexibility to the developers.</p><p>This alternative differently from containers which feel like a natural step in the evolution, serverless is like a different direction that requires us to rethink a lot of the steps involved in building a modern application. It doesn’t just affect the way we handle the infrastructure but also how our code should be organized, accessed, tested…</p><p>Serverless is still fairly new but already has proven to be a valuable tool to have in your toolkit.</p><p>Article originally published in my personal blog: <a href="https://rafaelnexus.com/articles/what-is-serverless/">https://rafaelnexus.com/articles/what-is-serverless/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4096d6b3f581" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Tips For Developers CV]]></title>
            <link>https://medium.com/@rafaeldias_66509/5-tips-for-developers-cv-6cce7c4c2ee5?source=rss-7a21cbde7c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cce7c4c2ee5</guid>
            <category><![CDATA[cv]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[tips]]></category>
            <dc:creator><![CDATA[Rafael Dias]]></dc:creator>
            <pubDate>Tue, 05 Jun 2018 12:23:03 GMT</pubDate>
            <atom:updated>2018-06-05T12:23:03.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*WSSecWJAYUIYXfB4JYu7oQ.png" /></figure><p>First, let’s make one thing clear I am no expert in HR, nor I am a recruitment guru but during the years I had to interview, test and select a bunch of technical people and I’ve seen the same mistakes over and over again.</p><p>The search for developers has never been higher, so a bunch of people gets away with a terrible CV. But if you want to go the extra mile and be ahead of the game is nice to pay attention and give some love and care to your CV, some small tweaks here and there can do wonders.</p><p>These are my two cents about the subject, that’s only my personal opinion :)</p><h3>1. Tailor Your CV For The Job</h3><p>Even if you are very proud of your background as a graffiti artist, please skip this entirely if you are applying for a backend developer. Of course, you can mention your passion about street art briefly to tell a little about yourself as a final note, down there at the footer, use the main space to showcase what you are capable of.</p><p>Like if you as a full-stack engineer find a very interesting position as front-end, take some time to review and tone down the back-end side, leave it there as a note, but you need to showcase your front-end skills, in this case, the back-end is a plus, not a must.</p><h3>2. Keep It Short, And I Mean Very Short</h3><p>Ok, let’s talk about numbers if its more than 3 pages probably I won’t read it, and most of the recruiters from the places I’ve worked on agree with me on this: the bigger the CV less likely it will be read.</p><p>The goal here is the one page CV</p><p>Of course, there are exceptions if you’re someone who really achieved tons of accomplishments, well, then maybe you can go on and be a little more wordy about it.</p><p>If the recruiter needs more detail he will ask you.</p><h3>3. Avoid The Buzzword Overload</h3><p>The easier way to get people distracted while reading your CV is to drop the buzzword bomb. It might serve to impress someone who is not from tech business but usually tells that the guy is trying to stall or fill with every possible hot keyword of the moment increasing his chances to be indexed somehow.</p><p>It is not uncommon to see some guys dropping marketing jargons mixed with programming language names without any coherence or context.</p><p>This only shows how confusing and unorganized the person is.</p><h3>4. Presentation Is Important</h3><p>I know, that probably you are a numbers person and don’t want to know the best font combination or the best alignment for your CV. But it needs to be readable, and preferably not horrendous.</p><p>I will drop some hints here:</p><ul><li>2 fonts max, one for a title and one for the body text. And no, Comic Sans is not allowed.</li><li>Font size is important, make it readable.</li><li>Black &amp; dark gray are your friends.</li></ul><p>But don’t overdo, avoid tables, pictures, and unnecessary stuff, less is more, emphasize the information.</p><h3>5. Describe What YOU DID</h3><p>You came until here, now your CV is 1 page long, beautiful with no excess of acronyms but… is not saying anything.</p><p>It is very important to showcase your code, especially back-end and devops guys can be almost impossible to showcase something without a Github profile.</p><p>About your professional experience be straightforward and describe what you did, not your team, not your company.</p><blockquote><strong><em>Company X</em></strong><em> Oct/2016 — Jan/2018<br>Responsible for the integration with partner X on Marketplace team. Achieved 70% better performance on batch products creation (reduced from 1s to 300ms) on the company’s product service by applying technic X using tool Y and language W.</em></blockquote><p>Now we are talking! It says where you were, what you were responsible for and what you accomplished there!</p><p>This loosely follows the <a href="https://www.independent.co.uk/news/business/resume-cv-tips-advice-google-hr-boss-perfect-job-interview-a8029456.html">famous formula</a>: accomplished <strong>X</strong> measured by <strong>Y</strong> by crafting <strong>Z</strong>.</p><p>This text was originally published in https://rafaelnexus.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cce7c4c2ee5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>