Amazon Lambda function Naming Conventions?
nelsonic opened this issue · 6 comments
The convention in Serverless appears to be to start Lambda function names with a Capital letter and then CammelCase after that ... see: https://github.com/serverless/serverless/tree/master/lib
... this feels wrong to me ...
what do others think?
Serverless is useless. The lack of stage/version support turn Lambda console a complete mess. Camel is not good as npm does not allow camel (npm init). The way it manages environment is crazy. Think about what would happen if your microservices grows to, say, 500 functions (my case)...now you have 4 environments, so serverless would create 2000 functions (stop stop stop). No, thanks.
I would say to drop serverless altogether and create your own CI/CD process (I did that and I did not regret).
@eslopes I think this means that serverless is just not the right setup for you. There are many testimonials online where serverless is a good solution and provided them a lot of benefits.
Just saying it is useless is not helping anyone. Maybe you could write a more detailed article as to why it did not make any sense in your situation.
I would use it if those problems were fixed, but serverless team focus seems to provide multiplatform capabilities. Amazon owns this market and it is accelerating, providing more, and more features on a daily basis. Microsoft? IBM? Really? Gimme a break. I spent 11 years at IBM. It is a black hole of good ideas. Not a single one find its way to the market (and do not start speaking about openwhisky/beer/vodka. It is like Google+...nobody cares).
Serverless could be great, but it is just OK if your project is small, and from what I've learned this last year microservices' projects should grow exponentially (both number and size) in the next couple of years. Amazon is not perfect, but is stable, and its support team is definitely outstanding. Try to get IBM's support on line...(send me a log, pls). So, my point is, why spend time trying to support multiple platforms? This reminds me apps that support Blackberry/Windows Phone. Why, Mr. Anderson, why? Make serveless great with Lambda/API Gateway and it will become the de facto standard to build microservices.
Hope you find a way to make this
@eslopes that's a little harsh on IBM and the challenger cloud providers, but thank you for sharing your perspective. It was interesting to see put it that way.
@QuantumGrizzly in fairness to IBM their "OpenWhisk" (part of "Bluemix") is actually pretty good but it's not as easy to use as Lambda and is comparatively more expensive ... 💸
I'd recommend reading this comparison post from our friends at Contino:
https://www.contino.io/insights/why-aws-lambda-stands-out-from-the-competition 💡
I've been working on a reasonably large project (20 devs) using Serverless and can say that I would definitely not use it for a "general" (larger) web application because there is a lot of "boilerplate" code in the project and having a request run through multiple Lambda functions is quite slow... 🐌
For me, the Lambda use-case is for a small function that gets triggered as a result of an S3 operation or processing sending/receiving an email, etc. Not for a "Web Application".
Testing Lambdas that call other lambdas is cumbersome whereas testing a Phoenix application is fast and painless!
@eslopes So you saying you would rather use AWS-SAM than serverless, serverless is not perfect, but they plugin system is very good, everytime serverless doesnt do something i need, i just build it into a plugin, i suppose that it is not ideal if you are a java dev, but for nodejs, i really couldnt wish more from a free open-source product.
Serverless went from a couple guys in a bedroom doing a cli tool that help them, to a fully fledged company, serverless provided uploading scripts and ease of creating lambda functions much better than aws was providing. They made lots of effort in creating plugins and to me they built a friendly and helpful community around it. However AWS as usual came along and decided to copy most of their effort and use the SAM plugin, so why should should serverless put all their eggs in one basket and only look at companies that use aws, when aws shown that they will continue to take in features from serverless into SAM.
While i havent used their cross cloud provider tools, i am thankful that serverless exists, and will continue to use it until their stop moving forward, or SAM becomes so great that makes it illogical to make the move.
However i do agree with you on IBM, i have worked on a company that uses a lot ibm products, and god, their systems suck, their service sucks, they slowdown our deployments because someone decided to use their tools to monitor deployments, their support sucks, so hopefully eventually IBM will just a fossil, since they refuse to improve or take care of their customers.