Improve api to help in extending

[geofmureithi]

Part of the API esp in mq-surreal can be refactored to help in building lib's on top of it eg.

mq/mq-surreal/src/producer.rs

Lines 10 to 13 in 5ea1781

	pub struct SurrealProducer {
	db: Arc<Surreal<Any>>,
	table: String,
	}

Some of my goals is to use the methods provided to do so eg:

mq/mq-surreal/src/producer.rs

Line 26 in 5ea1781

async fn publish(&self, job: Job) -> Result<(), Error> {

Specifically I want to work with this for apalis to close issue geofmureithi/apalis#22
Apalis introduced a message queuing trait in 0.4.

One problem I am facing is, you use a concrete type Job while apalis uses a generic JobRequest<T>, so it may be hard to integrate without some changes.

My main goal here is not to do the same implementation elsewhere when I don't necessarily use SurrealDb yet you already have a maintained crate here 😄.

[prabirshrestha]

I consider mq at a very early stage. I still haven't finished designing the apis and adding features so I expect it to continue to break in the future.

Is depending on producer trait not enough?

As for concrete job type you can always create your own and convert it to mq job type.

More than happy to continue to get feedback and make necessary changes.

[geofmureithi]

As for concrete job type you can always create your own and convert it to mq job type.

Let me look at this and get back.