4 ms·

Because frankly, the serverless/backendless(such as Firebase) movement is just turning Frontend developers into fullstack developers who are completely dependen

Because frankly, the serverless/backendless(such as Firebase) movement is just turning Frontend developers into fullstack developers who are completely dependent on vendor lockin. I believe, wholly, in frontend-first design and thinking. Talk to customers, understand their problems, build toward that and have the code adapt to their wants and needs. But with vendor lockin, sometimes you have problems that they genuinely can't let you solve, or you can't solve in a performent way. --- Also, it strikes me that in reality, a serverless architecture is just functional programming without the ability to share code nearly as easily. If you're worrying your head off about how you're having to pay for servers that are always up- you're absolutely solving the wrong problem. Even the cheapest junior developer's time costs a fraction as much as what you'll waste in time developing for serverless instead of a traditional solution- and it's not because serverless technology isn't there, it's because even in the ideal, serverless will always be a harder solve. It's inherent to the problem itself.

scarface74 8y ago
Developing for serverless is no harder than "traditional" development. The traditional API you have a controller that has methods that are called based on HTTP verbs and routes. The controller methods translate the request to the backend. With Lambda it's the same thing. You have a Lambda function mapped to an HTTP verb and route and you get s message and context. The handler acts just like your controller method. Converting from Lambda to a traditional MVC is not that hard.
- bdcravens 8y ago
  Can I run Lambda and API gateway locally?
- bdcravens 8y ago
  > With Lambda it's the same thing. You have a Lambda function mapped to an HTTP verb and route and you get s message and context Lambda is simple. However, to do what you're describing requires a lot more: API Gateway, IAM roles, etc.
  - scarface74 8y ago
    API gateway does the same thing as your own custom per request filters and your own routing attributes. The roles for the Lambda you can just give one or more of the built in policies. If you were using EC2 instances, you would still assign roles to the EC2 instance for the same permissions. If you are doing it outside of AWS you would hopefully setup DMZs firewalls, etc.

scarface74 8y ago

Developing for serverless is no harder than "traditional" development. The traditional API you have a controller that has methods that are called based on HTTP verbs and routes. The controller methods translate the request to the backend. With Lambda it's the same thing. You have a Lambda function mapped to an HTTP verb and route and you get s message and context. The handler acts just like your controller method. Converting from Lambda to a traditional MVC is not that hard.

bdcravens 8y ago
Can I run Lambda and API gateway locally?
bdcravens 8y ago
> With Lambda it's the same thing. You have a Lambda function mapped to an HTTP verb and route and you get s message and context Lambda is simple. However, to do what you're describing requires a lot more: API Gateway, IAM roles, etc.
- scarface74 8y ago
  API gateway does the same thing as your own custom per request filters and your own routing attributes. The roles for the Lambda you can just give one or more of the built in policies. If you were using EC2 instances, you would still assign roles to the EC2 instance for the same permissions. If you are doing it outside of AWS you would hopefully setup DMZs firewalls, etc.