<?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[Serverless Stories - Medium]]></title>
        <description><![CDATA[Ready to build it Serverless? Here are some of our favorite projects, walkthroughs, and pro-tips. - Medium]]></description>
        <link>https://medium.com/serverless-stories?source=rss----bfef62be8f1e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Serverless Stories - Medium</title>
            <link>https://medium.com/serverless-stories?source=rss----bfef62be8f1e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:29:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/serverless-stories" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Talking re:Invent & the Latest Serverless Framework Features in the Dec.]]></title>
            <link>https://medium.com/serverless-stories/talking-re-invent-the-latest-serverless-framework-features-in-the-dec-f45b584c34f1?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/f45b584c34f1</guid>
            <category><![CDATA[awsreinvent]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Fri, 16 Dec 2016 16:24:10 GMT</pubDate>
            <atom:updated>2016-12-16T16:23:25.262Z</atom:updated>
            <content:encoded><![CDATA[<h3>Talking re:Invent &amp; the Latest Serverless Framework Features in the Dec. 8th Office Hours Live Video Recording</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*3Scet7zB7h6cN9EBlbLklA.png" /></figure><p>Serverless Office Hours is a monthly live chat with core members of the Serverless team. In the 2nd episode of Office Hours, Developer Evangelist <a href="https://github.com/DavidWells">David Wells</a> and Core Framework Engineer <a href="https://github.com/eahefnawy">Eslam Hefnawy</a> reviewed Lambda announcements from AWS re:Invent and talked about new features in Severless Framework <a href="https://serverless.com/blog/serverless-v1.2.0/">v1.2</a> &amp; <a href="https://serverless.com/blog/serverless-v1.3.0/">v1.3</a> (now with <a href="https://serverless.com/framework/docs/providers/aws/guide/functions/#environment-variables">Environment Variables Support</a>, Yay!).</p><p><strong><em>Want to know more about the recent AWS Lambda announcements and why they matter? Check out </em></strong><a href="https://serverless.com/blog/recap-serverless-announcements-reinvent/"><strong><em>2016 AWS re:Invent Recap — Serverless Christmas came early</em></strong></a><strong><em>.</em></strong></p><p>David and Eslam also answered some questions from the community.</p><blockquote><a href="https://twitter.com/goserverless"><em>@goserverless</em></a><em> hi! Just hit Cloud Formation 200 resources limit while deploying. Any workarounds for this issue? Thanks in advance</em></blockquote><blockquote><em>— Andrés Santibáñez (@asantibanez) </em><a href="https://twitter.com/asantibanez/status/805844581313024000"><em>December 5, 2016</em></a></blockquote><p>And announced new Serverless projects, including:</p><ul><li><a href="https://github.com/serverless/examples">Serverless Examples GitHub Repo</a> — A collection of boilerplates and examples of serverless architectures built with the Serverless Framework and AWS Lambda. Add your project and share it with the world.</li><li><a href="https://github.com/serverless/plugins">Serverless Plugins GitHub Repo</a> — Serverless Plugins allow users to extend or overwrite the framework’s core functionality. Many of these plugins are contributed by our amazing community members!</li><li><a href="https://github.com/serverless/dashboard">Serverless Dashboard Project</a> — A desktop application providing a graphical user interface for the Serverless Framework, AWS Lambda, Google CloudFunctions and more.</li></ul><h3>See more details and answers to community questions in the full recording:</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIoW_IcvRTGM&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIoW_IcvRTGM&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FIoW_IcvRTGM%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e9a6ccfd4bba53ec7b845c6adcdabf02/href">https://medium.com/media/e9a6ccfd4bba53ec7b845c6adcdabf02/href</a></iframe><p>Tune in for the next edition of <strong>Serverless Office Hours, Thursday, Jan. 12, 10–11AM PST</strong>, coming to you live from our team retreat! Tweet <a href="https://twitter.com/goserverless">@goserverless</a> with your questions along with the hashtag <strong>#askServerless</strong> to join the conversation.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/serverless-office-hours-recap/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f45b584c34f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/talking-re-invent-the-latest-serverless-framework-features-in-the-dec-f45b584c34f1">Talking re:Invent &amp; the Latest Serverless Framework Features in the Dec.</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[C# service template, Alexa event support, service-wide metrics in Serverless Framework v1.4]]></title>
            <link>https://medium.com/serverless-stories/c-service-template-alexa-event-support-service-wide-metrics-in-serverless-framework-v1-4-d638b86c07a1?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/d638b86c07a1</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Fri, 16 Dec 2016 14:01:31 GMT</pubDate>
            <atom:updated>2016-12-16T14:03:18.932Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re happy to release v1.4.0 of the Serverless Framework!</p><p>This release is packed with lots of great new features. Let’s take a look at the highlights!</p><h3>Highlights of 1.4.0</h3><p>Here are the highlights of this release. You can find a complete list of all the updates in the <a href="https://github.com/serverless/serverless/blob/master/CHANGELOG.md">changelog</a>.</p><h4>Alexa event support</h4><p>v1.4 introduces a new event alexaSkill event source.</p><p>You can now hook up your Lambdas with alexaSkill events like this:</p><pre>functions:<br>  hello:<br>    handler: handler.hello<br>      events:<br>        - alexaSkill</pre><p>You can learn more about this new event source in <a href="https://serverless.com/framework/docs/providers/aws/events/alexa-skill">the docs</a>. You can also check out examples for setting up your own Alexa skill for <a href="https://github.com/serverless/examples/tree/master/aws-node-alexa-skill">Node.js</a> or <a href="https://github.com/serverless/examples/tree/master/aws-python-alexa-skill">Python</a> in the Serverless Examples Repository.</p><h4>C# service template</h4><p>AWS introduced .NET core support for Lambda at re:Invent.</p><p>Serverless has you covered and ships with the new aws-csharp template. You can use it to create C# services on AWS Lambda.</p><p>Simply run:</p><pre>serverless create --template aws-csharp</pre><p>to create a new C# service.</p><p>The <a href="https://serverless.com/framework/docs/providers/aws/examples/hello-world/csharp/">C# “hello world” example</a> will show you how you can setup and deploy your C# service.</p><p><strong>Note:</strong> Serverless supports all <a href="http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html">AWS Lambda runtimes</a> out of the box. You can change the runtime with the help of the runtime property in <a href="https://serverless.com/framework/docs/providers/aws/guide/serverless.yml/">serverless.yml file</a>.</p><h4>Directory support for service installation via GitHub URL</h4><p>The serverless install command makes it possible for you to download services based on GitHub repository URLs. The downside was that only full repositories could be downloaded.</p><p>Until now! A recent enhancement makes it possible to download specific directories from a GitHub URL.</p><p>Want to play around with the REST API example which connects to a DynamoDB?</p><p>Just install the service with the following command:</p><pre>serverless install --url https://github.com/serverless/examples/tree/master/aws-node-rest-api-with-dynamodb</pre><p><em>(Note: This is one line with no breaks)</em></p><h4>Service-wide metrics</h4><p>v1.3 introduced service metrics support allowing you to get function metrics by running:</p><pre>serverless metrics --function hello</pre><p>v1.4 enhances this command so that you can get service-wide metrics (all functions combined) when you run:</p><pre>serverless metrics</pre><h4>Stdin support for invoke</h4><p>serverless invoke and its local equivalent serverless invoke local are a great way to invoke your function to test its behavior.</p><p>v1.4 now supports <strong>stdin</strong> so that you can pipe data directly into the serverless invoke call like this:</p><pre>echo &quot;hello world!&quot; | serverless invoke --function hello --stage dev --region us-east-1</pre><p><em>(Note: This is one line with no breaks)</em></p><p>This provides way more flexibility to invoke a function with different data. Here’s an example of how a dataGenerator.js file could be used to generate data for your function:</p><pre>node dataGenerator.js | serverless invoke local --function hello</pre><h4>Enhancements, refactorings and bug fixes</h4><p>As usual we’ve also pushed a bunch of enhancements, refactorings and bug fixes (thanks for reporting!) in this release.</p><h3>Next Steps</h3><p>We’ve already started filling in the next <a href="https://github.com/serverless/serverless/milestones">milestones</a>. Check out the <a href="https://github.com/serverless/serverless/milestone/20">1.5 milestone</a> to see what you can expect in two weeks.</p><p>We hope that you have fun with the new release! Let us know if you have any questions or feedback in <a href="http://forum.serverless.com/">our Forum</a> or <a href="https://github.com/serverless/serverless/issues">GitHub Issues</a>.</p><p>The <a href="https://github.com/serverless/examples">Serverless Examples Repository</a> is an excellent resource if you want to explore some real world examples and learn more about what Serverless architectures look like.</p><h3>Using Semver</h3><p>Note that we’re using <a href="http://semver.org/">strict Semver</a> for our Serverless Framework versioning. This way you’ll know when we introduce major features or breaking changes.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/serverless-v1.4.0/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d638b86c07a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/c-service-template-alexa-event-support-service-wide-metrics-in-serverless-framework-v1-4-d638b86c07a1">C# service template, Alexa event support, service-wide metrics in Serverless Framework v1.4</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create a Fast, Secure, and Scalable Open Source Blog with React + Markdown]]></title>
            <link>https://medium.com/serverless-stories/how-to-create-a-fast-secure-and-scalable-open-source-blog-with-react-markdown-5361795c28f3?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/5361795c28f3</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Fri, 09 Dec 2016 21:07:41 GMT</pubDate>
            <atom:updated>2016-12-09T22:00:35.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*J1kCbSPeP6gCbeUN.jpg" /></figure><p>Content marketing has been growing in popularity for years, and for good reason, <strong>it works</strong>.</p><p>Creating blog content is a <a href="https://research.hubspot.com/reports/compounding-blog-posts-what-they-are-and-why-they-matter">proven source of sustainable organic traffic</a> and a great way to drive qualified leads.</p><p>Most companies look to WordPress, SquareSpace, or Medium for their company blogs. While these sites work for hosting blog content, they come with a number of downsides, especially if your target audience is developers.</p><p><strong>Problems with the typical company blog setup:</strong></p><ul><li>Barriers to contribute</li><li>Speed and security issues (<em>cough, cough </em>WordPress)</li><li>Traffic cannibalization (Medium)</li><li>Limited ability to customize &amp; reuse product UI</li><li>Poor authoring experience for developer-focused content</li></ul><p>This post presents about a different approach that, in my opinion, is better than a traditional blog setup.</p><p>Let’s explore the <strong>100% Open Source, Markdown &amp; React-powered blog</strong> that you’re reading.</p><h3>The Serverless Blog</h3><p>Serverless.com’s blog is 100% open source content driven by a <a href="https://github.com/serverless/blog">GitHub repo</a> and Markdown files.</p><p>Blog content is fed into our site and is rendered with our static website generator of choice <a href="http://phenomic.io/">Phenomic</a>.</p><p>Let’s explore the benefits of our blog setup and how they address the problems outlined above.</p><h4>1. Easier to contribute and edit posts</h4><p>Well for starters, anyone with a GitHub account can submit blog post updates, typo fixes, and new content without needing a user account with our site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/0*y7FbKevgafBUcynU.jpg" /></figure><p>On every post users have a one click ‘Edit this post’ link that lets anyone submit updates to posts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7Z-gS42xemh_GfKx.jpg" /></figure><p>This is great for getting streamlined contributions to our blog.</p><p><em>P.S. We’re always looking for fresh content. </em><a href="https://serverless.com/blog/contribute/"><em>Drop us a line if you’re interested in contributing</em></a><em>.</em></p><h4>2. Better developer-focused posts</h4><p>If you’ve ever had to write a code heavy developer-focused blog post in WordPress, it’s a <strong>rather painful</strong> experience. WYSIWYG editors are extremely proficient at mangling code snippets.</p><p>On the flip side, writing in GitHub flavored Markdown makes writing and (more importantly) maintaining blog posts about code MUCH easier.</p><p><strong>Markdown</strong> FTW! 🎉</p><p><em>Side note: If you’re stuck with WordPress, I wrote a plugin to allow you to write in </em><a href="http://davidwells.io/easy-markdown/"><em>GitHub favored Markdown</em></a></p><h4>3. Unified product experience</h4><p>We’re using React as our frontend framework of choice for creating our serverless applications (like <a href="http://github.com/serverless/dashboard">dashboard</a>). This is a no-go with other blogging setups.</p><p>If we decided to blog with WordPress, we’d need to maintain 2 separate style/component libraries because WordPress can’t render React components server-side. Keeping styles in sync in multiple platforms is painful and eventually leads to an inconsistent user experience.</p><p>Luckily, our site and blog are powered by <a href="http://phenomic.io/">Phenomic</a>, so we can use all of the same React components we use in our products.</p><p><strong>Code reuse and brand consistency FTW</strong>! 🎉</p><h4>4. Scale out of the box</h4><p>Using a static site gives us raw scale out of the box unlike dynamic blogging platforms like WordPress.</p><p><strong>How our static site is built:</strong></p><ol><li>npm run build uses React&#39;s server-side rendering capabilities to build all the static HTML files for the site</li><li>That’s it. The site is pre-rendered for all visitors 🔥</li></ol><p>If we get featured on the front page of the <em>New York Times</em> or Justin Bieber tweets about Serverless, we’re sitting pretty because our site is statically served from the <a href="https://www.netlify.com/">Netlify</a> content delivery network.</p><h4>5. Speed like Whoa 🔥</h4><p>Because we’re using <a href="https://github.com/MoOx/phenomic">Phenomic</a>, which uses React + React Router under the hood, page fetching and transitions are lightning fast.</p><p>Instead of hard page reloads when navigating around the serverless.com site, you get a single page app experience when navigating through site links.</p><p>Each link clicked only fetches the required data from a .json file, instead of a full HTML page like other static site generators.</p><p>Another out-of-the-box benefit with Phenomic is <strong>optimistic page rendering.</strong></p><p>This is an example of how the loading state of a blog post looks while the post’s lightweight json data is being fetched</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*QsPuf2ydUBLeGKrd.gif" /></figure><p>As you can see, when navigating to any given page, the visitor gets instant feedback, so the perceived site performance feels snappy.</p><h3>React + Phenomic + Static Websites are the future</h3><p>Ultra scalable, fast, dynamic static websites are the future of frontend sites and I highly recommend checking out our site repo for how it’s all hooked up!</p><p>You can run our site locally by:</p><ol><li>git clone git@github.com:serverless/site.git</li><li>npm install</li><li>npm start</li></ol><p>If I haven’t convinced you yet. Tweet at me <a href="http://twitter.com/davidwells">@DavidWells</a> and I will yell at you.</p><p>I’m planning a series of posts illustrating how the site is built.</p><p>For now, <a href="https://github.com/serverless/site">check out the GitHub repo</a>.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/how-to-create-a-fast-secure-and-scalable-open-source-blog-with-react-markdown/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5361795c28f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/how-to-create-a-fast-secure-and-scalable-open-source-blog-with-react-markdown-5361795c28f3">How to Create a Fast, Secure, and Scalable Open Source Blog with React + Markdown</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Function metrics, easier AWS credential setup, and Lambda versioning in Serverless Framework v1.3]]></title>
            <link>https://medium.com/serverless-stories/function-metrics-easier-aws-credential-setup-and-lambda-versioning-in-serverless-framework-v1-3-68e366f96f76?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/68e366f96f76</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Tue, 06 Dec 2016 22:48:45 GMT</pubDate>
            <atom:updated>2016-12-02T18:17:12.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*B74oGO8WtzjpHRV0quSBvg.gif" /><figcaption>We’re proud to release the Serverless Framework v1.3.0 today!</figcaption></figure><h3>Highlights of 1.3.0</h3><p>Let’s take a look at the highlights of this release. You can find a list with all the updates in the <a href="https://github.com/serverless/serverless/blob/master/CHANGELOG.md">changelog</a>.</p><h4>Function Metrics</h4><p>Ever wondered how your functions are performing? The new serverless metrics allows you to see all the function metrics, such as invocations, throttles, errors, and duration, at a glance.</p><p>Just type</p><pre>serverless metrics --function myFunction</pre><p>to see the metrics of the last 24h for your function myFunction.</p><p>You can even specify the timeframe you want to see for the metrics with the startTime and endTime options.</p><p>For example,</p><pre>serverless metrics --function myFunction --startTime 2016-11-28 --endTime 2016-12-02</pre><p>will show you all the metrics between Nov. 28th and Dec. 2nd.</p><p>You can read more about the new metrics functionality in <a href="https://serverless.com/framework/docs/providers/aws/cli-reference/metrics/">the documentation</a>.</p><h4>AWS Credentials Setup</h4><p>Setting up credentials should be streamlined in the overall Serverless experience. V1.3 adds a new command called serverless config credentials that helps you setup your AWS credentials on your local machine.</p><p>This example will setup the default AWS profile with the provided key and secret:</p><pre>serverless config credentials --provider aws --key someKey --secret someSecret</pre><p>No need to configure the credentials file through the aws-cli anymore.</p><p>You can read more about the new config functionality in <a href="https://serverless.com/framework/docs/providers/aws/cli-reference/config/">the documentation</a>.</p><h4>Lambda Versioning</h4><p>Serverless now supports automatic Lambda versioning with the help of the built-in Lambda versions AWS provides.</p><p>Keeping a history of all of your deployed Lambda functions is an important feature. AWS will now use your Lambda version in the logs, as well. This makes it way easier to track down bugs.</p><p>You don’t need to change anything. Just deploy your service as usual and Serverless will version your Lambda functions from now on.</p><h4>Refactorings and Bug Fixes</h4><p>We’ve also fixed a bunch of bugs (thanks for bringing them up!), and have continued our process of <a href="https://github.com/serverless/serverless/issues/2645">codebase refactorings</a> so that it’s easier for new contributors to get on board.</p><h4>Next Steps</h4><p>We’ve already started filling in the next <a href="https://github.com/serverless/serverless/milestones">milestones</a>. Check out the <a href="https://github.com/serverless/serverless/milestone/18">1.4 milestone</a> to see what you can expect in two weeks.</p><p>We hope that you have fun with the new release! Let us know if you have any questions or feedback in <a href="http://forum.serverless.com/">our Forum</a> or <a href="https://github.com/serverless/serverless/issues">GitHub Issues</a>.</p><h4>Using Semver</h4><p>Note that we’re using <a href="http://semver.org/">strict Semver</a> for our Serverless Framework versioning. This way you’ll know when we introduce major features or breaking changes.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/serverless-v1.3.0/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68e366f96f76" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/function-metrics-easier-aws-credential-setup-and-lambda-versioning-in-serverless-framework-v1-3-68e366f96f76">Function metrics, easier AWS credential setup, and Lambda versioning in Serverless Framework v1.3</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Serverless re:Invent]]></title>
            <link>https://medium.com/serverless-stories/a-serverless-re-invent-cd5d2790c414?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/cd5d2790c414</guid>
            <category><![CDATA[awsreinvent]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Tue, 06 Dec 2016 22:48:32 GMT</pubDate>
            <atom:updated>2016-12-06T22:47:59.127Z</atom:updated>
            <content:encoded><![CDATA[<p>Many of AWS’ biggest releases tend to happen around their annual re:Invent conference, and 2016 was no exception. AWS announced lots of amazing stuff last week in Vegas. Here are some highlights of what we’re most excited about as it relates to serverless architectures.</p><h3>Lambda@Edge</h3><p><strong>What is it?</strong></p><ul><li>Allows JavaScript to be run inside a Lambda on any AWS edge location</li><li>Several options available that define which types of requests trigger your code to run</li></ul><p><strong>Why it’s important?</strong></p><p>This allows for interesting use cases such as ‘intelligent’ HTTP processing and modifying HTTP headers on the fly. Also has some interesting potential use cases for IoT.</p><h3>AWS X-Ray</h3><p><strong>What is it?</strong></p><ul><li>Provides distributed tracing for distributed systems on AWS</li><li>Provides a visualization of your applications’ components and allows for an end-to-end view of requests</li><li>The final missing monitoring piece for AWS</li></ul><p><strong>Why is it important?</strong></p><p>Getting a detailed view of performance as well as debugging for microservice architectures built on AWS has always been a difficult problem. X-Ray appears to be a tool that will make this a lot easier. It’s not available for Lambda yet, but when it is it will allow for a lot more peace-of-mind and encourage larger, more complex systems to be built on top of it.</p><h3>Step Functions</h3><p><strong>What is it?</strong></p><ul><li>Visual workflow for designing and coordinating microservice oriented applications</li><li>Allows you to setup your functions as a series of ‘steps’, including automatic triggers, tracking, and retries</li></ul><p><strong>Why is it important?</strong></p><p>We haven’t had a chance to dive in deep on the new service yet, but the focus seems to be on maintaining state across functions, as well as providing a visual workflow tool. Tracking state across Lambdas has always been a problem and if this solves that problem it will allow much more complex serverless architectures to be built on AWs.</p><h3>Greengrass</h3><p><strong>What is it?</strong></p><ul><li>Embedded compute, messaging and data caching for connected devices</li><li>Allows for running Lambda functions on devices, online as well as offline</li><li>Brings the Lambda ‘event driven’ story to devices</li><li>Makes the IoT story much more compelling</li><li>Runs online and offline</li><li>Makes device to device communication much easier and more interesting</li></ul><p><strong>Why is it important?</strong></p><p>Greengrass is exciting because it brings Lambda’s ‘event driven’ compute power to devices, making the serverless story for IoT even more compelling. It promises to make offline compute as well as device-to-device communication much easier and more powerful.</p><h3>API Gateway in Marketplace</h3><p><strong>What is it?</strong></p><ul><li>API Gateway endpoints can now be sold on the AWS Marketplace</li></ul><p><strong>Why is it important?</strong></p><p>This is the first step towards allowing developers to sell their functions directly to customers. There aren’t a lot of examples to try out yet, but it will be very interesting to see what type of activity unfolds here.</p><h3>Dead Letter Queues for Lambda</h3><p><strong>What is it?</strong></p><ul><li>Allows failed Lambda events to be automatically sent to an SQS queue or to SNS topic</li></ul><p><strong>Why is it important?</strong></p><p>By default if a Lambda is triggered and fails it will automatically retry twice before discarding the event. Dead letter queues for Lambda mean you will never miss an event again. Failed events can be sent to SQS or SNS where they can be processed and debugged further, so you can actually find the cause of the problem and fix it. This feature makes event processing on Lambda much more reliable and will likely result in a more widespread use.</p><h3>C# for Lambda</h3><p><strong>What is it?</strong></p><ul><li>.NET Core 1.0 is now an officially supported runtime on Lambda</li></ul><p><strong>Why it’s important?</strong></p><p>This announcement is especially interesting for organizations with a C# competency (mostly enterprises) that want to take advantage of all of the value that Lambda has to offer.</p><blockquote><a href="https://docs.google.com/forms/d/e/1FAIpQLSc9-7zPxecAFMNLghatahtTPVpIH19Aypv6tPWxH9sxuyjcug/viewform"><strong>Take our survey on which announcements are the most exciting</strong></a></blockquote><h3>More re:Invent Lambda discussions in Serverless Office Hours</h3><p>Tune in for <a href="https://www.youtube.com/watch?v=IoW_IcvRTGM">Serverless Office Hours</a>, Thursday, Dec. 8, 10–11AM PST, for a live discussion of the Lambda announcements at re:Invent and how they relate to the Serverless Framework. We’ll also answer questions about the latest framework release — v1.3.</p><p>Start tweeting your questions now to <a href="https://twitter.com/goserverless">@goserverless</a> with the hashtag <strong>#ASKSERVERLESS</strong>. Then <a href="https://www.youtube.com/watch?v=IoW_IcvRTGM">log on here</a> for a live chat with members of the core team Thursday.</p><p><strong>About the Author:</strong> Nick Gottlieb is Head of Customer Development at Serverless. He’s passionate about understanding and solving complex problems for software development teams. Prior to joining Serverless he was in charge of scaling growth at CircleCI and helped to design and build early versions of CircleCI Enterprise.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/recap-serverless-announcements-reinvent/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd5d2790c414" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/a-serverless-re-invent-cd5d2790c414">A Serverless re:Invent</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Better DevOps with AWS Lambda + API Gateway and the Serverless Framework]]></title>
            <link>https://medium.com/serverless-stories/better-devops-with-aws-lambda-api-gateway-and-the-serverless-framework-757e6be93c84?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/757e6be93c84</guid>
            <category><![CDATA[aws-api-gateway]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Fri, 02 Dec 2016 22:51:23 GMT</pubDate>
            <atom:updated>2016-12-02T22:58:07.248Z</atom:updated>
            <content:encoded><![CDATA[<h4>Guest Post from <a href="https://medium.com/@nickdenengelsman">Nick den Engelsman</a></h4><p>Hi, I’m <a href="https://twitter.com/nickengelsman">Nick den Engelsman</a>. I’m a Full Stack Developer at <a href="https://www.bandlab.com/">BandLab</a> who specializes in orchestrating and automating highly available infrastructures.</p><p>In this post I’ll share some lessons learned from optimizing DevOps and how that led my team and I to the Serverless Framework.</p><p>At the start of 2016, and for the previous five years, I worked as a Cloud Systems Engineer at a certified AWS Managed Service Program Partner in The Netherlands. Most of my tasks were to educate clients and migrate them to the AWS cloud. Their environments and applications needed to be highly available, scalable and fault tolerant.</p><p>In that role automation was key. Clients only needed to worry about pushing code and in return we would worry about keeping their infrastructure up-to-date, secure, patched, autoscaled, and in general meeting SLA’s. If you think about it, <strong>that’s a lot of work!</strong></p><p>So streamlining our process was key.</p><h3>Optimizing DevOps</h3><h4>Phase 1:</h4><p>In order to stay <a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself">DRY</a> we adopted <a href="https://aws.amazon.com/cloudformation/">AWS CloudFormation</a> early on. This worked for a while, but we were copying CloudFormation JSON templates and other resources back-and-forth between projects (Not DRY).</p><h4>Phase 2:</h4><p>Since myself and a few others within the company had solid Ruby knowledge, we came up with the idea to create Ruby modules that would compile to CloudFormation JSON resources (similar to Python’s <a href="https://github.com/cloudtools/troposphere">Troposphere</a>). Again this worked for a while but also ended up not being as DRY as we would’ve liked!</p><h4>Phase 3:</h4><p>As time progressed, the company built-out the group of Ruby experts and we started an <a href="https://en.wikipedia.org/wiki/Research_and_development">R&amp;D</a> team whose only focus was the automation and building of components that could be re-used between clients and projects. We matured our Ruby modules and made them more and more intelligent in order do most of the configuration for us. It became its own “framework”!</p><h3>Soooo, where does serverless come into play?</h3><p>While still at the Dutch company we managed to set up a solid framework to automatically deploy/update/patch highly available infrastructures, which left us with only one thing we couldn’t change: Client applications!</p><blockquote><em>There was only one thing we couldn’t change: </em><strong><em>Client applications!</em></strong></blockquote><p>Every new client needed to be educated. And migrating them to AWS in general was a long process. For the most part, the refactoring of their application code was needed in order to become <a href="https://12factor.net/">12-factor-ready</a>.</p><blockquote><a href="https://aws.amazon.com/lambda/details/"><em>AWS Lambda</em></a><em> lets you run code without provisioning or managing servers. You pay only for the compute time you consume — there is no charge when your code is not running.</em></blockquote><p>When AWS first <a href="https://www.youtube.com/watch?v=9eHoyUVo-yg">introduced</a> Lambda at re:Invent in 2014, I was a bit skeptical. Their example used S3 events. The triggering of image resizing with Lambda was awesome, but I didn’t see our clients adopting this anytime soon.</p><p>Internally we started sprinkling in custom <a href="https://aws.amazon.com/blogs/aws/aws-cloudformation-update-lambda-backed-custom-resources-more/">Lambda-Backed Custom Resources</a> within CloudFormation stacks to fill-up missing gaps. This was when I started to realize how powerful Lambda actually is. We were able to automate a lot of use-cases and 3rd party applications/providers with the use of AWS Lambda.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZJND4QlX7VnVG7Pc.jpg" /></figure><h3>Fast forward</h3><p>I had begun to work on a passion-project of my own known as <a href="https://www.composrapp.com/">Composr</a> (later acquired by BandLab) which was fully EC2 — Ruby on Rails. I decided whilst funding my own project that it didn’t make sense to spend money on resources which could only be used occasionally, such as for testing and staging purposes.</p><blockquote><em>As </em><a href="https://aws.amazon.com/api-gateway/"><em>AWS API Gateway</em></a><em> and AWS Lambda were maturing, I decided to invest my time in using these newer styles of computing, and prove that it is entirely possible to design complete applications without having to manage any servers.</em></blockquote><p>The Serverless Framework seemed like the perfect fit to accomplish this goal! Noticing that it used CloudFormation from the start also gave me the assurance that deployments would be straight-forward and battle tested.</p><p><strong>Today</strong></p><blockquote><em>A creative, collaborative, global community of Musicians</em></blockquote><p><a href="https://www.bandlab.com/">BandLab</a> is where musicians and music fans from all over the world can come together to make, collaborate and share Music. The platform works on both iOS and Android. Everything users create is hosted in the cloud, so they can capture musical ideas wherever they are, then further develop them using BandLab’s web-based, MIDI-enabled app.</p><p>The Serverless Framework was easy to pick up within our team, even for developers without prior AWS knowledge.</p><p>After migrating the first few existing microservices towards a serverless setup, we were able to handle more events and background tasks in less time, which in return led to happier users on our platform (oh yeah, and less costs). We came to the conclusion that we wanted to push even further with this technology, to try and go serverless first.</p><p>The Serverless Framework has now become a core component within our organization. It allows us to define a standardized way of developing/deploying microservices, to release to market faster, and to keep our cost of ownership low.</p><blockquote><em>In general the Serverless Framework makes our work and life just a little bit happier :)</em></blockquote><p>Today, <a href="https://www.bandlab.com/">BandLab</a> is running most if its AWS infrastructure without any self-managed servers (just a few EC2 instances left). Since we run less servers, we have less people to worry about maintenance, monitoring, patching, scaling alarms and the like (happy developers).</p><h3>What’s next</h3><p>Curious where the <a href="https://www.bandlab.com/">BandLab</a> project is heading? Checkout our <a href="https://blog.bandlab.com/">blog</a> or follow us on <a href="https://twitter.com/bandlab">Twitter</a>.</p><h4>About the Author</h4><p><a href="https://medium.com/@nickdenengelsman">Nick den Engelsman</a> is Full Stack Developer at BandLab, who specialises in orchestrating and automating highly available infrastructures. He’s also a contributor to the Serverless Framework.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/going-serverless-at-bandlab/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=757e6be93c84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/better-devops-with-aws-lambda-api-gateway-and-the-serverless-framework-757e6be93c84">Better DevOps with AWS Lambda + API Gateway and the Serverless Framework</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Lessons Learned on Building Awesome Developer Communities from CMX Summit]]></title>
            <link>https://medium.com/serverless-stories/6-lessons-learned-on-building-awesome-developer-communities-from-cmx-summit-5d74da75dfa0?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d74da75dfa0</guid>
            <category><![CDATA[community-manager]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cmx-summit]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 19:44:39 GMT</pubDate>
            <atom:updated>2016-11-23T19:44:05.028Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://cmxhub.com/summit/">CMX Summit</a> is an annual conference for community managers featuring top tier experts from companies like Google, Slack, and Salesforce. Speakers cover topics ranging from how to grow developer communities from scratch to member engagement to measuring ROI on community. Fortunately for me, the CMX Summit is hosted in San Francisco, where I live and work, making it possible to connect with the world’s top community managers right in my backyard.</p><p>This year CMX divided the talks into two tracks — Developer Community &amp; Support Community. I was stoked to see the focus on developer community. As an open source framework, community is one of our highest priorities at Serverless. I was especially looking forward to learning more about how <a href="https://twitter.com/ashevat">Amir Shevat</a> (Slack) and <a href="https://twitter.com/adrisonic">Adriana Cerundolo</a> (Google) were engaging their communities.</p><p>Here are a few takeaways on how to build a thriving developer community from my 2016 CMX experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1qR04e3vjW15r56W.jpg" /></figure><h3>1. Focus on high value developers.</h3><p><a href="https://en.wikipedia.org/wiki/Pareto_principle">The Pareto Principle</a> states that 80% of activity comes from 20% of the population. So when you’re determining how to move the needle in your community, it’s important to focus on your top contributors. They provide the highest ROI.</p><h3>2. Build simplicity and predictability for a successful community.</h3><p>The natural progression of developer engagement in an open source community is:</p><ul><li><strong><em>Discovery</em></strong> — Onboarding has to be simple and developers need to have all the necessary info to get started.</li><li><strong><em>Setup Toolchains</em></strong> — Also needs to be super easy, as in one click.</li><li><strong><em>Develop Skills</em></strong> — Early beginners don’t have the knowledge to be creative yet, so it’s important to show them what’s possible.</li><li><strong><em>Find Tasks</em></strong> — If people can’t easily see (in the same place every time) what needs to be done, then they’ll go and work on other projects.</li><li><strong><em>Get Help</em></strong> — Make sure that forum and support questions are answered consistently to keep people coming back, and to make it obvious to users where to go for help.</li><li><strong><em>Feel Appreciated</em></strong> — As developers become deeply embedded in your community, make sure that they’re recognized and appreciated.</li></ul><p>Each of these steps represents a potential stumbling block for turning developers into core members of your community. Figuring out how to remove all pain points is crucial to success.</p><h3>3. Developer Communities belong under Product, not Sales or Marketing.</h3><p>This is something to keep in mind as your community continues to grow. Leverage your community to make your product better and cultivate future users. But be aware of turning developers off by spamming them with marketing lingo or trying to sell them stuff.</p><h3>4 Empathy is king.</h3><p>It’s easy to get excited about launching new programs and building new features that you think are cool. But it’s important to listen to the community and hear what they care about. Communication is a two-way street.</p><h3>5. Measure, measure, and measure some more.</h3><p>The only way to truly understand the health and success of a community is by measuring key metrics over time. Determine which metrics you can track to see how dynamic your community is. Some key metrics that <a href="https://twitter.com/ginab">Gina Bianchi</a> from Mightybell recommended tracking are monthly active users and monthly active user growth. Here at Serverless we define an active user as anybody who’s run at least four commands in the last 30 days.</p><h3>6. Make your community FUN!</h3><p>This was a common theme among every speaker. Most of us face fierce competition in our respective markets. Figure out how to make your community fun and engaging, and people will stay and attract more members, no matter how many more marketing dollars the other guy is spending.</p><p>These are just a few of the highlights from CMX Summit 2016. It was so inspiring to hear how other companies are prioritizing community management. We’ve already started incorporating these lessons into our strategy at Serverless. We’ll let you know how it goes. You can check out the <a href="http://cmxhub.com/browse/">CMX website</a> for more helpful articles about community.</p><p><strong>Want to get involved in the Serverless Community?</strong><em> </em>Join us on <a href="https://github.com/serverless">GitHub</a>, the <a href="http://forum.serverless.com/">Serverless Forum</a>, <a href="https://gitter.im/serverless/serverless">Gitter</a>, <a href="https://twitter.com/goserverless">Twitter</a> or by writing a guest post for <a href="https://github.com/serverless/blog">the blog</a>. We’re always open to feedback. Let us know what you think</p><p><strong><em>About the Author:</em></strong><em> Serverless Operations Manager Casey Shultz is a yoga loving, dog cuddling, San Francisco transplant originally from Alaska. When she’s not ruling the Serverless office with an iron fist you can find her camping in Yosemite.</em></p><p><em>Originally published at </em><a href="https://serverless.com/blog/lessons-learned-on-building-awesome-developer-community/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d74da75dfa0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/6-lessons-learned-on-building-awesome-developer-communities-from-cmx-summit-5d74da75dfa0">6 Lessons Learned on Building Awesome Developer Communities from CMX Summit</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flexible Environment Variable Support for AWS Lambda in Serverless v1.2]]></title>
            <link>https://medium.com/serverless-stories/flexible-environment-variable-support-for-aws-lambda-in-serverless-v1-2-580c5d0a4118?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/580c5d0a4118</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Tue, 22 Nov 2016 20:37:41 GMT</pubDate>
            <atom:updated>2016-11-22T20:38:09.414Z</atom:updated>
            <content:encoded><![CDATA[<p>Today we’re proud to announce the new version 1.2.0 of the Serverless Framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ITdVsfdX2TcXV--ntF27YA.gif" /></figure><h3>Highlights of 1.2.0</h3><p>Let’s take a look at the release highlights. You can find a complete list of changes in the <a href="https://github.com/serverless/serverless/releases/tag/v1.2.0">release changelog</a>.</p><h4>Environment Variables</h4><p>AWS just added native support for environment variables inside of Lambda functions a few days ago.</p><p>We’re proud to announce that Serverless v1.2 ships with support for native environment variables as well! You can define environment variables on a service- or function level.</p><p>Environment variables become even more useful if you use them together with Serverless Variables to reference dynamic values.</p><h4>JavaScript Support for Serverless Variables</h4><p>Serverless Variables now support raw JavaScript so that you can easily generate dynamic data. This makes the Serverless Variables even more powerful.</p><p>Possible use cases for this could be the fetching of data from a REST API (e.g. secrets) or the generation of random variable data (e.g. for testing).</p><h4>Include and Exclude for Packaging</h4><p>Serverless recently introduced globs support for the exclude configuration.</p><p>Negated glob patterns (e.g. !some-file or !some-directory/**) can be used to include files and directories back again.</p><p>However, having the include configuration for this was way more convenient. 1.2.0 brings back include with globs support.</p><p><strong><em>Note:</em></strong><em> Negated globs are still supported in both, </em><em>include and </em><em>exclude.</em></p><h4>Limited Lambda Permissions</h4><p>Lambda permissions for event sources (S3, SNS, etc.) are now bound to the resource, which should trigger the Lambda function rather than enabling all event sources of a certain type to call the Lambda function.</p><p>This update tightens security and avoids unexpected behavior.</p><p>It’s a change that will happen once you (re)deploy your service with Serverless 1.2 and will not introduce any breaking changes.</p><h4>Refactorings and Bug Fixes</h4><p>We’ve fixed a bunch of bugs (thanks for bringing them up!) and also started our process of <a href="https://github.com/serverless/serverless/issues/2645">codebase refactorings</a> which will improve the whole onboarding process for new contributors.</p><h4>Next Steps</h4><p>We’ve already started filling in the next <a href="https://github.com/serverless/serverless/milestones">milestones</a> for Serverless. Check out the <a href="https://github.com/serverless/serverless/milestone/17">1.3 milestone</a> to preview what you can expect in two weeks.</p><p>We hope that you have fun with the new release! Let us know if you have any questions or feedback in <a href="http://forum.serverless.com/">our Forum</a> or <a href="https://github.com/serverless/serverless/issues">Github Issues</a>.</p><h4>Using Semver</h4><p>Note that we’re using <a href="http://semver.org/">strict Semver</a> for our Serverless Framework versioning. This way you’ll know when we introduce major features or breaking changes.</p><h3>Serverless Examples</h3><p>We’ve created a new repository called <a href="https://github.com/serverless/examples">“examples”</a> which is a dedicated place for Serverless service examples. The goal is to showcase different scenarios using serverless architecture and the Serverless Framework.</p><p>Feel free to contribute and add your example!</p><h3>Serverless Dashboard</h3><p>The <a href="https://github.com/serverless/dashboard">Serverless Dashboard</a> desktop application is a project we’re working on to provide a user-friendly layer on top of the Serverless CLI.</p><p>The goal of the dashboard is to help enhance the user experience for the Serverless Framework. The new dashboard allows you to deploy your service, invoke a function or view the function logs with a single click.</p><p>You should definitely give it a spin! Please let us know what you think.</p><h3>Serverless LA Meetup</h3><p>On December 7th we’ll kick-off the <a href="https://www.meetup.com/Serverless-LA">Serverless LA Meetup</a> series with interesting talks from Nick Gottlieb (Head of Customer Development at <a href="http://serverless.com/">Serverless, Inc.</a>) and Marc Campbell (CTO of <a href="https://www.replicated.com/">Replicated</a>) about the Serverless Framework and serverless architectures. Join us if you’re in LA!</p><h3>Serverless Survey</h3><p>Your feedback is important in guiding the direction of the framework. Please take a few minutes and fill out <a href="https://docs.google.com/a/serverless.com/forms/d/1F7rRx01NMDmmLiDiEzc0iKGTlyEx1RrzItRvvoe6a4A/edit?usp=drive_web">our survey</a> so that we can understand how you use the Serverless Framework and what your needs are.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/serverless-v1.2.0/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=580c5d0a4118" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/flexible-environment-variable-support-for-aws-lambda-in-serverless-v1-2-580c5d0a4118">Flexible Environment Variable Support for AWS Lambda in Serverless v1.2</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Serverless Office Hours]]></title>
            <link>https://medium.com/serverless-stories/introducing-serverless-office-hours-a32f22f758c3?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/a32f22f758c3</guid>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Fri, 28 Oct 2016 19:33:20 GMT</pubDate>
            <atom:updated>2016-10-28T19:33:59.223Z</atom:updated>
            <content:encoded><![CDATA[<p>At Serverless our community and contributors’ input matters to us — a lot. Earlier this month we <a href="https://serverless.com/blog/releasing-serverless-framework-v1-and-fundraising/">released V.1 of Serverless</a>. Now that you’ve had some time to check it out, we want to know what you think.</p><p>What questions have come up? What do you want to see next? Let us know in our first edition of Serverless Office Hours where we’ll devote one hour to answering your questions and feedback.</p><p>Join the Serverless CEO <a href="https://twitter.com/austencollins">Austen Collins</a>, CTO <a href="https://twitter.com/flomotlik">Florian Motlik</a> and Developer Evangelist <a href="https://twitter.com/DavidWells">David Wells</a> for a live chat about V.1 of the Serverless Framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3jq_QNmXs7yi4yo3pKfaGQ.jpeg" /></figure><h4>How To Get Involved:</h4><ol><li>Install the latest version of Serverless: npm install -g serverless, if you haven&#39;t already checked it out.</li><li>Tweet <a href="https://twitter.com/goserverless">@goserverless</a> with your questions about V.1 of the Serverless Framework between now and 12AM PST, Thur., Nov. 3.</li><li>Be sure to include the hashtag <strong>#AskServerless</strong>.</li><li>Tune into <a href="https://www.youtube.com/watch?v=IxVxNjEqSCM">YouTube Live</a> Thur., Nov. 3, 10–11AM PST when the Serverless team will answer your questions.</li></ol><p>Can’t join us live? No problem! We’ll share a recording of Office Hours on <a href="https://www.youtube.com/channel/UCFYG383lawh9Hrs_DEKTtdg">YouTube</a>, so send us your questions anyway.</p><p>Start sending us your questions tagged with <strong>#AskServerless</strong> and stay tuned for upcoming Serverless Office Hours topics and dates!</p><p><em>You can join the ongoing discussion about Serverless on </em><a href="https://github.com/serverless/serverless"><em>GitHub</em></a><em>, </em><a href="https://twitter.com/goserverless"><em>Twitter</em></a><em>, </em><a href="https://gitter.im/serverless/serverless"><em>Gitter</em></a><em>, the </em><a href="http://forum.serverless.com/"><em>Serverless Forum</em></a><em> or </em><a href="https://www.facebook.com/serverless/"><em>Facebook</em></a><em>.</em></p><p><em>Originally published at </em><a href="https://serverless.com/blog/introducing-serverless-office-hours/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a32f22f758c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/introducing-serverless-office-hours-a32f22f758c3">Introducing Serverless Office Hours</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building A Serverless Garden Monitoring System with Lambda]]></title>
            <link>https://medium.com/serverless-stories/building-a-serverless-garden-monitoring-system-with-lambda-c72c54113df2?source=rss----bfef62be8f1e---4</link>
            <guid isPermaLink="false">https://medium.com/p/c72c54113df2</guid>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Serverless]]></dc:creator>
            <pubDate>Tue, 25 Oct 2016 15:32:29 GMT</pubDate>
            <atom:updated>2016-12-02T23:03:50.741Z</atom:updated>
            <content:encoded><![CDATA[<h4>Guest Post from <a href="https://medium.com/@johncmckim">John C. McKim</a></h4><h3>My Serverless Garden</h3><p>I have a problem with my garden. Or more accurately, I have a problem remembering to care for my garden.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*SKv6O5oDjEzSDOcI.jpg" /></figure><p>My name is <a href="https://twitter.com/johncmckim">John McKim</a> and I’m a software developer based in Brisbane, Australia. I work for <a href="https://acloud.guru/">A Cloud Guru</a> on our Serverless learning platform.</p><p>In February of this year (2016), I attended an AWS Meetup where <a href="https://twitter.com/samkroon">Sam Kroonenburg</a> spoke about <a href="https://acloud.guru/">A Cloud Guru</a>. Sam told us how he built <a href="https://acloud.guru/">A Cloud Guru</a> without a single server. I was inspired.</p><p>After that Meetup I started learning as much as I could about Serverless. I started by converting an <a href="https://blog.johncmckim.me/express-to-aws-lambda-part-1-a057096abe34">Express app to Serverless</a> with the Serverless Framework. But that wasn’t enough. I wanted to build a real project. To do that, I needed a problem.</p><h3>The Problem</h3><p>I love gardening, but I often forget to water my plants. I needed a way to monitor my plants, and more importantly, for them to tell me when they needed watering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*-AUeOKaQcouF8EPa.jpg" /></figure><p>This was a great problem to solve. I needed to build a dashboard and notification system and connect it to my garden through an IoT service. It’s an event-driven system which makes serverless architecture an ideal solution for this problem.</p><h3>The Project</h3><p>The architecture for the project is below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*3FGH0pgo55NCZhiF.png" /></figure><p>I started the project as a single monolithic Serverless service. There are <a href="http://martinfowler.com/bliki/MonolithFirst.html">good reasons to do this</a>. As the project grew, I broke it up into four services.</p><h4>IoT Service</h4><p>The <a href="https://github.com/garden-aid/iot-hub">IoT Service</a> is the heart of this project. The IoT Service uses the AWS IoT Device Gateway and Rules Engine. The Device Gateway provides an endpoint for messages to and from devices. I use the Rules Engine for two tasks:</p><ul><li>Storing raw messages in DynamoDB for the dashboard</li><li>Invoking the check moisture Lambda in the notifications service</li></ul><p>The Rules Engine connects the services with devices. It’s the piece that makes Serverless a great solution for an IoT system.</p><h4>Notifications Service</h4><p>The <a href="https://github.com/garden-aid/chat-bff">Notifications Service</a> sends messages to Slack when the soil moisture is too low. It has two Lambda functions in the service. The first Lambda function checks the moisture level and sends a SNS message if it’s too low. The SNS message triggers the second Lambda function which sends a message to Slack. This design keeps the system highly cohesive and loosely coupled.</p><p>The end result is notifications sent from devices appearing as messages in Slack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*lWr__z5gHbCw-2Tb.png" /></figure><h4>Web Backend</h4><p>The <a href="https://github.com/garden-aid/web-bff">Web Backend</a> provides a GraphQL API for the Web Client. The backend has just one API Gateway endpoint and Lambda function. The Lambda function processes GraphQL queries and responds with data from a DynamoDB table. A custom authorizer protects the GraphQL endpoint by verifying a JWT from Auth0. This stack allowed me to create a useful backend with very few lines of code.</p><h4>Web Client</h4><p>The <a href="https://github.com/garden-aid/web-client">Web Client</a> allows me to monitor my garden through a dashboard. I built the Web Client using React + Redux. The client polls the GraphQL API every 30 seconds for moisture levels. This data is used to display a dashboard to users (me).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*9X0oDGfFNV4eW28U.jpg" /></figure><h3>What I Learned</h3><p>This project has been extremely valuable to me. I still forget to water my plants. But I have learned so much by building something to solve a real problem.</p><p>It wasn’t all smooth sailing. In fact, the project isn’t finished (is software ever finished?). The AWS IoT Device Gateway requires clients to authenticate with mutual TLS 1.2 authentication. The device I bought does not support TLS 1.2 out of the box. So as of now (Oct 2016), I haven’t actually gotten a soil moisture sensor working.</p><h4>Know your Services</h4><p>Knowing what cloud services exist and how they work is important. If I had known that AWS IoT requires TLS 1.2 I would have bought a different device. Knowing what different services are offered allows you to choose the best in class for your project. I chose Firebase hosting over S3 + CloudFront as it’s far better suited for single page apps. Spending time researching services rather than just using what you know will benefit you in the long run.</p><h4>Selecting Boundaries</h4><p>Selecting boundaries for Microservices is hard. A good rule of thumb for Microservices is that each service should own its own data. Right now (Oct 2016), the DynamoDB table is in the IoT service and queried by the Web Backend. I took this approach as the Rules Engine is storing the data in DynamoDB. But this breaks the earlier rule. What I should have done is create the DynamoDB table and Rule that stores the data in the Web Backend.</p><h4>Automation</h4><p>Investing time in unit tests and CI/CD is always worth it. This project has been deployed to AWS and Firebase countless times. But it was rarely me that deployed the project. Travis CI has saved me a lot of time and caught errors before they were a problem. Even if you are creating a small side project, help yourself by automating everything.</p><h4>GraphQL</h4><p>Lastly, <a href="http://graphql.org/">GraphQL</a> is awesome. It’s a great alternative to REST API’s and well suited to Serverless systems. If you haven’t had a look at GraphQL I strongly suggest that you do. The Serverless Framework has a <a href="https://github.com/serverless/serverless-graphql">boilerplate</a> that can help you get started.</p><h3>What’s Next</h3><p>I recently (Sep 2016) started working for <a href="https://acloud.guru/">A Cloud Guru</a> — a company that provides <a href="https://acloud.guru/courses">online on-demand training</a> for engineers on AWS. I’m excited to be working for the company that inspired me to learn about Serverless in the first place. I now find myself very busy running a <a href="https://www.meetup.com/Brisbane-Serverless-Meetup-Group/">Serverless Meetup</a>, blogging and doing talks on Serverless.</p><p>But I do hope to keep working on this project. I recently (Oct 2016) received some new devices and I hope to build the soil moisture sensor soon.</p><p>If you would like to learn more about this project please go and read my blog posts:</p><p>If you want see where this project goes next follow me on <a href="https://medium.com/@johncmckim">Medium</a> or <a href="https://twitter.com/johncmckim">Twitter</a>.</p><h4>About John C. McKim</h4><p><a href="https://medium.com/@johncmckim">John McKim</a> is a developer at A Cloud Guru. He is is part of the team that is building the A Cloud Guru platform, a Serverless learning platform. He contributes to the Serverless Framework and runs the Brisbane Serverless Meetup.</p><p><em>Originally published at </em><a href="https://serverless.com/blog/building-a-serverless-garden/"><em>serverless.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c72c54113df2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-stories/building-a-serverless-garden-monitoring-system-with-lambda-c72c54113df2">Building A Serverless Garden Monitoring System with Lambda</a> was originally published in <a href="https://medium.com/serverless-stories">Serverless Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>