#lambda expresssions

[andre-the-analyst]

Python Live-1 | Lambda Function & Constructors in Python | Python Tutorial for Beginners | Edureka

Python Live-1 | Lambda Function & Constructors in Python | Python Tutorial for Beginners | #Edureka #Python #Datalytical

🔥Edureka Python Certification Training: https://www.edureka.co/python-programming-certification-training This Edureka session on Lamda Function & Constructors in Python will educate you about the Lambda functions and various constructors available in Python and help you understand how to use them in various scenarios.

———————————————————————————————-

🔴Subscribe to our channel to get video…

[freeudemycourses]

[100% OFF] Kotlin : Complete step by step guide for Beginners What you Will learn ? Solid foundation of kotlin Object Oriented Programming Lambda Expresssion Higher Order Functions…

[startupmemo]

Starting a Startup - Day 43 (BOD)

April 4th 2017

Back to Server (or Serverless) Development

I'll have to start working on backend and Web services API. Obviously, I'll use "cloud", but the question is, how exactly? I'm a fan of "serverless".

When Google App Engine came out almost 10 years ago, I becaome a big fan of PaaS. Just to give a historical perspective, the public cloud offerings were really started by Amazon. First S3, and EC2 and SimpleDB, etc. But, it was Google who offerred PaaS first. I think it was much later when Amazon provided Elastic Beanstalk.

PaaS services like Google App Engine gives a lot of benefits. You don't have to manage your server, I mean server in the software sense. When you use "cloud" you delegate all hardware management to the cloud service providers. But, generally you'll have to manage your software stack when you use services like EC2, including the "servers", which are not really specific to your apps. Recently, containter services like Docker have made it easier to manager your software stacks, but it's still you who have to handle all software deployment and management.

In the PaaS paradigm, the cloud service providers manage all common software stacks. As long as you build your app in a certain standard way, you don't have to worry about anything else. You just deploy your apps, and you only manage your apps. In case of Java, you just build your app in the standars war format, and that's all you have to do.

Why do you want to care about underlying web servers and what not when you don't have to? I loved PaaS. When I worked on Web services many years ago, I exclusively used Google App Engine. There are limitations, and it's not for everyone. But, if you think about it, is your app so special that would require special setups in the underlying frameworks (which are essentially stock software like Apache web server)?

Now, fast forward several years, Amazon started offering this "serverless" service, Lambda, a couple of years ago. No matter how they positioned it as a brand new product category, however, the serverless service is just a PaaS. You just write your app (or, "function" as they call it now) and deploy it. All other common software stack, including frameworks, etc., are taken care of by AWS. It's been getting a lot of attention since its release. All other cloud service providers like Microsoft Azure, Google Cloud, and IBM Bluemix now have similar offerings.

The biggest difference of "Serverless" relative to existing PaaS services like AWS Elastic Beanstalk or Google App Engine is that it is not limited to particular server framework. You donn't have to write your web apps for particular web app frameworks or according to particular standards, whether you are using Java, Python, or Node.js, etc. In fact, in the new serverless paradigm, you are not even limited to writing web apps. Any software piece can be run on Lambda, for instance. Clearly, this opens up an enormous possibilities which were not previously possible in the old PaaS framework.

I first learned about Lambda at work while working on a small web app project last year. (Before then, I was mostly focusing on mobile and VR/AR app development, and I wasn't really up to date with what was happening in the cloud technologies.) The moment I realized what it was, I immediately fell in love. This was exactly what I was looking for when I was struggling with the limitatation of PaaS many years ago.

For the current project, Serverless is obviously my first choice.

Node.js vs ASP.net Core on AWS Lambda

I've been thinking about this, and for various reasons, especially for projects like this which I'm building everything from the ground up, I'll use serverless, AWS Lambda in particular.

Now the questios is, which language to use. The frontend (at least for prototypes) is being built with Javascript/Typescrpt, so there could be a benefit of using Node.js even for backend, say, in terms of code reuse between frontend and backend, etc. On the other hand, I'm more familiar with languages like C#. You can actually run ASP.Net Core on Lambda, which I used a little bit last year. (BTW, I keep asking. What is wrong with Microsoft? When I used ASP.Net Core version 1.0, it was based on project.json. Since then, apparently they changed the framework to use MSBuild, which is very likely backward incompatible. I don't even know how big this change is, but it makes me cringe, literally.)

So, Node.js (with Serverless Expresss) vs C# (with ASP.Net Core).

Which one would be better?