4 ms·

Serverless has it's faults, but spaghetti code spread across 100 repos is definitely a "user error"...

• ecshafer 3y ago
  How do you solve the discoverability issue when theres 1000 serverless functions written by 10 different teams then? Serverless worsens the issue of having knowledge of the entire system i think, and i dont think this is even solvable.
  • inhumantsar 3y ago
    Lambdas are rarely entirely standalone, they support a larger service or glue services together. Creating one repo per Lambda is going to make things messy of course, just as breaking every little internal library out into its own repo. Regardless of the system or what it runs on, it's an easy trap to fall into but it's absolutely solvable with some technical leadership around standards.
    • cassianoleal 3y ago
      > Lambdas are rarely entirely standalone, they support a larger service or glue services together. I wish that was the case in real life. Unfortunately, the trend I've been noticing is to run anything that's an API call in Lambda, and then chaining multiple Lambdas in order to process whatever is needed for that API call.
  • latchkey 3y ago
    One serverless function is effectively a http router that knows how to call the appropriate code path to reach the 1000 handlers.