Chris Richardson

> @cer Thanks for you support. And please clarify below queries: > > 1. I am still not clear about eventuate tables. Do I need to create below Eventuate tables...

Hmm.. I see the problem with those scripts - they use Eventuate as the hardwired schema. But the key point is to create the same tables as those scripts. It's...

> But where to execute this schema file > [sagas/blob/master/postgres/tram-saga-schema.sql)](https://github.com/eventuate-tram/eventuate-tram-sagas/blob/master/postgres/tram-saga-schema.sql) Even though some tables are orchestrator specific and some are participant specific, I would execute it in both for both...

> 1. How to configure my own topic and partition names in order and customer micro services? Please could you clarify the question. Names of which topics? Partitions don't have...

> @cer Usually by using spring-cloud stream we will configure our Kafka destination like customer-topic and order-topic in application.yml file . Is there any way to configure topic names instead...

> 1. why it is again expecting **eventuate.saga_instance** schema as I have already created this table in public schema of both order & customer service DB. I think you are...

> Ok.what is the corresponding configuration property > Key for EVENTUATE_DATABASE_SCHEMA in the application.yml file as I have created my own order and customer service in local workspace `eventuate.database.schema`

> @cer Thank you for the quick response. I will try and feedback you. More queries: > > 1. In which eventuate framework PROD (tentative date) release the eventuate framework...

> 3. Why customer_credit_reservation table is created for SAGA instead it can use same customer table for updating the credit limit right? Because while querying my customer table always my...

> 7\. Order and Customer entity. Usually, it is a class which contains fields and corresponding getter and setter methods and JPA annotations but here we have business logic too...