Fred discusses the challenges of finding existing microservices versus the ease of creating new ones, emphasizing the trade-off between time savings and service redundancy. He highlights that while bugs may need to be fixed in multiple places, the understanding of the system should be a collective effort within the team, rather than relying solely on a single architect. The conversation reveals the importance of team knowledge in navigating the complexities of microservices architecture.
