Does Optimistic Concurrency per object imply Serializability if a transaction will never span multiple objects?
Given a system which provides:
Matrix distribution to process grid
I need to write a program, which will perform LU-decomposition, etc. The problem is that I don’t know about the preferred way to distribute the loaded matrix from the root process to other processes. I’m able to create a simple algorithm for some situations, but I really need the solution which works for arbitrary number of processes.
Microservice architecture but with strong data consistency [closed]
Closed 1 year ago.
Contradictions in replication in the dynamo paper
This is the paper in question: https://www.allthingsdistributed.com/files/amazon-dynamo-sosp2007.pdf.
How does a flow of architecture of a digital banking system looks like?
I am working at a digital banking company i.e company that provides software for banks so that the customers of that bank can use banking services via smartphone.
Distribute jobs evenly among a set of servers
I have the need to distribute a set of long running jobs across a cluster of containers in ECS. These jobs essentially would need to open a socket connection with a remote server and begin streaming data for import into a database.
Multiple Databases per Microservice
We have a scenario in which all the important and transactional fields of our business entities are highly structured and relational. The data size of these important fields is also very small. However, there is a raw JSON associated with each entity that is very rarely updated (only in exceptional cases). However, most of our read APIs require all the data including the raw JSON.