5 ms·

If successful this could lead reduction in developers needed in companies that use say AWS lambda.

spriggan3 10y ago
> If successful this could lead reduction in developers needed in companies that use say AWS lambda. How so ? to me it makes development even more complicated, cheaper relative to hosting fees maybe, but simpler ? I don't think so. What if I want to use language XYZ not supported by lambda ?
- buckbova 10y ago
  You can't. Isn't everyone using the same language simple? Convenient? Maybe not.
- nawitus 10y ago
  > cheaper relative to hosting fees maybe Currently serverless is more expensive in the average case from what I gather, mainly since it's new and there's little competition.
  - taurath 10y ago
    If avg case is that you stay within an average load for long periods of time, then it'll likely be more expensive (given a certain floor of actual load - for in-dev apps its dirt cheap - you won't have many servers running doing nothing.
- rainhacker 10y ago
  > What if I want to use language XYZ not supported by lambda ? Such problems can apply to any ready made solution. In general, a vendor product may or may not suffice custom needs and a user is free to build one from scratch. Abstraction of major pain points that fits a wide variety of user needs, if handled properly, can pave the way for a competitive solution.
tschellenbach 10y ago
If history is a guide, I suspect it will just increase the size and complexity of apps. Its amazing what small teams with serverless architectures can accomplish nowadays.
- rainhacker 10y ago
  > If history is a guide. Could you elaborate on this ? I agree the size and complexity could increase, but so could the number features in the apps. Since all such apps would be reusing the same code base, wouldn't this increase abstraction and reduce implementation hours ?
  - buckbova 10y ago
    I think it's something like a big monolithic app is less complex than a n-tier client server app which is less complex than a microservices distributed app which could be less complex than a purely FaaS implemented app, yet to be determined.
    - collyw 10y ago
      I guess thats the whole point. More complexity overall, because you split the parts up more. The advantage being that you only scale the parts that need to scale.

> If successful this could lead reduction in developers needed in companies that use say AWS lambda. How so ? to me it makes development even more complicated, cheaper relative to hosting fees maybe, but simpler ? I don't think so. What if I want to use language XYZ not supported by lambda ?

buckbova 10y ago
You can't. Isn't everyone using the same language simple? Convenient? Maybe not.
nawitus 10y ago
> cheaper relative to hosting fees maybe Currently serverless is more expensive in the average case from what I gather, mainly since it's new and there's little competition.
- taurath 10y ago
  If avg case is that you stay within an average load for long periods of time, then it'll likely be more expensive (given a certain floor of actual load - for in-dev apps its dirt cheap - you won't have many servers running doing nothing.
rainhacker 10y ago
> What if I want to use language XYZ not supported by lambda ? Such problems can apply to any ready made solution. In general, a vendor product may or may not suffice custom needs and a user is free to build one from scratch. Abstraction of major pain points that fits a wide variety of user needs, if handled properly, can pave the way for a competitive solution.

tschellenbach 10y ago

If history is a guide, I suspect it will just increase the size and complexity of apps. Its amazing what small teams with serverless architectures can accomplish nowadays.

rainhacker 10y ago
> If history is a guide. Could you elaborate on this ? I agree the size and complexity could increase, but so could the number features in the apps. Since all such apps would be reusing the same code base, wouldn't this increase abstraction and reduce implementation hours ?
- buckbova 10y ago
  I think it's something like a big monolithic app is less complex than a n-tier client server app which is less complex than a microservices distributed app which could be less complex than a purely FaaS implemented app, yet to be determined.
  - collyw 10y ago
    I guess thats the whole point. More complexity overall, because you split the parts up more. The advantage being that you only scale the parts that need to scale.