serverless-express

deploy nodejs/express applications

e your runtime to match your language. I’ve used this same template for JS, C#, and Python. Nobody said anything about Docker or Fargate. This has nothing to do with the topic. My problems had no need for using Docker. Do you randomly pick a tool kit and just hope it works out? I suspect you're not really working at scale and costs aren't a concern. You’re using your standard framework that you would usually use. You can use whatever deployment pipeline just as easily to deploy to EC2 with no code changes. Great job. We are all proud of you I guess, but this is not how engineering works, especially when you're building at scale. Actually it is. Since you are using a standard framework choose whatever deployment target you want.... Have you looked into Express and what dependencies it has, or do you just randomly pick the new framework of the week? I don't mean this as an attack, but I'm more than slightly annoyed that you keep referring to Node and Express, when that has nothing to do with the problems I'm trying to solve. I also mentioned C# and Python. But as far as Java/Spring. Here you go. https://github.com/awslabs/aws-serverless-java-container/wik... The funny thing is you've written out all these lengthy posts but never stopped to ask about whatever constraints the system has. You started with the solution and are basically now looking at one of my constraints (JVM ecosystem) and are saying it's not a good choice. I’ve also just posted a Java solution. The constraints of Lambda are well known and separate from Java - 15 minute runtime, limited CPU/Memory options and a 512MB limit of local TMP storage. In the real world, we often don't have the ability to randomly swap out a language. There's enough properly tested code that already exists or a massive code base that entire teams are supporting. They're not going to drop that just so they can go pick up a shiny new framework or product offering. LOL. My suggestion didn’t require “switching out the language”. Proxy integration works with every supported language - including Java. It also works with languages like PHP that are not supported via custom runtimes and third party open source solutions.

ode, deploy it anywhere else as you would any other API. Here is a Node Express example. https://github.com/awslabs/aws-serverless-express

poor craftsmen who blames his tools”. Don’t blame AWS for the missing skillset of your developers. There is no reason that it should take your developers any longer to build an API with lambda instead of a server. In fact, you can host the same APIs with lambda by only adding two or three lines of code and using proxy integration. For instance in Node: https://github.com/awslabs/aws-serverless-express

ocused on it'd just be better to start off with a Rails app, it's quick, it's easy and it's understood. There is also code to wrap a Rails app and run it on lambda.... And really, is lambda appropriate for anything more than a very focused niche app? I mean, try writing all the usual things you need to slot into a SaaS on it, billing, user management, signup, admin reports, admin functionality, emails, multi-tenancy, custom domains, etc. etc. Even a 20 user, internal, enterprise app needs most of that functionality Yes. Especially in today’s world of client side frameworks and microservices, you host your static assets like Javascript, css, and HTML in S3 and call server side APIs hosted on lambda. Put on top of that, you're forced to use a particular, proprietary tech stack and lock yourself into something that might very well die in a couple of years. Well, two things. What’s more likely to die in two years / your startup or AWS? Second, you can host your standard API just by adding four lines of code and you don’t have to make any changes to host it in Docker or on a VM. There is a way to do this in every language that lambda natively supports. For instance for Node: https://github.com/awslabs/aws-serverless-express I have a Node/Express app that gets deployed to both lambda and Fargate (Serverless Docker) when I push it. The only difference is that lambda uses one entry point and Docker uses another. I’ve done something similar with C# https://aws.amazon.com/blogs/developer/deploy-an-existing-as... Where it is deployed to both lambda and a Windows server running IIS. I can be a lot more productive with all the resources that AWS has to offer when all I have to do is provision resources with a CloudFormation template and instead of doing the grunt work of infrastructure administration I can concentrate on writing software.

rverless Docker) or EC2 instances without any code changes: C#/Web API https://aws.amazon.com/blogs/developer/deploy-an-existing-as... Node: https://github.com/awslabs/aws-serverless-express Python/Flask https://dev.to/apcelent/deploying-flask-on-aws-lambda-4k42 I’ve been told that there are similar frameworks for other languages but those are the three that I use. If you have any other questions, feel free to email me. My address is in my profile. I’m not a consultant trying to sell anything....

hat is holy, learn CloudFormation and don’t create resources manually. https://www.udemy.com/share/1011JEBUQdeF5TQn4=/ If you have any questions, an email address is in my profile.