Multiple Aggregates / Repositories in one Transaction

Question

I have a payment system as shown below. The payment can be made through multiple gift coupons. The gift coupons are issued along with a purchase. The customer can make use o

Answer 1

There's nothing wrong with using two repositories in one transaction. As JB Nizet points out, that's what a service layer is for.

If you're having issue keeping the connection shared, you can use the Unit of Work¹ pattern to control the connection from the service layer and have the factory that provides the data context to your repositories supply the OoW instance.

¹ The EF/L2S DataContext is itself a UoW implementation, but it's nice to have an abstract one for the service layer for situations such as these.