5 ms·

I agree, to be fair though - almost all of this could be mitigated in future by better tooling.

by mateuszf 8y ago

toomuchtodo 8y ago
Hope is not an architectural methodology.
- moduspol 8y ago
  If every emerging technology were scrapped early on due to lack of tooling, we'd have no mature technologies.
  - toomuchtodo 8y ago
    Fair point, as long as it’s someone else’s time and dime to mature these arguably fad technologies of questionable value. Until then, it’s not a mature technology, it should not be sold as such, and you take significant risk in implementing with it.
    - deleted 8y ago
      [deleted]
  - Annatar 8y ago
    Very few technologies in IT are actually mature, and of those that are, it’s exactly their documentation and tooling which makes them mature.
ariehkovler 8y ago
Serverless tooling is coming fast. 1. Biggest issue with serverless is debugging when you can't make a local environment and can't install anything like a conventional debugger in the serverless environment. I know of at least one company with a new and very elegant solution for this problem. 2. Visibility and monitoring is also a challenge and there are a bunch of serverless monitoring startups. 3. Security is interesting because, again, you can't install anything to protect your code: no Web Application Firewalls, for example. And there are several interesting theoretical attacks on serverless apps. Already, there are specialist serverless security companies. A lot of companies don't 'migrate' to serverless. They use a Lambda or GCP Function to handle one small part of a backend task like image processing or some other form of backend tooling. Serverless is often just a good way of gluing other microservices together.
- acejam 8y ago
  You can run and debug AWS Lambda locally. We've done it with several of our API's: https://github.com/awslabs/aws-sam-cli https://github.com/awslabs/aws-sam-cli
  - ariehkovler 8y ago
    you can't always create the full environment locally, though, including inputs and connections to other services... local Lambda is an option but there are more elegant solutions too.
    - acejam 8y ago
      You have full control over the incoming event object, so you should have complete control over inputs. Connections to services depends on your setup of course. If you can route to your VPC, you can access those private resources too. By default, it will use your local AWS keypair, but I believe there is a way to assume an IAM role as well.
      - ariehkovler 8y ago
        Sure, but if you can just get full stack traces right off of your production code while it runs, then that's even easier.

I agree, to be fair though - almost all of this could be mitigated in future by better tooling.

toomuchtodo 8y ago

Hope is not an architectural methodology.

moduspol 8y ago
If every emerging technology were scrapped early on due to lack of tooling, we'd have no mature technologies.
- toomuchtodo 8y ago
  Fair point, as long as it’s someone else’s time and dime to mature these arguably fad technologies of questionable value. Until then, it’s not a mature technology, it should not be sold as such, and you take significant risk in implementing with it.
  - deleted 8y ago
    [deleted]
- Annatar 8y ago
  Very few technologies in IT are actually mature, and of those that are, it’s exactly their documentation and tooling which makes them mature.

ariehkovler 8y ago

Serverless tooling is coming fast. 1. Biggest issue with serverless is debugging when you can't make a local environment and can't install anything like a conventional debugger in the serverless environment. I know of at least one company with a new and very elegant solution for this problem. 2. Visibility and monitoring is also a challenge and there are a bunch of serverless monitoring startups. 3. Security is interesting because, again, you can't install anything to protect your code: no Web Application Firewalls, for example. And there are several interesting theoretical attacks on serverless apps. Already, there are specialist serverless security companies. A lot of companies don't 'migrate' to serverless. They use a Lambda or GCP Function to handle one small part of a backend task like image processing or some other form of backend tooling. Serverless is often just a good way of gluing other microservices together.

acejam 8y ago
You can run and debug AWS Lambda locally. We've done it with several of our API's: https://github.com/awslabs/aws-sam-cli https://github.com/awslabs/aws-sam-cli
- ariehkovler 8y ago
  you can't always create the full environment locally, though, including inputs and connections to other services... local Lambda is an option but there are more elegant solutions too.
  - acejam 8y ago
    You have full control over the incoming event object, so you should have complete control over inputs. Connections to services depends on your setup of course. If you can route to your VPC, you can access those private resources too. By default, it will use your local AWS keypair, but I believe there is a way to assume an IAM role as well.
    - ariehkovler 8y ago
      Sure, but if you can just get full stack traces right off of your production code while it runs, then that's even easier.