<?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 Nitzan Shapira on Medium]]></title>
        <description><![CDATA[Stories by Nitzan Shapira on Medium]]></description>
        <link>https://medium.com/@nitzanshapira?source=rss-943bc330228f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*cylcUCbYBufcoR5XYGsG_A.jpeg</url>
            <title>Stories by Nitzan Shapira on Medium</title>
            <link>https://medium.com/@nitzanshapira?source=rss-943bc330228f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 08:52:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nitzanshapira/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[Announcing the Epsagon Live Demo Environment]]></title>
            <link>https://medium.com/@nitzanshapira/announcing-the-epsagon-live-demo-environment-d83501e35641?source=rss-943bc330228f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d83501e35641</guid>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Nitzan Shapira]]></dc:creator>
            <pubDate>Fri, 26 Oct 2018 14:12:01 GMT</pubDate>
            <atom:updated>2018-10-26T14:14:05.312Z</atom:updated>
            <content:encoded><![CDATA[<p>by <a href="https://blog.epsagon.com/author/nitzan-shapira">Nitzan Shapira</a> October 25, 2018</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VTWUnXgmpkai1Kwg" /><figcaption>Live Demo Environment</figcaption></figure><p><strong>Our live demo environment is up and running!</strong></p><p>After many requests, we’ve decided to open today the <em>live demo environment</em> of Epsagon. It is easily accessible via this link:</p><p><a href="https://demo.epsagon.com/">https://demo.epsagon.com</a></p><p><strong>Why did we set a public demo environment?</strong></p><p>As we mentioned in our <a href="https://blog.epsagon.com/epsagon-is-launching">Epsagon launch post</a>, we are big believers in self-serve to drive the adoption and growth of serverless by developers. The live environment is a real, live application, deployed in AWS using AWS Lambda, API gateway, SNS, Kinesis, and other services and APIs. it is constantly processing requests.</p><p><strong>What can you do with this environment?</strong></p><p>Everything! Except for monitoring your own application. You can watch how Epsagon works for our demo application, including statistics, visualization, distributed tracing, cost analysis, and more. <a href="https://demo.epsagon.com/">Try it now</a>!</p><p><strong>Got any requests?</strong></p><p>We’re happy to add more features to the environment — just let us know!</p><p><em>Originally published at </em><a href="https://blog.epsagon.com/announcing-the-epsagon-live-demo-environment"><em>blog.epsagon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d83501e35641" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your Startup Needs Serverless Slack Bots]]></title>
            <link>https://medium.com/hackernoon/why-your-startup-needs-serverless-slack-bots-dd02f1d9d21b?source=rss-943bc330228f------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd02f1d9d21b</guid>
            <category><![CDATA[serverless-slack-bot]]></category>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Nitzan Shapira]]></dc:creator>
            <pubDate>Mon, 24 Sep 2018 13:20:35 GMT</pubDate>
            <atom:updated>2019-05-17T04:32:56.225Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In this post, I will explain how we utilize serverless Slack bots in Epsagon, demonstrate their value, and provide an example — including corresponding open source code, using Python and Serverless Framework, to implement your custom serverless Slack bot.</em></p><p>Slack is without a doubt the most famous messaging software for startups. Startups have this unique need for speed and agility, and Slack is just perfect for that. No overhead — just pure efficiency.</p><p>One of my favorite features in Slack is its vast list of Apps and Integrations, as well as the easy way to develop custom apps, which are commonly called “<a href="https://hackernoon.com/tagged/slack-bots">Slack Bots</a>.” The point behind these apps is simple — you want all the information in a single location, and if Slack is the primary way of communication and knowledge sharing, why not stream information from other sources into it as well?</p><p>You can find many lists of recommended apps, such as <a href="https://blog.producthunt.com/20-slack-apps-you-ll-love-a295ef2c0f9c">this one</a>. I highly recommend looking for existing apps that fit your needs and add them. Built-in apps are great — but what if you need a specific, tailor-made app, which precisely meets your requirements? Luckily, the people at Slack thought of this and created an easy way to develop custom apps and integrations. Slack has excellent documentation which you can find here, and it will guide you step-by-step to build your app.</p><figure><img alt="Stack Overflow Slack bot" src="https://cdn-images-1.medium.com/proxy/1*Co918UofSnJ_SaxQBf17rQ.png" /></figure><p>Here are just some of the bots that we’re using at Epsagon. Usually, every Slack bot reports to a dedicated Slack channel.</p><ol><li><strong>GitHub</strong> (built-in): the easiest way to follow changes in code and issues.</li><li><strong>TravisCI</strong> (built-in): this continuous integration tool has a smooth Slack integration.</li><li><strong>Mention</strong> (built-in): a useful tool for tracking things around the internet, which has a ready-to-use Slack bot.</li><li><strong>RSS feeds</strong> (built-in): the AWS feed, <a href="https://hackernoon.com/tagged/google">Google</a> Alerts, and more. These can be easily added using the “/feed …” statement.</li><li><strong>Custom RSS feed</strong> (in-house): we implemented our own Google Alerts Slack bot since we wanted to improve the formatting of the built-in integration.</li><li><strong>Stack Overflow</strong> (in-house): watch and comment on Stack Overflow questions.</li><li><strong>Reddit</strong> (in-house): our way of monitoring the front page of the internet for discussions that are relevant to us.</li><li><strong>Meetup</strong> (in-house): notifications about new meetups around the world that we might be interested in.</li><li><strong>Birthday bot</strong> (built-in): because it’s fun!</li></ol><p>As you can see, we love Slack bots — both built-in and custom ones. What is the easiest way to develop a custom Slack bot?</p><figure><img alt="AWS updates Slack bot" src="https://cdn-images-1.medium.com/proxy/1*6f_WzU7mcKMtOT18_EADfQ.png" /></figure><p>To run a Slack bot, you need to run code (surprising, isn’t it?). This code sends events via the Slack API, which then publishes them to a corresponding Slack channel. What is the trigger for the bot to run? Well, it can be triggered by a user action (as happens with interactive Slack bots), but usually — it’s going to be time-based. Every 1 minute, every 1 hour, etc.</p><p>This code also needs to have some sort of a compute unite. It can run on a server, or as a serverless function.</p><p>Serverless fits the use case of Slack bots perfectly. Using a serverless compute service, such as AWS Lambda, you can deploy Slack bots in no-time, and never worry about them again!</p><p>I will demonstrate the Reddit Slack bot that we’ve implemented in Epsagon. It tracks submissions in subreddits that we are following.</p><figure><img alt="Reddit Slack bot" src="https://cdn-images-1.medium.com/proxy/1*1ZcIdbFsp_JISaMyth-ZyA.png" /></figure><p>This is an open source project which can be found in our <a href="https://github.com/epsagon/reddit-slackbot">GitHub</a>.I’m not going to go through the entire process of configuring Slack — you can find excellent documentation online. Instead, I’m going to focus on workarounds that we did to make things more convenient for us. Note: although this is a Reddit bot, the general ideas are the same for any scheduled serverless Slack bot. The Reddit bot can be used as a template for other bots.</p><p><strong>Slack webhook</strong>: Webhooks for Slack easily be created using <a href="https://api.slack.com/incoming-webhooks">this</a> guide.</p><p><strong>The configuration file (config.json)</strong>: The configuration contains the Slack URL, the Reddit client parameters, and the subreddits to follow. The subreddits are written in Reddit’s format. In this case, we will get notified about submissions which include the keyword “lambda” in the subreddits “programming” and “Python.”</p><figure><img alt="Reddit Slack bot configuration" src="https://cdn-images-1.medium.com/proxy/1*vp1UxMal6oXY8ISK8tGEoQ.png" /></figure><p><strong>Lambda code (main.py)</strong>: The code includes three functions.</p><ol><li>Handler — the Lambda handler, called every 60 minutes in this case.</li><li>get_submissions — retrieves new submissions using the Reddit API.</li><li>update_slack — formats the message and posts it to the Slack channel.</li></ol><figure><img alt="Reddit Slack bot AWS Lambda code" src="https://cdn-images-1.medium.com/proxy/1*k8gQaf2leY5jMqW4H_7TMg.png" /></figure><p>Notice that the handler function contains an update of the function’s configuration — specifically, the LAST_SUBMISSION environment variable. It is used to remember the time of the last submission, and to publish only new ones to Slack. <strong>This is a way to save a state in the function without setting up a database</strong>. We’ll get to it later.</p><p><strong>serverless.yml</strong>: We are big fonds of the Serverless Framework. Deploying new Lambda functions is straightforward using the framework.</p><figure><img alt="serverless.yml" src="https://cdn-images-1.medium.com/proxy/1*r5GFc_SQhXSqMT6Aof5JpQ.png" /></figure><p>The serverless.yml file includes special permission for the function — to edit its configuration (lambda:UpdateFunctionConfiguration). This permission is needed because the handler function is updating the environment variable LAST_SUBMISSION. The Resource field can be calculated using the AWS region, the account ID (which can be found using this guide), and the function’s name, taken from the service field at the top of the file.</p><p>This approach is indeed “hacky,” but it enables us to forget about setting up additional AWS resources, such as a DynamoDB. Since there is no way to save a state in a Lambda function today, this is an easy solution. While letting a Lambda function change its configuration (including its code) is a potential security risk — this function is triggered only be a scheduled timer and does not expose an external API, which minimizes the risk. However — setting one DynamoDB for all the Slack bots that you have is also a rather easy solution.</p><p>As mentioned, the project is available in our <a href="https://github.com/epsagon/reddit-slackbot">repository</a>. Also, <strong>it can be used as a template for any time-based serverless Slack bot</strong>. We have used the same template at Epsagon for creating Google Alerts bot, Stack Overflow bot, and others.</p><p>What is your experience with Slack bots? Do you have ideas for improving our Slack bot? Share your stories with us, and contribute to the project!</p><p><em>Originally published at </em><a href="http://blog.epsagon.com/why-your-startup-needs-serverless-slack-bots"><em>blog.epsagon.com</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd02f1d9d21b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/why-your-startup-needs-serverless-slack-bots-dd02f1d9d21b">Why Your Startup Needs Serverless Slack Bots</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recommended Reading for Entrepreneurs]]></title>
            <link>https://medium.com/@nitzanshapira/recommended-reading-for-entrepreneurs-3e60834af73f?source=rss-943bc330228f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e60834af73f</guid>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[readinglist]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Nitzan Shapira]]></dc:creator>
            <pubDate>Sun, 23 Sep 2018 23:53:06 GMT</pubDate>
            <atom:updated>2018-09-24T13:13:09.987Z</atom:updated>
            <content:encoded><![CDATA[<p>This is an updating list of my favorite books for tech entrepreneurs, and hopefully, it will motivate some of you to read more.</p><p>As an entrepreneur, especially a first-timer, naturally you have a lack of knowledge on different topics. If you have a technological background, you might want to learn about marketing and sales. If you were in a business-oriented position before, you might want to get familiar with the basic principals of product management.</p><p>About three years ago, I started reading books that were not for mere “fun.” These books are educational or informational on various topics. Over time, I started reading more and more and sometimes listen to some of them via audiobooks.</p><p><strong><em>A tip for reading more books</em></strong><em>: Do it when you wake up, with the morning coffee, before starting your work — I do it before even checking my phone. 10 or 15 minutes every day add up — you’ll be surprised.</em></p><p><strong><em>A word on audiobooks</em></strong><em>: “Listening” to books is the new thing, and many books have a great audio version. It can be ideal when commuting or doing sports. I listen to books during long runs.</em></p><h3>Top Choices</h3><p>My favorites.</p><h4>The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers</h4><p><em>Ben Horowitz</em></p><p>Although a relatively new book, this piece by <a href="https://twitter.com/bhorowitz?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Ben Horowitz</a> (founder of <a href="https://a16z.com/">Andreessen Horowitz</a>) is already considered a classic among many. It describes the journey of Ben as an engineer, manager, and entrepreneur, through the many challenges that he experienced as a founder of a company. In my opinion, this story is fascinating, and I mostly learned a lot from it about hiring and the importance of having the best possible team when trying to succeed in the startup journey. I listened to the audiobook which was excellent.</p><h4>Crossing the Chasm</h4><p><em>Geoffrey Moore</em></p><p>Originally published in 1991, this book is still very relevant today. It talks about marketing in high-tech industries — how to market and sell innovative products, not just to the early adopters, but to the mainstream market — which is eventually the goal of any tech startup. Succeeding in doing so is known as “crossing the chasm.” It is a book about tech marketing, and marketing on the internet correctly.</p><h4>Survival to Thrival: Building the Enterprise Startup</h4><p><em>Bob Tinker and Tae Hea Nahm</em></p><p>The go-to-market book. This one is not very familiar and was recommended to me by a friend. If you are an enterprise entrepreneur, then this book is for you. It talks about “the missing piece” — everyone talks about product-market fit, marketing, and sales — separately. This book ties all of them together in a very organized way, which makes it clear, at last, what it takes from a startup to proceed from a “survival” mode (founding and after) to a “thrival” mode — having an effective sales and marketing machine. It was co-written by a veteran entrepreneur and an experienced investor, provides many examples, and it is just great in general.</p><h3>Recommended</h3><p>Give them a shot.</p><h4>The Lean Startup</h4><p><em>Eric Ries</em></p><p>A book that became very popular, and for a good reason. Generally speaking, it is focused on product management, and specifically on lean product management, a philosophy that can be seen today in Scrum, and similar management methods.</p><h4>Zero to One</h4><p><em>Peter Thiel</em></p><p>This book by the co-founder of PayPal and one of the earliest investors in Facebook is a list of short “stories,” or principals, which talk about the importance of having a significant differentiation in to beat your competition.</p><h4>How to Get Rich</h4><p><em>Felix Dennis</em></p><p>The story of Felix Dennis, a very successful (non-tech) entrepreneur in the UK. It is very well-written and amusing and provides some fundamental ideas about entrepreneurship in general.</p><h4>Getting Things Done</h4><p><em>David Allen</em></p><p>This one is a classic about time management and efficiency. I honestly did not finish it yet, but just the first 10% provides some techniques that I implemented, and I was quite amazed by the immediate results.</p><h4>Managing Oneself</h4><p><em>Peter Drucker</em></p><p>A concise book published by the Harvard Business Review. Just read it, it’s worth it.</p><h3>Classics</h3><p>Not just for entrepreneurs.</p><h4>Rich Dad Poor Dad</h4><p><em>Robert Kiyosaki and Sharon Lechter</em></p><p>The all-time classic about money management, investing, and how to retire and avoid the “mouse race.” I highly recommend it.</p><h4>How to Win Friends and Influence People</h4><p><em>Dale Carnegie</em></p><p>This one is about human relationships and communication. How to convince someone to take your side? What’s the best way to respond in different situations? A few takeaways from this book can make a big difference in the way you communicate.</p><h3>In Progress</h3><p>I’m currently reading or listening to the following books — will update soon.</p><ul><li>Shoe Dog: A Memoir by the Creator of Nike / Phil Knight (audiobook)</li><li>The Challenger Sale: Taking Control of the Customer Conversation / Matthew Dixon</li></ul><h3>What is your favorite book?</h3><p><em>Originally published at </em><a href="https://nitzanshapira.com/my-reading-list-for-entrepreneurs/"><em>nitzanshapira.com</em></a><em> on September 23, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e60834af73f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Popular Deployment Tools for Serverless]]></title>
            <link>https://medium.com/hackernoon/the-most-popular-deployment-tools-for-serverless-2385cc3d289e?source=rss-943bc330228f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2385cc3d289e</guid>
            <category><![CDATA[serverless-deployment]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[popular-deployment-tools]]></category>
            <category><![CDATA[deployment-tool]]></category>
            <category><![CDATA[serveless-tools]]></category>
            <dc:creator><![CDATA[Nitzan Shapira]]></dc:creator>
            <pubDate>Tue, 18 Sep 2018 18:43:25 GMT</pubDate>
            <atom:updated>2019-05-17T04:32:56.673Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*68MlzzPwDOgGVADQKUTobw.jpeg" /></figure><p>When starting to write software in <a href="https://hackernoon.com/tagged/serverless">serverless</a> and Function-as-a-Service, the default cloud vendor’s console is the starting point. However, once the application gains some complexity, a proper deployment tool is necessary. This post covers the most popular deployment tools for serverless.</p><h3>The Cloud Provider’s Way</h3><p>Each of the cloud vendors provides an easy way to deploy functions:</p><ul><li><strong>AWS</strong> has a <a href="https://docs.aws.amazon.com/lambda/latest/dg/vpc-ec-upload-deployment-pkg.html">CLI for deploying Lambda functions</a>, as well as two tools (SAM and Chalice) which are covered in this article.</li><li><strong>Microsoft Azure</strong> recommends using <a href="https://docs.microsoft.com/en-us/azure/azure-functions/functions-develop-vs">Visual Studio for deploying functions</a>, and it also enables doing so using the <a href="https://docs.microsoft.com/en-us/azure/azure-functions/deployment-zip-push">Azure CLI</a>.</li><li><strong>Google Cloud </strong>provides different ways of <a href="https://cloud.google.com/functions/docs/deploying/">deploying Cloud Functions</a><em>. </em>The <a href="https://cloud.google.com/sdk/gcloud/reference/functions/deploy"><em>gcloud command-line tool</em></a> is the recommended way.</li><li><strong>IBM Cloud</strong> offers the <a href="https://console.bluemix.net/docs/openwhisk/bluemix_cli.html#cloudfunctions_cli">IBM Cloud CLI</a>.</li></ul><h3>Platforms</h3><p>Serverless deployment platforms enable more than just deploying your code — their features vary from modeling the serverless application, code management, visualization, and multi-cloud support.</p><h4>AWS SAM</h4><p>SAM — <a href="https://github.com/awslabs/serverless-application-model/blob/master/HOWTO.md">Serverless Application Model</a> — is a way to describe and deploy serverless applications in a simple way. It extends the AWS CloudFormation to provide a simplified method of defining AWS Lambda functions, API Gateway, and DynamoDB tables. It supports the runtime of the Lambda functions. AWS SAM only supports applications deployed on AWS.</p><p>AWS SAM applications are described in the <a href="https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md">SAM format</a>, which is JSON or YAML and deployed using the <a href="https://github.com/awslabs/aws-sam-cli">AWS SAM CLI</a>. Get started using <a href="https://github.com/awslabs/serverless-application-model/blob/master/HOWTO.md">this guide</a>. AWS SAM also has an active <a href="https://awssamopensource.splashthat.com/">Slack channel</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*Bv61fcJwVcz8S0lhCU9aMA.png" /><figcaption><em>Describing an application using AWS SAM (source: AWS)</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*b31hiO4ynbDLRrXWEFF4aQ.png" /><figcaption><em>Deploying a function using the AWS SAM CLI (source: AWS)</em></figcaption></figure><h4>Pulumi</h4><p>Aspiring to be the “Cloud Native Infrastructure as Code” framework, <a href="https://www.pulumi.com/">Pulumi</a> aims to provide a cloud development model for serverless functions, container apps, and data infrastructure for any cloud. The <a href="https://pulumi.io/quickstart/install.html">Pulumi CLI tool</a> is the primary way of using Pulumi, and it deploys to different providers: AWS, Azure, GCP, OpenStack, as well as Kubernetes. Pulumi also created the <a href="https://pulumi.io/quickstart/cloudfx/index.html">Pulumi Cloud Framework</a>, which lets you program infrastructure and application logic, particularly suitable for serverless applications, and being cloud-agnostic. Pulumi has an <a href="https://slack.pulumi.io/">active Slack community</a>, and it is also <a href="https://github.com/pulumi">available on GitHub</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*b31hiO4ynbDLRrXWEFF4aQ.png" /><figcaption><em>Deploying and managing infrastructure using Pulumi (source: TechCrunch)</em></figcaption></figure><h4>Serverless Framework</h4><p>The Serverless Framework is an <a href="https://serverless.com/framework/">open-source tool</a> for managing and deploying serverless functions. It supports multiple <a href="https://hackernoon.com/tagged/programming">programming</a> languages and cloud providers. Earlier this year, it introduced two additional tools — <a href="https://serverless.com/event-gateway/">Event Gateway</a>, which provides an abstraction layer to easily design complex serverless applications, and <a href="https://serverless.com/dashboard/">Serverless Dashboard</a>, for better management of the application, as well as collaboration. Serverless Framework applications are written as YAML files (known as <em>serverless.yml</em>) which describe the functions, triggers, permissions, resources, and various plugins of the serverless application.</p><p>A comparison of <a href="https://serverless.com/learn/comparisons/">Serverless Framework vs. other tools</a> provides some insights into the differentiation of the framework. Serverless Framework has an active <a href="https://github.com/serverless/serverless">GitHub community</a>. Many examples to get started can be found <a href="https://github.com/serverless/examples">on the GitHub page</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UBSYyP56vp1btn3Gh5_l8A.png" /><figcaption><em>Deploying an application using Serverless Framework (source: serverless.com)</em></figcaption></figure><h4>Stackery</h4><p>Stackery’s promise is to be the best toolkit for serverless development for teams. Unlike AWS SAM and Serverless Framework, from day one Stackery introduced a dashboard for <a href="http://www.stackery.io/product/">visually designing and building</a> serverless applications. Also, it does provide a standard CLI as well, and also announced that <a href="http://www.stackery.io/blog/stackery-sam-announcement/">it is now built on AWS SAM</a>.</p><p>In addition to creating and deploying serverless applications, Stackery also provides strong collaboration tools for teams, including rollback protection, automatic build packaging, and a GitHub integration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*b31hiO4ynbDLRrXWEFF4aQ.png" /><figcaption><em>Building serverless applications visually using Stackery (source: Stackery)</em></figcaption></figure><h3>Tools</h3><p>Unlike platforms, tools are suitable for specific tasks and mostly provide automation around them.</p><h4>AWS Chalice</h4><p><a href="https://aws.amazon.com/blogs/developer/chalice-1-0-0-ga-release/">Chalice</a> is a framework by AWS for writing serverless applications in Python and allows to quickly create and deploy applications that use AWS Lambda. Chalice provides a command line tool for creating, deploying, and managing apps, integration with common AWS services, and automatic IAM policy generation. <a href="http://chalice/">Chalice is available on GitHub.</a></p><h4>Apex</h4><p><a href="http://apex.run/">Apex</a> is a framework which aims to let you easily build, deploy, and manage AWS Lambda. One of the key features of Apex is the ability to use languages that are not natively supported by AWS Lambda through the use of a Node.js shim injected into the build. In addition to building and deploying the functions, other related tools provide testing, deployment roll-backs, and log tailing. <a href="https://github.com/apex/apex">Apex is available on GitHub</a>.</p><h4>Architect</h4><p>If you are deploying AWS Lambda functions in Node.js, you should check out <a href="https://arc.codes/">Architect</a>. This framework uses a plaintext manifest to describe cloud infrastructure, including version control, fast deployment and working locally. <a href="https://github.com/arc-repos">Architect is available on GitHub</a>.</p><h4>Claudia.js</h4><p>A popular project among developers using AWS Lambda, Node.js, and API Gateway, is <a href="https://claudiajs.com/">Claudia.js</a>. It enables to deploy an AWS Lambda and API Gateway applications with a single command, using only standard NPM packages and makes it easy to manage multiple versions. <a href="https://github.com/claudiajs">Claudia.js is available on GitHub</a>.</p><h4>Sparta</h4><p>The Go programming language is becoming more and more popular, and together with the <a href="https://aws.amazon.com/blogs/compute/announcing-go-support-for-aws-lambda/">announcement of Go support for AWS Lambda</a> earlier this year, <a href="https://gosparta.io/">Sparta</a> is a framework that transforms a standard Go application into a self-deploying AWS Lambda powered service, while all configuration and infrastructure requirements are written as Go types as well. <a href="https://github.com/mweagle/Sparta">Sparta is available on GitHub</a>.</p><h4>Terraform</h4><p>The well-known Infrastructure as Code service, <a href="https://www.terraform.io/">Terraform</a> is used to manage and deploy cloud stacks across different providers. It also <a href="https://www.terraform.io/docs/providers/aws/guides/serverless-with-aws-lambda-and-api-gateway.html">provides a way to deploy serverless applications</a>, including AWS Lambda and API Gateway.</p><h4>Zappa</h4><p>Probably the most popular tool for deploying serverless web services in Python, <a href="https://www.zappa.io/">Zappa</a> enables to easily deploy web applications, usually written in Flask or Django. Zappa wraps the standard application and deploys a Lambda function to enable a serverless, scalable experience. <a href="https://github.com/Miserlou/Zappa">Zappa is available on GitHub</a>.</p><h3>Summary</h3><p>As we can see, over the past two years, many tools for deploying and managing serverless applications have emerged. Each of these tools has a different focus, but in the end, they all have a common goal — to enable developers to iterate faster in serverless, without losing their heads.</p><p>Obviously, deployment is just one part of the serverless journey. Other aspects include performance, testing, security, debugging, and monitoring. Each of these has to be resolved to to enable a fully-serverless state of mind.</p><p><em>Originally published at </em><a href="http://blog.epsagon.com/the-most-popular-deployment-tools-for-serverless"><em>blog.epsagon.com</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2385cc3d289e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/the-most-popular-deployment-tools-for-serverless-2385cc3d289e">The Most Popular Deployment Tools for Serverless</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 ways to gain serverless observability]]></title>
            <link>https://medium.com/hackernoon/five-ways-to-gain-serverless-observability-406e5cab51af?source=rss-943bc330228f------2</link>
            <guid isPermaLink="false">https://medium.com/p/406e5cab51af</guid>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Nitzan Shapira]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 22:41:01 GMT</pubDate>
            <atom:updated>2019-05-17T04:32:57.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*fNZUlBcLh5qm36mfU6Na-Q.png" /></figure><p><em>In this post, I’m covering five approaches for gaining observability in serverless (FaaS based) systems. I hope that it can help developers, system architects, and DevOps engineers make the serverless journey successful, less frustrating, and of course — enjoyable.</em></p><p><a href="https://hackernoon.com/tagged/serverless">Serverless</a> and Function-as-a-Service (FaaS) have been around for about three years now. It started with AWS Lambda, and quickly expanded into similar services provided by the leading cloud vendors — Microsoft, <a href="https://hackernoon.com/tagged/google">Google</a>, IBM, and others. However, as people started using it, serverless became much more than just FaaS. Serverless systems today involve functions, containers, managed services provided by the cloud vendor (e.g., message queues, DBs, storage), and a vast variety of SaaS APIs (e.g., Auth0, Twilio, Stripe), all interacting with one another.</p><p>Due to the nature of these functions — limited running time, low memory, and no state, developers are encouraged to utilize more and more of these managed services. As the number of functions and APIs increase, so does the complexity of serverless applications. Modern applications are highly distributed (“nano-services”) and event-driven. On top of that, the lack of access to any server, and everything being stateless, doesn’t make things easier. Observability is a central challenge when trying to resolve issues quickly and preventing system downtime, as well as understanding performance and cost implications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jDtzqOp_s2UxDQwH.png" /><figcaption><em>Serverless system are distributed and event-driven</em></figcaption></figure><p>To overcome these challenge, developers and DevOps engineers have several options today for gaining observability into their systems. Each approach has pros and cons, and naturally — its sweet spots. Since AWS is the most popular platform for serverless today, many of the examples presented here are from AWS, but they can be applied in other cloud vendors.</p><h3>1. “This is easy” — using the default cloud vendor console</h3><p>The cloud vendor’s console is the first and most direct approach to attempting to solve issues in your serverless system. AWS equips developers with <a href="https://aws.amazon.com/cloudwatch/">CloudWatch</a>, <em>“a monitoring service for AWS cloud resources and the applications you run on AWS.”</em> Anyone using AWS Lambda is well familiar with the CloudWatch console. There, you can find log groups for each of your functions, and each group contains all the logs of the function. The logs refresh asynchronously, and it can take any time from seconds to minutes for the logs to update.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zneH5GHlx7QgUjge.png" /><figcaption><em>The CloudWatch console</em></figcaption></figure><p>Since most developers feel comfortable writing logs, it’s pretty straightforward to use. Just run your function, and take a look at the log. However, when things become a bit more complicated, i.e., in a distributed system with multiple functions, queues, triggers, and more, it can be quite challenging to understand the whole picture and connect all the different log items. Imagine a chain of 5 Lambda functions with triggers in between — not to mention the times you don’t remember to log everything. Azure and Google have a similar solution for logging from their FaaS services. The default console is great to start with, and indeed cannot be ignored. However, when crossing the 5 or 10 functions range, most teams quickly discover challenges in understanding their systems, and some even refer to it has “log hell.” Let’s explore some alternatives.</p><h3>2. “Let’s go somewhere else!” — log streaming to an external service</h3><p>When your serverless architecture evolves, and you’re going through logs, more logs, and some more logs, something suddenly doesn’t feel right. It shouldn’t be this way — should it? You’re spending all your time going through endless lists of lines, written from functions which run millions of times every day. It’s not practical, and it just doesn’t work anymore. Even if you found the correct error in the log, going backward and doing root-cause-analysis is nearly impossible.</p><p>What has been going on in all the message queues? Perhaps an external API is slowing your system down and causing your cloud bill to spike? There must be a better solution — right?</p><p>You probably heard about log aggregation platforms, such as Splunk, Loggly, and others. Some of them are great — they even automatically detect anomalies for you! In that case, why not stream all of your logs into such a service, and then quickly and easily search and filter everything there? No more manual log scrubbing? Hurray!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b_vcwuPfXzc3Z7vA.png" /><figcaption><em>Log aggregation platforms (source: Loggly)</em></figcaption></figure><p>Yan Cui describes some of these methods in <a href="https://theburningmonk.com/2018/04/serverless-observability-what-can-you-use-out-of-the-box/">one</a> of his many excellent blog posts. It’s relatively easy to stream logs into any existing log aggregation service. So, now, you can quickly do all the queries and searches that you’ve always wanted to do there. When a function fails, you can find the corresponding log, and search for the logs of other functions as well.</p><p>However — is this really what you wanted? You still have to log everything manually, and you still don’t get to the bottom of the <strong>asynchronous nature</strong> of the system. Where are all the triggers and events? How are they connected? Also, these log aggregation tools do not come cheap.</p><p>It’s time to think about a more appropriate solution — a distributed tracing solution.</p><h3>3. “I want more” — advanced observability layer provided by the cloud vendor</h3><p>Luckily, AWS and the other cloud vendors do not come empty-handed (I’m going to focus on AWS in this part). AWS proposes <a href="https://aws.amazon.com/xray/">X-Ray</a>, which <em>“makes it easy for developers to analyze the behavior of their production, distributed applications with end-to-end tracing capabilities.”</em> AWS X-Ray is a great tool which allows you to trace and instrument your code to gain extra visibility into what’s going on. It also enables you to profile different parts of your code and identify slow spots, or slow AWS APIs, such as DynamoDB, SQS, and others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L-Qc61AYGwYOwf1P.png" /><figcaption><em>AWS X-Ray (source: AWS)</em></figcaption></figure><p>We’ve given X-Ray a run in several distributed serverless applications and found out that it can indeed provide much value when it comes to an understanding of what slows down your Lambda. The automatic integration and the instrumentation of the Lambda function can help in spotting issues, triggers, and slow APIs. X-Ray does not connect asynchronous events yet, such as a Lambda publishing a message into SNS, which triggers another Lambda. Therefore, it can be challenging to troubleshoot complex issues with X-Ray. Also, many of X-Ray’s cool stuff doesn’t happen automatically but requires the developer to insert traces manually. Finally, serverless architectures are dynamic, always evolving, and connect with multiple external 3rd party services. This is a perfect opportunity for companies to leverage advanced AI to anticipate any issues that could occur in such a dynamic environment. If built-in tools like X-Ray are not enough, you will probably consider the next step.</p><h3>4. “Leave me alone” — implement a tracing solution yourself</h3><p>Sometimes, the existing tools are just not enough. You have a complex, distributed system, with tens or hundreds of functions. At the end of the day, you want to be able to answer questions such as: “is everything working properly?”, “what slows down my system?”, and also, when something goes wrong — “why did it break?” and “what’s the fastest way to fix it?”.</p><p>Since you’re a talented developer, and you didn’t manage to find a satisfying solution, you decide to implement one yourself. This fascinating <a href="https://theburningmonk.com/2017/09/capture-and-forward-correlation-ids-through-different-lambda-event-sources/">blog post</a> suggests ways for capturing and forwarding correlation IDs between functions, which can be an inspiration to such tracing technology.</p><p>Using similar methods you might be able to trace an asynchronous event through your system! Beautiful, isn’t it? Now you need to take this nice tracing tech, expand it a little to all the different cloud vendor services and the external APIs that you’re using, implement a back-end to analyze all the events, have a nice UI to show it, add some alerts, of course, so you’ll know when something breaks… If you’ve reached this far, think twice. You are about to enter a fascinating world of distributed tracing, and unless this is the business of your company (for some of us, this is the case), you are going to spend A LOT of time on this — and it’s probably never going to be enough. The one thing you should think about is — how do you want to spend your time? Utilizing serverless to its last and expand your business, or holding all the Lambda functions very tight all day long to make sure everything doesn’t collapse? There must be something out there!</p><h3>5. “Help me, Google!” — search for a dedicated solution</h3><p>You’ve come this far. You’re asking for help. Eventually, you don’t want to develop an observability solution for serverless yourself, just like you didn’t want to implement the AWS Lambda yourself. Utilize managed services — this is the mantra that you chose to follow. Today, there are several products which can help you understand what’s going on in your serverless system. Most of them focus solely on AWS, as it is still holds a significant share of the market, although Microsoft, Google, and IBM are quickly progressing toward it. The core question that you need to ask yourself when choosing such a solution is, “will this product solve the most difficult challenges in my distributed system?” Again — since modern, microservices-based systems are inherently distributed, it can be tough to solve issues quickly when just observing every service, or every function, separately. The variety of triggers, events, services, and APIs that you’re using can make a small problem huge. These asynchronous events are sneaky!</p><p>When choosing an observability solution for your serverless system, I would recommend considering the following things into consideration:</p><ul><li>Is this solution going to help me pinpoint the issues in my system quickly?</li><li>Can I get an overview of <strong>everything</strong> that’s going on, not just my code? (APIs, managed services, etc.)</li><li>Will it be enough for me, or will I have to go back to the cloud vendor’s console to get more information?</li></ul><p>At <a href="https://epsagon.com/">Epsagon</a>, we love distributed tracing. This is why we’ve researched and developed a visualization and end to end observability technology, dedicated to modern, serverless systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/0*XCGdlg9-iGuUAV2P.png" /><figcaption><em>End to end transaction in Epsagon</em></figcaption></figure><p>There are many great solutions out there, and make sure to give them a shot before going back to the old “log and search” approach. Serverless is a new software paradigm, and it requires new approaches for observability and monitoring. The world is moving fast — don’t let it get away!</p><p>AWS Serverless AWS Lambda Observability Monitoring Performance Distributed Systems Distributed Tracing Serverless Monitoring Lambda Monitoring</p><p><em>Originally published at </em><a href="https://blog.epsagon.com/five-ways-to-gain-serverless-observability"><em>epsagon.com</em></a><em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=406e5cab51af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/five-ways-to-gain-serverless-observability-406e5cab51af">5 ways to gain serverless observability</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>