Hi,
I'm looking at SymmetricDS as an alternative for a coming project. We would like setup a proof of concept environment.
Our project consists of a central Oracle database server and hundeds of clients. Around 50 clients are working offline consistently and sync once per week or less. The rest is mostly online. There is around 30 datasets that will be used by different clients. Clients modify data while offline. Clients would use Windows tablets with Java application and an embedded database and SymmetricDS. We are looing also at MSSQLServer Express and master MS SQLServer replication as an option.
Basic use case from a client point of view:
1. auto registration with SymmetricDS master. We need figure out how to put him/her in a correct group to receive only his/her data.
2. create schema and fetch data set.
3. go offline.
4. capture data.
5. go online and sync.
6. repeat from step 3.
Thank you for any comments and suggestions,
Radovan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Radovan, all the requirements you mentioned sound like a very doable use case with SymmetricDS. For point #1, the "routers" in Symmetric control which nodes get which data. It is usually best if there is some sort of field within the data itself that indicates where it needs to go (it could be the node id itself or the store number in a retail example. That would be a column match router http://www.symmetricds.org/doc/3.9/html/user-guide.html#_routers).
Hi,
I'm looking at SymmetricDS as an alternative for a coming project. We would like setup a proof of concept environment.
Our project consists of a central Oracle database server and hundeds of clients. Around 50 clients are working offline consistently and sync once per week or less. The rest is mostly online. There is around 30 datasets that will be used by different clients. Clients modify data while offline. Clients would use Windows tablets with Java application and an embedded database and SymmetricDS. We are looing also at MSSQLServer Express and master MS SQLServer replication as an option.
Basic use case from a client point of view:
1. auto registration with SymmetricDS master. We need figure out how to put him/her in a correct group to receive only his/her data.
2. create schema and fetch data set.
3. go offline.
4. capture data.
5. go online and sync.
6. repeat from step 3.
Thank you for any comments and suggestions,
Radovan
Radovan, all the requirements you mentioned sound like a very doable use case with SymmetricDS. For point #1, the "routers" in Symmetric control which nodes get which data. It is usually best if there is some sort of field within the data itself that indicates where it needs to go (it could be the node id itself or the store number in a retail example. That would be a column match router http://www.symmetricds.org/doc/3.9/html/user-guide.html#_routers).
For a good intro, you could go through the tutorials at https://www.symmetricds.org/doc/3.9/html/tutorials.html
We also offer professional services for 6 months POC projects if you are interested at https://www.jumpmind.com/.
Let us know what specific questions you have.
Mark