Cross-machine dependencies are a feature being added to DSC with PowerShell v5; that sort of orchestration isn't currently available. However, you will want to be careful about how you use this even when that option is available; you don't want to be stopping and starting services every time DSC checks your configuration, for example, and there's not a particularly good way to tell it to do that only if the files need to be updated.
Cool as it is, DSC isn't always the right tool for the job.
Thanks for the answer. Yes, as I think about it the orchestration described above is probably not a great process; ideally you would want services from disparate nodes to be independent of one another and thus tolerant of outages