☆ Yσɠƚԋσʂ ☆

  • 148 Posts
  • 50 Comments
Joined 5 years ago
cake
Cake day: January 18th, 2020

help-circle



















  • I find small services work fine for well defined and context free tasks. For example, say you have common tasks like handling user authorization, PDF generation, etc. Having a common service to handle that is a good idea. This sort of a service bus can be leveraged by different apps that can focus on their business logic, and leverage common functionality.

    However, anything that’s part of a common workflow and has shared state is much better handled within a single application. Splitting things out into services creates a ton of overhead, and doesn’t actually address any problems since you have to be able to reason about the entirety of the workflow anyways. You end up having a much more difficult development process where you need a bunch of services running. Doing API calls means having to add endpoints, do authentication, etc. where within a single app you just do a function call. Debugging and tracing becomes a lot more difficult, and so on.


















  • This dynamic illustrates how capitalism goes through different stages. Early on, companies compete on quality trying to attract customers with better products, and you end up with quality things that work well, last a long time, and so on. However, eventually you get to the point where the same volumes of the product are no longer needed, and that’s when you start seeing things like planned obsolescence creep in because the logic of capitalism is that you have to keep selling and growing indefinitely.