Identify common usage scenarios for Sql based technologies

[tmasternak]

Problem

Currently samples regarding different sql technologies (transport, persistence) are scattered between different parts of doco. They are showing single aspect of technology usage which is not that useful for the end users.

[SimonCropp]

Why is showing single aspects of technology usage not useful. That is the purpose of the majority of samples and it has served us well for several years

[SzymonPobiega]

@SimonCropp it would be useful if it worked. The reality is that the samples that involve sql technologies usually involve at least 2 so they already are not atomic.

[markgould]

I would also like to see some better guidance for this too. We are using SqlTransport and have moved from NHibernate to SQL Persistence. Previously we had all transport and persistence was using one catalog (legacy monolith database where triggers are inserting into queues for some parts of the system).

Now with the Bridge, I've switched to a dedicated transport database (with one queue in the monolith database to handle the trigger inserts which the bridge then picks up) and persistence is now stored in the SQL database where the business data for that endpoint belongs to.

I do think having some guidance for people that are using SQL for everything, would be helpful.

Thanks to everyone for all the hard work. NServiceBus is just getting better and better.

[SzymonPobiega]

@markgould

Now with the Bridge, I've switched to a dedicated transport database

Bridge? Which one? Do you use the new multi-catalog feature?

[markgould]

I'm using your NServiceBus.Bridge library. I'd raised an issue over there but found out it was due to needing the latest SQL Transport which wasn't released at the time.

[SzymonPobiega]

@markgould I am sorry, I didn't notice it. For some reason github failed to deliver the new issue notification to me. I'll look into it.

EDIT: It seems like I was not watching my own repos on github due to wrong default settings :(

[kbaley]

Some clarification from @tmasternak:

The idea was to have something similar to https://docs.particular.net/transports/sql/deployment-options?version=sqltransport_7 but spanning sqlt, sqlp, and entityframework (and nhibernate?). In short, how you can mix and match our sql packages if you work on top of sql. These would include schema, catalog setup as well as sharing transactions to avoid DTC. We already have samples around that but I think they could use some more high level explanations.