github.com/mweagle/Sparta@v1.15.0/docs/reference/step/index.xml (about) 1 <?xml version="1.0" encoding="utf-8" standalone="yes"?> 2 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 3 <channel> 4 <title>Sparta - AWS Lambda Microservices</title> 5 <link>/reference/step/</link> 6 <description>Recent content on Sparta - AWS Lambda Microservices</description> 7 <generator>Hugo -- gohugo.io</generator> 8 <language>en-US</language> 9 <lastBuildDate>Mon, 10 Dec 2018 21:37:37 +0000</lastBuildDate> 10 11 <atom:link href="/reference/step/index.xml" rel="self" type="application/rss+xml" /> 12 13 14 <item> 15 <title>Lambda</title> 16 <link>/reference/step/lambda/</link> 17 <pubDate>Mon, 10 Dec 2018 21:45:23 +0000</pubDate> 18 19 <guid>/reference/step/lambda/</guid> 20 <description>Step Functions AWS Step Functions are a powerful way to express long-running, complex workflows comprised of Lambda functions. With Sparta 0.20.2, you can build a State Machine as part of your application. This section walks through the three steps necessary to provision a sample &ldquo;Roll Die&rdquo; state machine using a single Lambda function. See SpartaStep for the full source. 21 Lambda Functions The first step is to define the core Lambda function Task that will be our Step function&rsquo;s core logic.</description> 22 </item> 23 24 <item> 25 <title>Fargate</title> 26 <link>/reference/step/fargate/</link> 27 <pubDate>Sun, 16 Dec 2018 07:02:28 +0000</pubDate> 28 29 <guid>/reference/step/fargate/</guid> 30 <description>Teaching people to do serverless is hard. It&#39;s far less about teaching someone about FaaS and far more about getting people into the right mindset. It is not about technology, or at least, it&#39;s not about doing technology 31 &mdash; Paul Johnston - knows some stuff about stuff (@PaulDJohnston) December 13, 2018 While Serverless and FaaS are often used interchangeably, there are types of workloads that are more challenging to move to FaaS.</description> 32 </item> 33 34 </channel> 35 </rss>