ЕЗ
ардуин это из звездных войн что то?
Из властелина колец.
Size: a a a
2020 December 04
EE
я крапиву палкой пиздил
сейчас бы кстати тоже этим занялся
AD
Зырьте, че ребенок залепил, воткнул две крутилки в ардуину и сделал гонялку машинки по экрану на скрече и ардуине, одна ручка - руль, другая ручка меняет скорость
Афигеть
АД
азазазазависть
G
Sure, of course. Yes, I'm modeling my solution to use dry-transactions and at certain point we thought about notify other system about a failed step and I thought about queue to not miss this information of failure
Basically I want to make sure that those steps will all occur inside a unique transaction, but if a step fails I would like to store this information in a DB or something like this, but to control this information consumption I would put this failure information in a queue to be consumed according to the DB workload capacity.
w
Афигеть
Это он типа аналоговые порты изучал, там АЦПшки стоят на 6 инпутах
2020 December 05
ES
Я в 7 лет носился с разгона в стенку разве что...
Ну я картины рисовал.
И грядки копал.
И грядки копал.
ES
Ля это шо
ES
Не зря я драй рб в тайтл добавил.
ES
Подцепили какого-то итальянца.
G
Basically I want to make sure that those steps will all occur inside a unique transaction, but if a step fails I would like to store this information in a DB or something like this, but to control this information consumption I would put this failure information in a queue to be consumed according to the DB workload capacity.
I think it's a bit clearer, isn't it? @davydovanton
w
I think it's a bit clearer, isn't it? @davydovanton
Dry-transaction is not about db-transaction, its about business operation. Im not sure, that making several steps is a good way to have atomacy. And if one step fails and you can survive just having logs about that, that probably means, that you don't need db transaction
w
Im sure you are familiar with Saga pattern, right? https://blog.couchbase.com/saga-pattern-implement-business-transactions-using-microservices-part/#:~:text=A%20saga%20pattern%20is%20a,completion%20of%20the%20previous%20one.
G
Dry-transaction is not about db-transaction, its about business operation. Im not sure, that making several steps is a good way to have atomacy. And if one step fails and you can survive just having logs about that, that probably means, that you don't need db transaction
Sure, such pattern is a great strategy, and Richardson is a great developer. But I mean business operation indeed. But each fail I would like to persist in a storage or DB to the system know about it in a permanent way. For this reason I thought about this structure using a queue --> API --> DB to persist this failure info.
w
Sure, such pattern is a great strategy, and Richardson is a great developer. But I mean business operation indeed. But each fail I would like to persist in a storage or DB to the system know about it in a permanent way. For this reason I thought about this structure using a queue --> API --> DB to persist this failure info.
Then, i believe having ruby listener for you steps, which can use MQ client to queue events is what you need
w
You can skip mq and api part by storing events into db directly in a thread or by ActiveJob
G
Then, i believe having ruby listener for you steps, which can use MQ client to queue events is what you need
Hum, interesting this by-pass and storing events directly into DB by a thread or a job using ActiveJob
G
Thanks for the insights @wi11son
Д
Сколько будет стоить прога кредитного брокера с автоматической рассылкой в банки на пробивку клиента и ...или насколько сложно ее написать кто знает?
薛
