Exactly.

Evented production typologies can be achieved without losing the code reuse of developing everything together in the same repo.

You can have thousands of engineers sharing code via functions while also deploying the entire codebase in a myriad of different production modes to execute procedures differently for different purposes.

Just because Kafka consumers need their own persistent process that's seperate from request/response architecture, does t mean those functions need their own source repository and deployment systems, etc.

Reuse everything.