<?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 Ant Stanley on Medium]]></title>
        <description><![CDATA[Stories by Ant Stanley on Medium]]></description>
        <link>https://medium.com/@iamstan?source=rss-ad73a257e53d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YPwXxf-y45Sp_fR2sNtfWA.jpeg</url>
            <title>Stories by Ant Stanley on Medium</title>
            <link>https://medium.com/@iamstan?source=rss-ad73a257e53d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:32:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iamstan/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[Cloud Complexity Paradox]]></title>
            <link>https://medium.com/dev-axe/cloud-complexity-paradox-5916cde527c6?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5916cde527c6</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[amazon-web-services]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Tue, 20 Jun 2023 15:27:54 GMT</pubDate>
            <atom:updated>2023-06-20T15:27:54.430Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jgrikHF8rG_AaNSIBrzdPQ.png" /><figcaption>Cloud complexity</figcaption></figure><p><em>The more undifferentiated heavy lifting you offload to the cloud, the more complex it becomes to use the cloud.</em></p><p>Cloud providers like Amazon Web Services’ primary value is that they take on the undifferentiated heavy lifting of providing a functional technology platform for your business. The idea is that why should your organisation employ deep networking, storage, and software specialists in areas that offer no differentiation to your business. They employ these experts, and use them to provide your organisation a platform to build the stuff that does make a difference to your business.</p><p>Over time cloud provider offerings have moved up the stack, taking on more and more of the workloads that are typical in enterprises, along with it more of the undifferentiated workload with each new service. AWS for example has gone from virtual machines by the hour, storage by the gigabyte and a messaging service to a behemoth with over 200 unique services, each of which have multiple features and options.</p><p>This explosion in offerings gives more flexibility than ever before, but comes with significant complexity that hinders adoption.</p><h3>Complexity in choice.</h3><p>Cloud providers have multiple services you can use to achieve the same outcome, with each service having specific benefits and drawbacks, which are dependent on a number of factors, many of which are unique to a specific organisation. In the case of Amazon Web Services, they famously have <a href="https://www.lastweekinaws.com/blog/the-17-ways-to-run-containers-on-aws/">17 ways to run a container</a> workload, how does one decide which platform to use to run that container workload? Is a containerised workload even the best option when AWS also offers VM’s, bare metal, cloud functions and edge functions. Just the compute options are staggering. The choices don’t end with compute, there are multiple messaging services, database services, storage services, and so on. At this point the chances of making sub-optimal choices are probably higher than making the right contextual choice.</p><h3>Complexity in tools.</h3><p>Once service choices are made, which tool set do you use to provision and maintain this infrastructure? Within AWS alone there are a myriad of choices. Beyond using the web interface and CLI, there is the ubiquitous Cloudformation service providing an Infrastructure as Code(IaC) primitive service. Cloudformation can be used natively or via another tool, such as SAM (Serverless Application Model), or the Cloud Development Kit (CDK) from AWS, or 3rd party frameworks like the Serverless Framework and Architect. There is also Terraform which provides a 3rd party declarative IaC primitive, or Pulumi which provides imperative and declarative IaC. Each tool choice has its own characteristics which will impact choice, and relative success. Know which tool to use for which context can be daunting.</p><h3>Complexity in abstraction.</h3><p>The abstraction complexity ultimately is what drives all the other levels of complexity. Cloud providers offer undifferentiated heavy lifting, the question is how much of that heavy lifting do you want to hand off to the provider? Using highly abstracted services means reducing the lines of code you ship into production, and the amount of infrastructure you are directly responsible for. It reduces the complexity in your operational environment as the number of tasks required to operate your production workloads has reduced.</p><p>The flip side is that these abstracted services need more configuration, which sees significant increases in the amount of lines of configuration code. It is possible to build an entire application in AWS with no lines of code running in production, using services like Step Functions, with the tradeoff that there will be hundreds of lines of configuration code to define the behaviour of the services.</p><p>The more abstracted the service is, typically the more configuration options there are. The complexity tradeoff has moved from operational complexity to configuration complexity. Add to this the complexity of configuration tooling, using the more abstracted services of cloud providers can seem impenetrable to less experienced folks.</p><h3>Confusion</h3><p>All of this complexity leads to confusion. Steve Jobs famously wanted to create devices that were so intuitive they did not require an instruction manual. Cloud providers are on the opposite end of that spectrum. They create services so complex they need mountains of technical documentation, best practice guidelines and large teams dedicated to educating people how to use them correctly.</p><p>Over time cloud providers have created a fantastic moat for the people that have spent years building in depth knowledge of these services, whilst making it very challenging for folks and organisations new to cloud.</p><p><em>Original blog post published on </em><a href="https://www.akeero.com/post/cloud-complexity-paradox"><em>Akeero.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5916cde527c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dev-axe/cloud-complexity-paradox-5916cde527c6">Cloud Complexity Paradox</a> was originally published in <a href="https://medium.com/dev-axe">Dev Axe</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[re:Invent Revisited — AWS Fargate]]></title>
            <link>https://medium.com/interruptdev/re-invent-revisited-aws-fargate-87d0980eb2d0?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/87d0980eb2d0</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[container-orchestration]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[aws-fargate]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Thu, 26 Nov 2020 01:49:35 GMT</pubDate>
            <atom:updated>2020-11-26T01:49:35.873Z</atom:updated>
            <content:encoded><![CDATA[<h3>re:Invent Revisited — AWS Fargate</h3><h4>In 2017 AWS launched Amazon Elastic Kubernetes Service, the thing most organizations thought they needed, and AWS Fargate, the thing most organisations actually needed.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lLCBqAy2mcyrkkFGpxrk2g.jpeg" /><figcaption>MGM Grand Arena before Werner’s keynote in 2017</figcaption></figure><p>The 2017 edition of re:Invent had some great announcements. In my previous post we looked at the 2017 announcement of AppSync which didn’t make a keynote. In this post we’re looking at AWS Fargate, announced in Andy Jassy’s keynote, then revisited in Werner’s never ending keynote<a href="https://youtu.be/nFKVzEAm-ts"> the next day by Abby Fuller</a>.</p><p>In the same keynote AWS’s managed Kubernetes service Amazon Elastic Kubernetes Service (EKS) was announced. AWS launching a managed Kubernetes service was always expected. It would have been a bigger announcement if they didn’t launch something in that space. For AWS launching a managed version of an open source project is an acknowledgement they have enough customers running that software themselves that would prefer AWS to run it for them.</p><p>There is a growing number of AWS customers that choose Fargate as their first destination when migrating to container based infrastructure. Vanguard got on the re:Invent stage in 2019 to talk about their AWS migration, with Fargate providing an easy migration target for their existing aPaaS. They skipped the Kubernetes learning curve, and lifted their entire aPaaS into Fargate. Far from alone, organisations as diverse as Samsung Electronics to Square have migrated significant infrastructure to Fargate.</p><p>I see Fargate as the next generation of EC2. EC2 abstracts away hypervisor management and removes management of underlying physical infrastructure from end users. Fargate abstracts away container orchestration management plane and removes management of underlying virtual machines.</p><p>With Fargate the major difference between the two is application encapsulation at container not virtual machine level, resulting in a lightweight portable artifact, with a trade off on constraints on operating system choice. Unfortunately that Windows NT 3.51 VM that should have died in a fire 15 years ago cannot live on in Fargate. The upshot of this is Fargate provides significant cost reductions over virtual machines, improved performance and agility, without the overhead of thinking about container orchestration.</p><p>AWS Fargate is not first to market. Microsoft Azure Container Instances (ACI) is similar and predates it. Predating both is Hyper.sh’s Secure Container Platform. Like Iron.io, a startup that pioneered Functions as a Service before AWS, Hyper.sh no longer exists. It’s engineering group quietly moved Ant Financial Group some time in 2019.</p><p>Early container implementations had the problem of not providing the same level of isolation as virtual machine hypervisors. This limited the adoption of containers in secure environments. Hyper.sh provided a solution to this by creating their own<a href="https://opencontainers.org/"> OCI</a> compliant container runtime,<a href="https://github.com/hyperhq/runv"> runV</a>, that would run on top of a lightweight hypervisor. This provided a lightweight VM with a container interface, but all the security and isolation of a virtual machine. In conjunction with Intel in 2017, Hyper.sh open sourced this approach through the Kata Containers project. Not surprisingly Ant Financial Group are a large user of Kata Containers.</p><p>At re:Invent 2018 AWS announced the Firecracker microVM. A lightweight hypervisor written in Rust, used by AWS Fargate and AWS Lambda. Under the hood AWS Fargate borrows a lot of the concepts from Kata Containers and the original Hyper.sh platform. An OCI compliant container runtime on top of a lightweight VM, albeit with a tech stack they’ve created.</p><p>In a full circle moment, Kata Containers now supports the Firecracker microVM, and Ant Financial Group, with the old Hyper.sh engineering team, are<a href="https://medium.com/kata-containers/kata-containers-version-2-0-e45df4dd328"> using it today</a>.</p><p>I predict AWS Fargate is the future of container infrastructure. For the same reasons that EC2 displaced VMware’s vSphere as the VM platform of choice, Fargate will become the container platform of choice, displacing Kubernetes. It provides all the security of a VM, with the benefits of a container, with none of the management of an orchestration platform.</p><p><em>Originally published at </em><a href="https://interrupt.dev/reinvent-revisited-aws-fargate/"><em>https://interrupt.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87d0980eb2d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interruptdev/re-invent-revisited-aws-fargate-87d0980eb2d0">re:Invent Revisited — AWS Fargate</a> was originally published in <a href="https://medium.com/interruptdev">Interrupt by Senzo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[re:Invent Revisited — AWS AppSync]]></title>
            <link>https://medium.com/interruptdev/re-invent-revisited-aws-appsync-281ff7cb69c3?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/281ff7cb69c3</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[appsync]]></category>
            <category><![CDATA[graphql-vs-rest]]></category>
            <category><![CDATA[aws-appsync]]></category>
            <category><![CDATA[graphql]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 00:15:35 GMT</pubDate>
            <atom:updated>2020-11-25T00:15:35.435Z</atom:updated>
            <content:encoded><![CDATA[<h3>re:Invent Revisited — AWS AppSync</h3><h4>In 2017 the best session I saw at re:Invent was on a Twitch stream I watched while sitting on the floor waiting in a queue. It was the launch of AWS AppSync.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XnEKzAkoqx2ID9JT_PZK5A.jpeg" /></figure><p>The volume of product announcements at re:Invent is huge. In the first few years of re:Invent product announcements were made during one of the keynotes from Andy Jassy or Werner Vogels. I think it was the 2014 re:Invent that they started to push smaller announcements to Jeff Barr’s blog in the days leading up to re:Invent.</p><p>By 2017, they had created the re:Invent Launchpad. A Twitch stream that ran throughout the conference to launch products that didn’t make a keynote, or go into more detail on products announced in the keynote. It was at the re:Invent Launchpad that AWS AppSync launched.</p><p>You can watch the launch here, featuring <a href="https://twitter.com/taraw">Tara Walker</a> and <a href="https://twitter.com/undef_obj">Richard Threlkeld</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fza6J9Zsp1vM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dza6J9Zsp1vM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fza6J9Zsp1vM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1d8a23e4bf007e15738aa0e67b9ffd80/href">https://medium.com/media/1d8a23e4bf007e15738aa0e67b9ffd80/href</a></iframe><p>I remember watching this launch live on Twitch, whilst sitting on the floor waiting in the queue to get into a re:Invent session. I loved this style of launch because they went into more depth than you could ever go into a keynote trying to launch 10 products in 2 hours. I was surprised at the time it didn’t make the keynote, and considering how much AppSync has grown I’m even more surprised now.</p><p>At its core AppSync is a managed GraphQL service. GraphQL was developed by Facebook engineers in 2012, and released as an Open Source project in 2015. GraphQL has quickly become the preferred way for web and mobile developers to interface with backend systems.</p><p>For the front-end developer GraphQL simplifies development. On the backend however, implementing a scalable GraphQL API yourself does not have the same ease. AppSync takes away the pain of running a GraphQL API, and has introduced AWS to a whole new generation of front-end developers.</p><p>In the early days of AWS, they supported SOAP and REST API’s. In his 2006 interview with ACM, Werner Vogels talked about how a small group of REST evangelists used AWS’s REST APIs.</p><blockquote>“A small group of REST evangelists continue to use the Amazon Web Services numbers to drive that distinction, but we find that developers really just want to build their applications using the easiest toolkit they can find.”<em> — Werner Vogels, “A conversation with Werner Vogels” ACM Queue 30 June 2006, </em><a href="https://queue.acm.org/detail.cfm?id=1142065"><em>https://queue.acm.org/detail.cfm?id=1142065</em></a></blockquote><p>In 2006 REST was the new interface standard popular with PHP developers driving the web revolution at the time. In 2020 GraphQL is the interface of choice with the new wave of developers rewriting the web in JavaScript.</p><p>AppSync is bringing a new generation of web developers into AWS, dramatically reducing the time and effort to design, deploy and run GraphQL APIs at scale. For this new generation of developers, it will be completely normal for a single developer to create and run an application end to end by themselves.</p><p>For experienced serverless hands like<a href="https://twitter.com/theburningmonk/"> Yan Cui</a>, AppSync takes the Serverless paradigm to the next level. In 2016 he was part of a team that<a href="https://theburningmonk.com/2016/12/yubls-road-to-serverless-architecture-part-1/"> built a serverless social network using API Gateway and Lambda in 6 months</a>. In 2020 he<a href="https://theburningmonk.com/2020/11/how-i-built-a-social-network-in-4-weeks-with-graphql-and-serverless/"> built a social network by himself in 4 weeks using AppSync</a>.</p><p>For 2020 I’d like to see</p><ul><li>Greater language support for GraphQL resolvers beyond the current use of Velocity Template Language</li><li>Schema Federation to allow multiple development teams to work on their own schema but publish a single federated schema via a single AppSync endpoint</li><li>PCI DSS compliance to allow the use of AppSync in card payment environments</li><li>Custom Authorizers that mimic the API Gateway Lambda Custom Authorizers</li></ul><p>I expect to see AppSync’s usage to accelerate as a broader feature set enables it to appeal to a wider audience. The AppSync team have done a great job pushing the “do more with less” paradigm, and I expect this service has only just started on it’s growth trajectory.</p><p><em>Originally published at </em><a href="https://interrupt.dev/reinvent-revisited-aws-appsync/"><em>https://interrupt.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=281ff7cb69c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interruptdev/re-invent-revisited-aws-appsync-281ff7cb69c3">re:Invent Revisited — AWS AppSync</a> was originally published in <a href="https://medium.com/interruptdev">Interrupt by Senzo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[re:Invent Revisited — The Amazon Builders Library]]></title>
            <link>https://medium.com/interruptdev/re-invent-revisited-the-amazon-builders-library-f92663ca95a?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f92663ca95a</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[awsreinvent]]></category>
            <category><![CDATA[awsreinvent2020]]></category>
            <category><![CDATA[reinvent]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Tue, 24 Nov 2020 11:14:14 GMT</pubDate>
            <atom:updated>2020-11-24T11:14:14.154Z</atom:updated>
            <content:encoded><![CDATA[<h3>re:Invent Revisited — The Amazon Builders Library</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9mtge36rHh8dhD7PtT9ezw.jpeg" /></figure><p>We’re kicking off a week of looking back at announcements from previous re:Invents, as we build up to re:Invent 2020. We’re starting with one of my favourite announcements of re:Invent 2019, the Amazon Builders’ Library.</p><p>Amazon and AWS have been very closed about how they build things. Werner Vogels has shared some insights up on stage during his keynotes over the years. Occasionally a research paper appears ( <a href="https://www.allthingsdistributed.com/files/amazon-dynamo-sosp2007.pdf">The Dynamo Paper</a>,<a href="https://www.usenix.org/conference/nsdi20/presentation/brooker"> Millions of Tiny Databases</a>). Historically though, they haven’t shared much about how they build systems.</p><p>The lessons from building the Amazon platform over the previous 24 years had been to a large extent kept out of sight. This<a href="https://queue.acm.org/detail.cfm?id=1142065"> 2006 interview</a> with Werner is one of the best examples of Amazon sharing, albeit at a high level, how they operate. It’s been too rare an act of sharing. Amazon were very early adopters of service orientated architecture, they used small autonomous teams, adopted asynchronous processing through the use of queues, and many more. All before the general tech community had given these concepts the names we now use.</p><p>The Amazon Builders’ Library announcement changed that. It’s a collection of technical articles on how AWS builds systems. It’s written by AWS’s engineering team building the systems that run AWS. It was even<a href="https://news.ycombinator.com/item?id=21714209"> positively received on Hacker News</a>.</p><p>It gives consumers of AWS services a look at some of the design decisions behind the services they use everyday.This helps in many ways. It helps you understand how the services you consume work and where their boundaries are. It helps you learn architectural patterns and techniques you can apply in your own architecture.</p><p>It also helps AWS establish their tech credentials, which is good for hiring, and gives customers a warm fuzzy feeling that they’re working for a partner that lives up to their own marketing.</p><p>The pace at which its updated with new articles since launch has been slow. To date, it hosts 17 written articles and 6 videos. I assume this slower pace of release is a byproduct of using a small pool of principal engineers who write the articles, combined with the fact that the Builders’ Library is not their core role.</p><p>My hope for 2021 and the Amazon Builders’ Library is for an expanded pool of engineers writing articles giving us a deeper view of other parts of the AWS platforms, and for AWS clients to start publishing similar quality technical articles.</p><p>The Builders’ Library goes deep in a limited number of areas, but expanding width of areas it goes deep into, the more invaluable it will become.</p><p>Check it out here.<a href="https://aws.amazon.com/builders-library"> https://aws.amazon.com/builders-library</a>.</p><p><em>Originally published at </em><a href="https://interrupt.dev/reinvent-revisited-the-amazon-builders-library/"><em>https://interrupt.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f92663ca95a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interruptdev/re-invent-revisited-the-amazon-builders-library-f92663ca95a">re:Invent Revisited — The Amazon Builders Library</a> was originally published in <a href="https://medium.com/interruptdev">Interrupt by Senzo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Containers + Serverless: Cloud Native Bimodal — Interrupt by Senzo]]></title>
            <link>https://medium.com/interruptdev/containers-serverless-cloud-native-bimodal-interrupt-by-senzo-5875640d1914?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5875640d1914</guid>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Tue, 24 Nov 2020 11:10:19 GMT</pubDate>
            <atom:updated>2020-11-24T11:10:58.443Z</atom:updated>
            <content:encoded><![CDATA[<h3>Containers + Serverless: Cloud Native Bimodal</h3><p>Around 2015, Gartner started to promote the idea of a bimodal IT organisation, with mode 1 effectively being ‘as is’ operations for existing infrastructure, and mode 2 being newer, modern, agile techniques and platforms.</p><p>A bimodal approach has the effect of promoting the idea that legacy infrastructure and operations are sufficient for existing systems, whilst supporting the innovation lab movement, which for most corporations is <a href="https://hbr.org/2019/10/why-companies-do-innovation-theater-instead-of-actual-innovation">innovation theatre</a>, at a hefty cost with little return. This approach prevents any real change in organisations, and in a world where the majority of IT budgets are spent on maintenance of existing infrastructure, it does little reduce that.</p><p>In the Gartner definition of Bimodal, the use of container and serverless technologies would be in the mode 2 operations bucket. That’s where new agile platforms and associated operational practices are used for new initiatives. Real world use tells a different story. The organisations reaping the most benefit from cloud platforms and agile operations are those that go all in.</p><h3>Two case studies that prove big doesn’t mean hamstrung</h3><p>Nordstrom, the 119 year old, $15 billion-a-year revenue retailer publicly stated they were going all in on AWS in 2015. Initially, they started down the route of many organisations moving to AWS, implementing automation and tools like Chef to automate their VMs in the cloud. At the same time container and serverless technologies were emerging. Nordstrom adopted both. Their first foray into containers was their homegrown container management solution, which has since been <a href="https://kubernetes.io/case-studies/nordstrom/">superseded by Kubernetes</a>. They’ve achieved significant agility, with faster deploys and greater developer independence, whilst reducing their EC2 bill with AWS. Containers helped drive efficiency in their existing applications, without a major refactor. At the same time they were pioneering event driving architectures using serverless technologies, bringing new capabilities to the business. Doing all of this with a singular operational model of small teams, and developers pushing code to production via git-based workflows.</p><p>By using a singular operational model, container based platforms to drive efficiency and agility in existing applications, and serverless platforms to take advantage of new event driven paradigms, Nordstrom is able to be more responsive to its business needs whilst reducing costs, improving reliability and agility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*r9mxQtY2xyoxoYrSoG59wQ.png" /><figcaption>Jeff Dowds, IT Executive at Vanguard showing a high level view of the Vanguard infrastructure at re:Invent 2019</figcaption></figure><p>Nordstrom is far from alone in this. Vanguard, the 45 year old fund manager with $6.2 trillion assets under management, <a href="https://aws.amazon.com/solutions/case-studies/vanguard-case-study/">got up on stage</a> at re:Invent 2019 to talk about their migration to AWS. The migration enabled them to <em>“reduce the cost of computing 30 percent and deploy workloads up to 20 times faster, as well as improve resiliency and innovate quickly”. </em>Like Nordstrom, Vanguard adopted a singular operational model, using containers (in the form of AWS Fargate) to drive efficiency in their existing applications, and leverage the event-driven nature of serverless platforms for stream processing.</p><p>These organisations are hardly alone. DataDog’s <a href="https://www.datadoghq.com/state-of-serverless/">State of Serverless</a> report found that 80% of AWS customers they surveyed who are using containers also used AWS Lambda. Containers + serverless is the norm, not the exception.</p><p>This is the cloud native pattern that works. A singular operational model with small empowered teams. Containers to drive efficiency in your existing applications, and Serverless architectures to become event driven.</p><h3>Why use both?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/0*ahRWN-leXS2gYo0E.png" /></figure><p>Why is this the model? Why not use containers for everything? Why not serverless all the things? Why not different operational models for the different areas?</p><p>A singular operational model is key. The DevOps Research Agency (DORA) in its annual State of DevOps report identifies organisations into four clusters of operational practices: low, medium, high and elite. The organisations that are successfully achieving the outcomes of improved efficiency and agility whilst reducing costs share the same characteristics of high and elite performers. The 2018 DORA State of DevOps report found that an elite performer’s use of cloud was 23x more likely to meet the five cloud characteristics of on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service as identified in the NIST definition of cloud. The 2019 report found this had grown to 24x more likely. Essentially, elite performers were significantly more likely to fully utilise the cloud.</p><p>By adopting the practices of an elite performing organisation you will be in a better place to leverage container and serverless cloud native platforms.</p><p>The decision when to use a container or a serverless platform has some nuance to it. Containers are a great place to replatform existing applications. They give you isolation, a portable image format, and great resource efficiency; all of which can be achieved without rewriting any application code.</p><p>Serverless applications on the other hand give you all those same benefits, but to a greater extent, combined with the advantage of being truly event driven and pay per use, with the caveat that the application model will require a refactor in most cases.</p><p>Serverless applications have a lower cost and operational overhead than any other model, but they come with the cost of significant change. When it comes to migration, the tension between these factors comes into play with containers often winning because the cost of change to serverless outweighs the benefit. Serverless migrations are most common when there is another driver to refactor an application beyond replatforming for efficiency.</p><p>Cloud Native Bimodal is a strategy to leverage containers and serverless cloud platforms under a singular operational model, to drive agility and efficiency to better meet the needs of the organisation.</p><p>Containers allow you to migrate quickly, serverless allows you to push your architecture further. Cloud Native Bimodal will dramatically improve the ability of your technology investment to meet your business needs.</p><p><em>Originally published at </em><a href="https://interrupt.dev/containers-serverless-cloud-native-bimodal/"><em>https://interrupt.dev</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5875640d1914" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interruptdev/containers-serverless-cloud-native-bimodal-interrupt-by-senzo-5875640d1914">Containers + Serverless: Cloud Native Bimodal — Interrupt by Senzo</a> was originally published in <a href="https://medium.com/interruptdev">Interrupt by Senzo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Statement regarding Stackery & ServerlessDays]]></title>
            <link>https://medium.com/@iamstan/statement-regarding-stackery-serverlessdays-e5bd3d8786e5?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5bd3d8786e5</guid>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Fri, 08 Mar 2019 15:05:10 GMT</pubDate>
            <atom:updated>2019-03-08T15:05:10.447Z</atom:updated>
            <content:encoded><![CDATA[<p>On 5 March 2019 Geekwire <a href="https://www.geekwire.com/2019/former-spouses-allegations-portland-startup-ceo-ripple-tech-community/">published a story</a> detailing alleged abuse by Stackery CEO Nate Taggart of his former spouse Kate Taggart.</p><p>Stackery is an active member of the Serverless community and has been involved in previous ServerlessDays events. They were involved in the organisation of ServerlessDays Portland and sponsored a number of ServerlessDays events globally.</p><p>The global leadership team of ServerlessDays is still evaluating the situation, and will be forming a separate committee to advise on any further course of action. Whilst this is happening we have decided to stand in solidarity with PDX Women in Tech, and have asked Stackery to withdraw from all ServerlessDays involvement at this time. They have agreed and will be releasing their own statement.</p><p>We are taking outside advice, and will wait on recommendations from the committee we are forming to investigate this matter before proceeding with any other action.</p><p>We will not be issuing any further comment on this at this point in time.</p><p>Regards,</p><p>Ant Stanley on behalf of the ServerlessDays global organising team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5bd3d8786e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TypeScript, ES Modules & Micheal Jackson]]></title>
            <link>https://medium.com/@iamstan/typescript-es-modules-micheal-jackson-2040216be793?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2040216be793</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[es2015]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Tue, 05 Feb 2019 22:15:38 GMT</pubDate>
            <atom:updated>2019-02-05T22:15:38.508Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/427/1*xuB4KIOK0dc67c1DphuCMw.jpeg" /><figcaption><a href="https://www.flickr.com/photos/104869787@N03/10184066544/">https://www.flickr.com/photos/104869787@N03/10184066544/</a> (CC BY 2.0)</figcaption></figure><p>ECMAScript Modules were introduced with the ES2015 specification for ECMAScript and is the modern module system for JavaScript.</p><p>Node’s module system, CommonJS, predates ES Modules, and was created out of the need for module system in Node. In September 2017, Node.js added support for ES modules, alongside CommonJS modules, with the release of Node.js 8.5, using the .mjs (Micheal Jackson Script) extension to differentiate ES modules from CommonJS modules.</p><p>TypeScript has had some ES module support for a while, and at a high level appears it would be simple to update your tsconfig.json to target ES2015 as the output syntax if you were using ES module syntax in your TypeScript.</p><p>The reality is slightly different as TypeScript does not transpile to .mjs files, and due to the way it handles ES modules there are some limitations on the syntax you use. Essentially TypeScript treats ES modules the same as CommonJS modules, even though they are different</p><p>Below is a brief list of what to watch out for if you want to export .mjs files that will run in Node.js …</p><p>1.) TypeScript cannot transpile to .mjs files.</p><p><em>Workaround: </em>Transpile to ES2015 target, and use a post compile script to rename the files to .mjs from .js</p><p>The command below works in any POSIX based OS using Bash that supports the find and mv commands.</p><pre>find ./dist/ -name &quot;*.js&quot; -exec bash -c &#39;mv &quot;$1&quot; &quot;${1%.js}&quot;.mjs&#39; - &#39;{}&#39; \;</pre><p>Github Issue on .mjs support: <a href="https://github.com/Microsoft/TypeScript/issues/18442">https://github.com/Microsoft/TypeScript/issues/18442</a></p><p>2.) TypeScript cannot import .mjs files.</p><p><em>Workaround:</em> There is none. Unfortunately you can’t do it today. You can import .ts files written with ES2015 syntax though.</p><p>3.) TypeScript allows the use of CommonJS require() and ES module import syntax in the same module. Node.js does not.</p><p><em>Workaround:</em> Ensure any TypeScript you write only uses ES module syntax. You should rewrite any instances of require() syntax to use import() syntax.</p><p>4.) ES modules in Node.js doesn’t support __dirname or __filename statements. The import.meta.url syntax is intended to provide similar functionality to __filename when using ES modules in Node.js as the alternative. TypeScript supports import.meta syntax, but allows __filename and __dirname to be used in files that are exported to ES modules</p><p><em>Workaround: </em>Ensure you use import.meta.url syntax instead of __filename and __dirname</p><p>Github PR to introduce support for import.meta : <a href="https://github.com/Microsoft/TypeScript/pull/23327">https://github.com/Microsoft/TypeScript/pull/23327</a></p><p>5.) ES modules are read-only. TypeScript allows you to mutate ES modules, which will create an error</p><p><em>Workaround:</em> Ensure you don’t attempt to change an ES module after it’s imported.</p><p>This post focuses mainly on where TypeScript allows you to ship code that won’t run in Node.js. I recommend reading my other blog post on tips for using ES modules<a href="https://medium.com/@iamstan/tips-for-writing-es-modules-in-node-js-96ec688615a4">, https://medium.com/@iamstan/tips-for-writing-es-modules-in-node-js-96ec688615a4,</a> if you want to have a greater understanding of how to write ES modules if you’re used to CommonJS.</p><p>The biggest issue with transpiling TypeScript to ES modules is that TypeScript treats ES module syntax as another way of doing the same thing as CommonJS, when fundamentally under the hood CommonJS and ES modules are different.</p><p>TypeScript allows mixing and matching of CommonJS and ES module syntax which will always fail when running in Node.js because they are distinct module systems, and Node uses the file extension to determine which module system to use before parsing the file, so will only ever load one or the other module system.</p><p>This is a great deep dive to read on ES modules, including how they differ to CommonJS under the hood. <a href="https://hacks.mozilla.org/2018/03/es-modules-a-cartoon-deep-dive/">https://hacks.mozilla.org/2018/03/es-modules-a-cartoon-deep-dive/</a></p><p>Hope this is useful!</p><p>Ant Stanley</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2040216be793" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips for writing ES modules in Node.js]]></title>
            <link>https://medium.com/@iamstan/tips-for-writing-es-modules-in-node-js-96ec688615a4?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/96ec688615a4</guid>
            <category><![CDATA[es6]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[es2015]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Mon, 04 Feb 2019 13:53:50 GMT</pubDate>
            <atom:updated>2019-02-05T22:11:56.618Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*58yeMDhXI_3A98nqfvFa4w.jpeg" /><figcaption><a href="https://www.flickr.com/photos/blachswan/15174190641">https://www.flickr.com/photos/blachswan/15174190641</a> (CC By 2.0)</figcaption></figure><p>Recently I’ve been working a bit with ES modules within Node.js. I’ve found documentation and blog posts to be a little patchy with some detail, but not all, and docs all over the place. So this post is essentially everything I’ve learnt about using ES modules within Node.js, transitioning from CommonJS, all in one place.</p><p>EcmaScript Modules were defined in the ES2015 specification introduced in June 2015. They were first introduced to Node.js in September 2017 behind the --experimental-modules flag and is due be supported without the flag in 2020. There are a number of benefits of ES modules, namely</p><ul><li>A universal module system between browsers and Node.js.</li><li>Static code analysis enabling tree-shaking of ES modules using bundling frameworks like Rollup and Webpack. Ship just the code used in your application.</li></ul><p>Node.js will maintain a level of compatibility between CommonJS and ES modules. This post helps to provide useful tips on writing ES modules, for those used to writing CommonJS modules.</p><p>There are a number of differences between CommonJS and ES modules that need to be understood. Key differences are</p><ul><li>ES modules use .mjs files, CommonJS uses .js files. Node.js uses the file extension to determine which module system to load.</li><li>ES modules are statically imported vs CommonJS modules are dynamically imported.</li><li>Node.js’s resolution algorithm will import the .mjs version of a module before a .js version, if two versions with the same name exist.</li><li>You can import modules using a URL path</li><li>CommonJS brings modules in as a module object. Essentially a normal JavaScript Object you can mutate and basically treat as a normal object. ES modules it doesn’t bring the module in as a normal JavaScript Object, with some limitations on how you interact with an ES module.</li></ul><p>Below are some tips for writing ES modules in Node.js if you’re used to CommonJS modules.</p><h4>Statically importing modules</h4><p>The import module from &#39;module&#39; syntax brings in the module globally and read-only. This changes the way you use them in a few ways.</p><ul><li>All of your import module from &#39;module&#39; statements must be at the top of your module/script</li><li>You cannot mix and match CommonJS and ES module syntax in the same module/script. Basically if it’s a .mjs file, make sure there are require() statements in your code.</li><li>An ES module can import a CommonJS module. Be aware of how the relevant modules export methods and properties and the way they are imported are subtly different in each case. To expand on the example in this <a href="https://medium.com/the-node-js-collection/an-update-on-es6-modules-in-node-js-42c958b890c">post,</a> if you have the following code</li></ul><pre>//foobar.js<br>function foo() {<br>  return &#39;bar&#39;;<br>}</pre><pre>function bar() {<br>  return &#39;foo&#39;;<br>}</pre><pre>module.exports.foo = foo;<br>module.exports.bar = bar;</pre><p>You could reference it in a CommonJS module like this</p><pre>//app.js<br>const { foo, bar } = require(&#39;foobar&#39;);<br>console.log(foo(), bar());</pre><p>and the equivalent in ES modules to reference the same CommonJS module, foobar.js, would be</p><pre>//app.mjs<br>import { foo, bar } from &#39;foobar&#39;<br>console.log(foo(), bar());</pre><p>Whilst the syntax looks similar, what is happening is slightly different. In the CommonJS example, the line const { foo, bar } = require(&#39;foobar&#39;) is using Object destructuring to extract the foo and bar objects from require(&#39;foobar&#39;). In the ES module example, the import { foo, bar } from &#39;foobar&#39; syntax is directly importing the named exports foo and bar.</p><p>The CommonJS syntax is basically doing this.</p><pre>const foobar = require(&#39;foobar&#39;)<br>const { foo, bar } = foobar<br>console.log(foo(), bar());</pre><p>The CommonJS syntax is using two steps to create the foo and bar objects vs the ES module syntax which does it in one step.</p><p>Key to understanding how to use CommonJS modules within ES modules is to understand how default and named exports work. To expand on the above example, if you used the following syntax</p><pre>//app.mjs<br>import foobar from &#39;foobar&#39;<br>const { foo, bar } = foobar<br>console.log(foo(), bar());</pre><p>You would get an error. The reason is that the CommonJS module, foobar.js, does not have a default export. To bring the relevant methods in from foobar.js you would either bring them in by name, as the initial working example does, or you would import them under a single namespace like this.</p><pre>//app.mjs<br>import * as foobar from &#39;foobar&#39;<br>const { foo, bar } = foobar<br>console.log(foo(), bar());</pre><p>The * operator references all the methods and properties exported by foobar.js and the as foobar creates a module namespace called foobar that you can use to reference individual methods.</p><p>The import module from &#39;module&#39; syntax can only be used when the module being imported has a default export.</p><ul><li>You can’t reference any methods, properties or objects of the imported module within the import statement. So code like this</li></ul><pre>const version = require(&#39;./package.json&#39;).version</pre><p>needs to be rewritten like this</p><pre>import * as pkg from `./package.json`<br>const version = pkg.version</pre><ul><li>ES modules are read-only, so you can’t mutate them once imported. Syntax like this which works in CommonJS.</li></ul><pre>const module = require(&#39;./module&#39;)<br>const func = () =&gt; { return &#39;this is a function&#39; }<br>Object.assign(module, func)</pre><p>versus the ES module equivalent</p><pre>import module from &#39;module&#39;<br>const func = () =&gt; { return &#39;this is a function&#39; }<br>Object.assign(module, func)</pre><p>The CommonJS example will work, the ES module example will fail. If you use this pattern you’ll need to figure out another way to achieve what you want.</p><h4>Exporting Modules</h4><p>The way you export functions, methods and objects with ES modules changes slightly. The biggest change is the introduction of an explicit default export with the export default syntax.</p><p>With ES modules default and named exports can co-exist. For example.</p><pre>//foobar.mjs</pre><pre>function foo() {<br>  return &#39;bar&#39;;<br>}</pre><pre>function bar() {<br>  return &#39;foo&#39;;<br>}</pre><pre>export { foo }<br>export default bar</pre><p>The example above has a named export foo and a default export bar, so to import them you can use the code below</p><pre>//app.mjs<br>import { foo } from &#39;foobar&#39;<br>import foobar from &#39;foobar&#39;</pre><pre>console.log(foo()); // &#39;bar&#39;<br>console.log(foobar()); // &#39;foo&#39;</pre><p>This example imports foo as a module called foo and imports bar as a module called foobar. A more useful example might be where you export a class as the default export, and helper methods as named exports on their own.</p><p>If you tried to do this with CommonJS modules and the module.exports syntax, the exports would override each other. For example</p><pre>//app.js<br>function foo() {<br>  return &#39;bar&#39;;<br>}</pre><pre>function bar() {<br>  return &#39;foo&#39;;<br>}</pre><pre>module.exports.foo = foo;<br>module.exports = bar;</pre><p>And the corresponding import with require()</p><pre>const { foo } = require(&#39;foobar&#39;); //will create an error<br>const foobar = require(&#39;foobar&#39;)</pre><pre>console.log(foo()); // Error!!<br>console.log(foobar()); // &#39;foo&#39;</pre><p>In the above CommonJS example, in the line module.exports = bar the previous object module.exports.foo is overwritten and isn’t exported so will error if referenced in an import.</p><p>Another useful feature of ES modules exports is the ability to export directly from an imported module. For example you can write the following</p><pre>export { foo } from &#39;foobar&#39;</pre><p>Which is the ES module equivalent of the CommonJS code below.</p><pre>const { foo } = require(&#39;foobar&#39;)<br>module.exports.foo = foo</pre><p>On the whole, ES module exporting is more flexible and explicit.</p><h4>Working with files in ES modules</h4><p>The way you reference and work with files in ES modules changes.</p><p>The __filename and __dirname statments don’t work in ES modules. For the equivalent operation you need to use import.meta.url syntax. So code that would be written like this in CommonJS</p><pre>console.log(`Current file is ${__filename}`);<br>console.log(`Current directory is ${__dirname}`);</pre><p>Would need to be rewritten like this in ES modules</p><pre>const currentFile = import.meta.url;<br>const currentDirectory = new URL(import.meta.url).pathname;</pre><pre>console.log(`Current file is ${currentFile}`);<br>console.log(`Current directory is ${currentDirectory}`);</pre><p>The key difference is that import.meta.url brings the filename in a URL format, so using file:// to reference the file. This syntax is currently in <a href="https://github.com/tc39/proposal-import-meta/#importmeta">stage 3 of the TC39 process</a> and is a JavaScript implementation, not Node.js specific. So code written using this syntax can be used in both the browser and Node.js.</p><p>In general you should start using the new Node.js implementation of the URL WHATWG URL API, <a href="https://nodejs.org/dist/latest-v11.x/docs/api/url.html">defined in the Node docs here,</a> for file and path operations. The Node.js Path and File modules still work with ES modules, but you can also use the new URL implementation for working with files. At this point ES module syntax in Node.js only works with URLs using file://, though the spec does support all URLs, so hopefully down the line we’ll be able import modules via a remote URL in Node.</p><h4><strong>Dynamic Imports with ES modules</strong></h4><p>Whilst ES modules are statically imported, there is the ability to dynamically import ES modules using the import() syntax. This syntax is also at <a href="https://github.com/tc39/proposal-dynamic-import">stage 3 of the TC39 process</a>, and is supported by Node.js behind the --experimental-modules flag.</p><p>The import() syntax is function-like, and can be used very similarly to the require() syntax. It dynamically imports ES modules, versus require() which can only import CommonJS modules.</p><p>The reality is that you don’t often need to dynamically load JavaScript modules, a common use case is the hot loading of generated code within an application, but in most instances where you use a module, statically importing it is preferable.</p><p>The key thing to be aware of with the import() syntax is how to reference the exported methods and objects. If you have a module like below</p><pre>//foobar.mjs<br>function foo() {<br>  return &#39;bar&#39;;<br>}</pre><pre>function bar() {<br>  return &#39;foo&#39;;<br>}</pre><pre>export { foo, bar };</pre><p>It has two named exports, foo and bar, which can be imported dynamically like this</p><pre>//app.mjs</pre><pre>const currDir = new URL(import.meta.url).pathname<br>const fooBarLocation = new URL(currDir, &#39;/foobar.mjs&#39;)<br>const foobar = import(fooBarLocation) //full path to foobar.mjs file</pre><pre>console.log(foobar.foo(), foobar.bar());</pre><p>You need to reference the full path to the module you are importing dynamically. The above example uses the new URL implementation to get the current file location and to join that with the relative path of the module, and will work in Node.js and in the browser.</p><p>Now lets say you have a module that has a default export, there is a slight difference in the way it is imported, namely default exports will be imported under the .default namespace, so like this.</p><pre>//foobar.mjs<br>function foobar() {<br>  return &#39;foobar&#39;;<br>}</pre><pre>export default foobar;</pre><p>Dynamically imported like this</p><pre>const currDir = new URL(import.meta.url).pathname<br>const fooBarLocation = new URL(currDir, &#39;/foobar.mjs&#39;)<br>const foobar = import(fooBarLocation) //full path to foobar.mjs file</pre><pre>console.log(foobar.default());</pre><p>When dynamically importing ES modules with default exports just remember that you reference the default export using module.default not module.</p><p>It also should be noted, that if you dynamically import ES modules using import() any static code analysis or tree shaking won’t work on those dynamically imported modules.</p><h4>Package.json and shipping ES modules?</h4><p>So what happens with package.json with ES modules? The agreed specification is that you still use main to specify your entry point to your ES module. Bundlers like Rollup and Webpack used module to specify a separate entry point before Node support ES modules.</p><p>Now under the --experimental-modules flag you can specify an .mjs file under main in package.json or don’t specify a file extension at all and Node.js’s resolution algorithm with look for a .mjs file before a .js file.</p><p>This allows you to do a dual export of CommonJS and ES modules for backwards compatibility with older versions of Node.js, or for developers that don’t won’t to use ES modules just yet.</p><p>An example package.json that exports both CommonJS and ES modules and uses Babel for transpiling would look like this.</p><pre>{                         <br>  &quot;name&quot;: &quot;dualexport-module&quot;,                         <br>  &quot;version&quot;: &quot;1.0.0&quot;,                         <br>  &quot;description&quot;: &quot;An example of a module exported with CJS and ESM.&quot;,                         <br>  &quot;license&quot;: &quot;MIT&quot;,                         <br>  &quot;main&quot;: &quot;index&quot;,                         <br>  &quot;module&quot;: &quot;index.mjs&quot;,                                               <br>  &quot;engines&quot;: {&quot;node&quot;: &quot;&gt;= 6.x&quot;},<br>  &quot;scripts&quot;: {<br>    &quot;build&quot;: &quot;npm run build:cjs &amp;&amp; npm run build:mjs&quot;,<br>    &quot;build:js&quot;: &quot;babel src&quot;,<br>    &quot;build:cjs&quot;: &quot;npm run build:js -- --env-name cjs --out-dir dist/&quot;,                           <br>    &quot;build:mjs&quot;: &quot;npm run build:js -- --env-name mjs --out-dir dist/module &amp;&amp; for file in $(find dist/module -name &#39;*.js&#39;); do mv \&quot;$file\&quot; `echo \&quot;$file\&quot; | sed &#39;s/dist\\/module/dist/g; s/.js$/.mjs/g&#39;`; done &amp;&amp; rm -rf dist/module&quot;,                           },                           <br>  &quot;dependencies&quot;: {},<br>  &quot;devDependencies&quot;: {}                       <br>}</pre><p>In this example main just specifies index without an extension. If you execute this package with --experimental-modules flag it will look for the .mjs version first, if you execute it without the flag, it will look for the .js version and ignore the .mjs version completely.</p><p>The package.json also has 4 build scripts</p><ul><li>&quot;build:js&quot; runs Babel against the src folder</li><li>&quot;build:cjs&quot; runs the build:js script setting a build environment variable to cjs to tell Babel to export CommonJS modules to dist/</li><li>&quot;build:mjs runs the build:js script setting a build environment variable to mjs to tell Babel to export ES modules for dist/module then runs the find command to file all .js files in dist/module and then moves them to dist whilst renaming them from .js to .mjs</li></ul><p>This uses Babel to do the transformation source code written using ES modules, and using the .mjs extension to a CommonJS and ES module version that can be consumed by either module system.</p><p>The .babelrc.js configuration that goes along with this package.json looks like this</p><pre>module.exports = { <br>  presets: [<br>    [&#39;@babel/preset-env&#39;, { targets: [&#39;node 6&#39;] }],<br>  ],<br>  plugins: [<br>    [&#39;@babel/plugin-transform-classes&#39;, { loose: true }],<br>    [&#39;@babel/plugin-transform-destructuring&#39;, { loose: true }],<br>    [&#39;@babel/plugin-transform-spread&#39;, { loose: true }],<br>    [&#39;@babel/plugin-syntax-dynamic-import&#39;],<br>    [&#39;@babel/plugin-syntax-import-meta&#39;]<br>  ],<br>  env: { <br>    cjs: { <br>      presets: [<br>        [&#39;@babel/preset-env&#39;, { modules: &#39;commonjs&#39; }],<br>      ],<br>    },<br>    mjs: {<br>      presets: [<br>        [&#39;@babel/preset-env&#39;, { modules: false }],<br>      ], <br>    },<br>  },<br>};</pre><p>The Babel plugins [&#39;@babel/plugin-syntax-dynamic-import&#39;] and [&#39;@babel/plugin-syntax-import-meta&#39;] have been added specifically to handle the new ES module syntax for import.meta.url and import(). The problem is that these problems allow parsing of the import.meta.url and import() but they don’t transform them, so will bring ES syntax into you CommonJS module, that will fail. The workaround to do this is to handcraft an ES module and CommonJS version of the module using the relevant allowed syntax, and in the CommonJS transpilation config ignore ES module version when transpiling. Extending the above config it would look like this</p><pre>module.exports = { <br>  presets: [<br>    [&#39;@babel/preset-env&#39;, { targets: [&#39;node 6&#39;] }],<br>  ],<br>  plugins: [<br>    [&#39;@babel/plugin-transform-classes&#39;, { loose: true }],<br>    [&#39;@babel/plugin-transform-destructuring&#39;, { loose: true }],<br>    [&#39;@babel/plugin-transform-spread&#39;, { loose: true }],<br>    [&#39;@babel/plugin-syntax-dynamic-import&#39;],<br>    [&#39;@babel/plugin-syntax-import-meta&#39;]<br>  ],<br>  env: { <br>    cjs: { <br>      presets: [<br>        [&#39;@babel/preset-env&#39;, { modules: &#39;commonjs&#39; }],<br>      ],<br>      ignore: [<br>        &#39;src/functionWithImportMeta.mjs&#39;,<br>        &#39;src/functionWithDynamicImport.mjs&#39;,<br>      ]<br>    },<br>    mjs: {<br>      presets: [<br>        [&#39;@babel/preset-env&#39;, { modules: false }],<br>      ], <br>    },<br>  },<br>};</pre><p>This Babel config also assumes that you have written your code using .mjs modules and the transpile configuration triggered by the esm environment variable does no transformation of module syntax.</p><p>The package.json keeps the module as a separate entry point for backwards compatibility reasons, though it’s not strictly needed as Rollup can resolve .mjs files with the correct configuration of rollup-plugin-node-resolve</p><p>This package.json and .babelrc.js is based on the configuration used for the graphql npm module, which from version 14 onwards, is written using ES modules with the .mjs extension and ships both .js and .mjs versions of the module.</p><p>The huge advantage this gives anyone using graphql with a bundler like Rollup is that you can distribute a module with the core GraphQL functionality for a GraphQL server at around 350KB vs the approximately 2.4MB of the entire module with both .mjs and .js versions.</p><h4>ES modules for CLI’s</h4><p>This is very platform dependent, but the general advice is wait for the --experimental-modules flag to be removed before using ES modules in a CLI.</p><p>If you’re using MacOS and you create an executable file in ./bin and reference it properly in package.json and use the #!/usr/bin/env node--experimental-modules shebang for that file, it will work. But it will only work on MacOS, it will not work on any other Linux based operating system. Pain has taught me this.</p><p>The reason is that on Linux systems it will only take one parameter in the shebang, the bit #/usr/bin/env in it, and it won’t read the --experimental-modules flag as that’s a second parameter to the shebang, as node is the first parameter.</p><p>So unless you’re shipping a CLI for MacOS only, make sure you transpile down to CommonJS code.</p><h4>Useful links to read</h4><ul><li><a href="http://2ality.com/2018/12/nodejs-esm-phases.html">ECMAScript modules in Node.js: the new plan</a></li><li><a href="https://hacks.mozilla.org/2018/03/es-modules-a-cartoon-deep-dive/">ES Modules, a cartoon deep-dive</a></li><li><a href="https://medium.com/the-node-js-collection/an-update-on-es6-modules-in-node-js-42c958b890c">An update on ES6 modules in Node.js</a></li><li><a href="https://nodejs.org/api/esm.html">Node.js ESM documentation</a></li><li><a href="https://nodejs.org/api/url.html">Node.js URL documentation</a></li><li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import">MDN ES Module Import documentation</a></li><li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export">MDN ES Module Export documentation</a></li></ul><p>Hopefully you find this useful, and are saved from some of the pain I went through! Getting on top of ES modules now will give you a head start before the --experimental-modules flag is removed, and help with implementation of the specification as potential bugs can be found before the flag is removed.</p><p>Ant Stanley</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96ec688615a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Goodbye JeffConf, hello ServerlessDays!!]]></title>
            <link>https://medium.com/serverless-zone/goodbye-jeffconf-hello-serverlessdays-9ae26791d3f?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ae26791d3f</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Tue, 10 Apr 2018 14:31:03 GMT</pubDate>
            <atom:updated>2018-04-10T15:04:19.763Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XhrSNnnLBHwh8wmJaLIk2g.png" /></figure><p>When <a href="https://medium.com/u/139b9858e816">Paul Johnston</a> wrote his blog post <a href="https://serverless.zone/serverless-is-just-a-name-we-could-have-called-it-jeff-1958dd4c63d7">“Serverless” is just a name. We could have called it “Jeff”</a>, I doubt there was any expectation it would spawn a conference let alone a series. Yet here we are with the <a href="https://hamburg.jeffconf.com/">third JeffConf</a> concluded two months ago.</p><p><a href="https://medium.com/u/139b9858e816">Paul Johnston</a>, <a href="https://medium.com/u/604ac4ebfc5f">James Thomas</a> and myself decided to organise the first JeffConf with 6 weeks notice in June last year, with one of its core principles that it should be a community event, and representative of the broader community.</p><p>As we’ve seen the community take the idea and grow it by organising follow-on conferences in Milan and now Hamburg we realise it is time to say goodbye to JeffConf.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*Hz7nNa8UF3oR4nO14I5P6A.png" /></figure><p>Key to growing the community is creating a space where everyone feels included and welcomed. Unfortunately, by naming a conference JeffConf, we’ve created a space that is more inclusive for people named Jeff, which ultimately is against the aims of the conference. So with that we say goodbye to JeffConf, but not goodbye to Jeff (our happy mascot).</p><p>At JeffConf Hamburg we announced that it would be the last JeffConf, and is now reborn as ServerlessDays</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GYcLVtCTGxapFjd9cizlkg.png" /></figure><p>So what’s a ServerlessDay? It’s exactly that. The original strap line for JeffConf was <strong>“One Day. One Track. One Community”</strong>. ServerlessDays continues with that mantra. The conferences are one day, single track conferences, run by the local community for the local community focusing on serverless technologies.</p><p>Today we’re announcing four ServerlessDays events.</p><ul><li><a href="https://tlv.serverlessdays.io/">ServerlessDays Tel Aviv</a> — 23 May 2018</li><li><a href="https://serverless.org.nz/">ServerlessDays Auckland</a> — 5 June 2018</li><li><a href="https://london.serverlessdays.io/">ServerlessDays London</a> — 6 July 2018</li><li><a href="http://vienna.serverlessdays.io/">ServerlessDays Vienna</a> — 10 October 2018</li></ul><p>CFP’s are open and tickets will go on sale shortly!</p><p><strong>We also want to invite you to help grow the community in your area by running a ServerlessDays or assist an existing organising team!</strong> The ServerlessDays format is loosely based on the popular DevOpsDays conferences and inspired by other community organised conference families like JSConf and BSides.</p><p>There are currently organising teams in place in multiple cities at various stages. If you want to be part of an organising team, potentially sponsor, volunteer or just generally help out email your local team listed below and get involved.</p><h4>Get involved in a ServerlessDays near you!</h4><ul><li>ServerlessDays Auckland — auckland@serverlessdays.io</li><li>ServerlessDays Amsterdam — amsterdam@serverlessdays.io</li><li>ServerlessDays Boston — boston@serverlessdays.io</li><li>ServerlessDays Dublin — dublin@serverlessdays.io</li><li>ServerlessDays Hamburg — hamburg@serverlessdays.io</li><li>ServerlessDays Helsinki — helsinki@serverlessdays.io</li><li>ServerlessDays Hong Kong — hongkong@serverlessdays.io</li><li>ServerlessDays Istanbul — istanbul@serverlessdays.io</li><li>ServerlessDays London — london@serverlessdays.io</li><li>ServerlessDays Milan — milan@serverlessdays.io</li><li>ServerlessDays New York — newyork@serverlessdays.io</li><li>ServerlessDays Portland — portland@serverlessdays.io</li><li>ServerlessDays Seattle — seattle@serverlessdays.io</li><li>ServerlessDays San Francisco — sanfrancisco@serverlessdays.io</li><li>ServerlessDays Tel Aviv — telaviv@serverlessdays.io</li><li>ServerlessDays Toronto — toronto@serverlessdays.io</li><li>ServerlessDays Vienna — vienna@serverlessdays.io</li></ul><p>If you city isn’t listed above and you’re interested in organising a ServerlessDays in your city, then email us at organise@serverlessdays.io</p><p>We’ve created a loose framework to help you run your own and have an existing community of organisers willing to provide guidance and support. If you’re interested in running a ServerlessDays in you area head on over to <a href="https://www.serverlessdays.io/organise">https://www.serverlessdays.io/organise</a> to understand what it’s all about and get in contact with us to make it happen.</p><p>Lastly, but most importantly, we’re not saying goodbye to Jeff! We don’t want to exclude Jeff’s, but rather include everyone. With that spirit Jeff is being joined by some new friends!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jyhp-Y8wkB8xSqp4icVkJg.png" /></figure><p>Jeff’s BFF’s need names, so we’re opening it up to you the community to name them. Submit your name <a href="https://serverlessdays.typeform.com/to/bDnOsJ">suggestions here</a> and we’ll use it to create a shortlist of names to be voted on.</p><p>So good bye JeffConf, you’ve given us a seed. Hello ServerlessDays, we look forward to growing with you.</p><p>Adieu</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ae26791d3f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-zone/goodbye-jeffconf-hello-serverlessdays-9ae26791d3f">Goodbye JeffConf, hello ServerlessDays!!</a> was originally published in <a href="https://medium.com/serverless-zone">Serverless Zone</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From buzzword to meaningful infrastructure option? What’s behind “Serverless”]]></title>
            <link>https://medium.com/serverless-zone/from-buzzword-to-meaningful-infrastructure-option-whats-behind-serverless-fad87f290929?source=rss-ad73a257e53d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fad87f290929</guid>
            <category><![CDATA[openwhisk]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Ant Stanley]]></dc:creator>
            <pubDate>Thu, 25 Jan 2018 22:16:43 GMT</pubDate>
            <atom:updated>2018-01-25T22:16:43.073Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xhXRGhQCAnohQZTIzbjiww.jpeg" /></figure><p>[Interview with <a href="https://medium.com/u/56b578970060">Alex Casalboni</a>, translated from the original German article published at <a href="https://t3n.de/news/jeffconf-2018-hamburg-905965/">https://t3n.de/news/jeffconf-2018-hamburg-905965/</a>]</p><p>JeffConf is a community-focused conference built from and for local serverless communities. It’s a single track, one-day event that moves away from the buzzword in order to foster learning and knowledge sharing across the community as we embrace a new way of building applications.</p><p>JeffConf was launched last year in London and Milan, with more than 300 attendees. This year, JeffConf will take place on February 16 at the Altonaer Museum in Hamburg, Germany.</p><p><strong>Who is Alex?</strong></p><p>Alex is a Software Engineer from Italy. He started building web products as a full stack developer back in 2011, and he joined <a href="https://cloudacademy.com/">Cloud Academy</a> in 2013 as the first employee, where he learned how to successfully build a global product (hundreds of thousands of enterprise teams and professionals learning across 200 countries) and a distributed team (today, more than 70 highly talented individuals across the globe). He is a passionate musician and coder, and enjoys working with machine learning, AI, signal processing, and anything related to math and data science.</p><p>Alex joined the “Serverless Revolution” around <a href="https://blog.alexcasalboni.com/serverless-computing-machine-learning-baf52b89e1b0">early 2016</a>, when he started experimenting with <a href="https://aws.amazon.com/blogs/aws/machine-learning-recommendation-systems-and-data-analysis-at-cloud-academy/">AWS Lambda for Machine Learning applications</a>. He also loves supporting the open-source community by sharing experiments and tutorials and contributing to open projects such as the Serverless Framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*kzYSya0kkM-QUwZwGV3FgA.png" /></figure><p><strong>Who or what is Jeff?</strong></p><p>Jeff is “<em>Serverless.</em>” I think everybody should be like Jeff.</p><p>Jeff represents a community that autonomously formed around a misunderstood name. Indeed, <a href="https://serverless.zone/serverless-is-just-a-name-we-could-have-called-it-jeff-1958dd4c63d7">“Serverless” is just a name</a>, I’d say a provocative name, meant to shake the development community for the sake of marketing.</p><p>Of course, there are still servers (as well as CPU registers, memory allocations, physical network interfaces, etc.), but a lot of smart people really like the idea of not worrying about such underlying details, as long as there is something/someone else that can handle it for you, better than you ever could.</p><p>The word “<em>serverless</em>” was born in a context where running a Python or Node.js piece of code for five seconds required you to launch a compute instance, configure it, patch it, and pay for it by the hour. And, what if this simple piece of code had to run a few hundred times per second or handle unpredictable traffic peaks? Well, that would probably require a cluster of instances and an insane amount of maintenance.</p><p>In this context, we already had third-party APIs and fully managed services to handle authentication, object storage, databases, search, etc., but we missed a new abstraction layer in the compute spectrum that would glue these systems together.</p><p>That’s why <strong>FaaS</strong> (<em>Function as a Service</em>) allowed the community to start a serverless revolution, with the ultimate goal of speeding up the development and prototyping process, while at the same time reducing maintenance costs and effortlessly making most “prototypes” production-ready.</p><p>While organizing JeffConf Milan in Italy, I got in touch with Soenke Ruempler (Co-founder of <a href="https://superluminar.io/">superluminar</a>), who presented an amazing talk in Milan and is now co-organizing <a href="https://hamburg.jeffconf.com/">JeffConf Hamburg</a>. This is how local communities can help each other and grow stronger together. And this is exactly how JeffConfs will keep spreading around the world in 2018 (we have great news coming up pretty soon).</p><p><strong>Can you share some concrete examples or use-cases of companies using Jeff?</strong></p><p>Jeff is a great fit for most use cases that align to <strong>distributed microservices architectures</strong>. Since most serverless platforms come with generous free tiers, Jeff is basically free for prototyping and for low traffic or spiky loads. Once the traffic increases or changes drastically, Jeff will make sure your compute layer scales up or down accordingly, without any change in code.</p><p>For example, you can build <strong>RESTful or GraphQL APIs</strong>, <strong>process file uploads</strong>, <strong>schedule periodic tasks</strong>, implement <strong>webhooks</strong>, build <strong>data processing pipelines</strong>, <strong>integrate third-party services</strong> into legacy architectures, optimize <strong>computation at the edge</strong>, build <strong>IoT or Chatbot applications</strong>, etc. Since serverless functions are always executed in response to an event, you can design a whole <strong>event-based system</strong> where your functions run only when something relevant happens, eventually triggering other functions downstream. In such a system, function orchestration can become a complex problem. That’s where new visual tools such as <a href="https://aws.amazon.com/step-functions/">AWS Step Functions</a> and <a href="https://azure.microsoft.com/en-us/services/logic-apps/">Azure Logic Apps</a> can help.</p><p>Adoption of serverless is steadily increasing, and companies like <a href="https://medium.com/netflix-techblog/developer-experience-lessons-operating-a-serverless-like-platform-at-netflix-a8bbd5b899a0">Netflix</a>, <a href="https://aws.amazon.com/solutions/case-studies/square-enix/">Square Enix</a>, <a href="https://www.youtube.com/watch?v=g0M0PN2bFFA">iRobot</a>, <a href="https://serverless.com/blog/rob-gruhl-serverless-event-sourced-nordstrom-emit-2017/">Nordstrom</a>, <a href="https://medium.com/airbnb-engineering/binaryalert-real-time-serverless-malware-detection-ca44370c1b90">AirBnb</a>, <a href="https://medium.com/capital-one-developers/serverless-is-the-paas-i-always-wanted-9e9c7d925539">Capital One</a> have publicly shared their experiences in serverless.</p><p><strong>What are the benefits of Jeff/Serverless?</strong></p><p>As with most fully managed solutions, adopting FaaS as your compute layer allows you to <strong>offload a considerable part of the heavy lifting</strong> required to run your code. This will make your solution <strong>faster</strong> in terms of time-to-market, <strong>easier</strong> to operate thanks to its “zero-administration” side, and ultimately <strong>cheaper</strong> when you consider the total cost of ownership. Indeed, even without considering the potential cost savings related to its PAYG model (by 100ms increments), the overall cost of a product tends to be cheaper when you remove most of the infrastructure, network, and hardware maintenance from the equation.</p><p>Furthermore, FaaS allows you to monitor logs, performance, and costs on a per-function basis. This gives you more granularity when it comes to performance and cost optimization, but it also opens a whole new market for tooling and monitoring solutions. Luckily, organizations such a <a href="https://www.iopipe.com/">IOpipe</a>, <a href="https://www.datadoghq.com/blog/monitoring-lambda-functions-datadog/">Datadog</a>, and <a href="https://blog.newrelic.com/2016/11/29/aws-lambda-integration-serverless-infrastructure/">New Relic</a> promptly covered this space in the last 18 months.</p><p><strong>What are the challenges for developers or operations who are new to serverless?</strong></p><p>With every architectural “revolution” come new challenges. The ecosystem is still very young and quickly evolving, which makes it hardly an option for slow enterprises, although it started gaining momentum in 2017.</p><p>Many frameworks are still emerging in the open-source world, with each solving a particular pain point. However, few of them are doing so in a exhaustive and vendor-neutral way. Although the <a href="https://serverless.com/framework/">Serverless Framework</a> is leading the public cloud tooling spectrum, new projects such as <a href="https://www.openfaas.com/">OpenFaaS</a> are successfully targeting the private/hybrid and container-native world.</p><p>Since most of the “<em>lock-in</em>” of FaaS is related to the set of integrations and services consumed by your functions, the tooling framework and platform of choice will often depend on where your data is stored, rather than the quality of its software or its community (this is sad, but true for many organizations that can’t afford to migrate).</p><p>While there have been public cases of migration from legacy/monolithic architectures to serverless, a serverless lift-and-shift strategy is not yet available. Migrating legacy components or whole systems will likely require a partial re-design of the architecture toward a more event-driven approach. Some frameworks and libraries have been solving this problem for simple use cases (e.g. <a href="https://github.com/Miserlou/Zappa">Zappa</a> for Django/Flask applications, <a href="https://github.com/awslabs/aws-serverless-express">aws-serverless-express</a> for Express applications, etc.), but I would argue that most legacy architectures diverged from “<em>Hello World</em>” sample apps years ago and their porting is never as painless as promised.</p><p>In my opinion, the most underestimated challenge is due to the false expectation of <strong><em>#NoOps</em></strong>. Many public clouds have often marketized “serverless” as the death of (Dev)Ops, which is a cheap and provocative way to spread the buzzword, but this idea becomes dangerous when <strong>developers pretend that they can ignore all of the best practices </strong>(e.g. infrastructure as code, immutability, test-driven development, continuous-integration, etc.). As a new community, I believe that it’s our responsibility to not disregard the past, but to learn from it and keep innovating in the right direction.</p><p><strong>Are there also organizational challenges?</strong></p><p>The most critical challenge is probably related to an organization’s ability to trust the cloud provider of choice. Since “serverless” is a cloud-native way of developing applications, hybrid solutions are not trivial to implement. Therefore, many organizations might struggle with the “vendor lock-in fear” even though many aspects of the technology and its tooling make it fairly easy to migrate to other clouds (maybe not as easy as a Docker container, but pretty close).</p><p>On the other hand, an organization could build its own FaaS layer on top of existing infrastructure (e.g. a Kubernetes cluster running on-prem). This would allow developers to benefit from the new abstraction layer even if the heavy-lifting related to infrastructure management is not completely removed from the organization.</p><p>Depending on your current technology stack, Jeff might be a great fit for new pilot projects or even new features that must be integrated with legacy architectures, especially if you have already embraced DevOps best practices.</p><p>Nevertheless, some organizations have skipped a few steps and <a href="https://github.com/toricls/cobolambda">migrated their Cobol code base to serverless</a> (directly from the mainframe).</p><p><strong>Which topic are you going to talk about at JeffConf Hamburg?</strong></p><p>I’ve always been fascinated by big data and data analytics<strong>, </strong>therefore I’m going to discuss “<em>Serverless Data Warehousing &amp; Data Analysis</em>”. Storing possibly unstructured data and querying it efficiently without managing servers is quite a challenging problem, and I’m going to explore a few techniques and gotchas that I’ve learned while implementing our solution on AWS.</p><p>This journey started in early 2016 because my data science team needed a way to deploy machine learning models, iterate quickly to optimize their predictive performance, and scale up effortless without the need of a DevOps team (data scientists are not ssh-lovers). I chose AWS Lambda and after a few weeks, we had our first models online, implemented in Python and scikit-learn. Once the real-time predictions were operational, I started working on the data analytics side of the system, as we needed a way to improve the performance and precision of our reports. I’m going to share my experience with the data analytics stack on AWS, which includes Lambda, Kinesis, Athena, and QuickSight.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fad87f290929" width="1" height="1" alt=""><hr><p><a href="https://medium.com/serverless-zone/from-buzzword-to-meaningful-infrastructure-option-whats-behind-serverless-fad87f290929">From buzzword to meaningful infrastructure option? What’s behind “Serverless”</a> was originally published in <a href="https://medium.com/serverless-zone">Serverless Zone</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>