What's Redwood's approach to monorepos / microservices?

I want to deploy different microservices with different entrypoints (some are web and some are api-only) but want to share the type definitions in a monorepo.

What is Redwood’s approach to this?

Codegen from the GraphQL API is probably the answer you’re looking for, as the GraphQL API from Redwood is probably the conduit between all separate services

Say I have several external REST API services I need to spin up independently of each other, but I still want to share type defs and utilities between them. What would be the Redwood approach, save from creating an entire separate repo?

That mainly depends on your deployment strategy I’m afraid, you could use docker to have them all live in one repo - redwood doesn’t really much say in that