EA with MySQL Replication Vs Config mgmt tool

[Sreedhar]

Dear Friends,

I am seeking your suggestions and experiences with this topic.

We are planning to setup a EA repository can be accessible from different regions of the world (Country in Europe, Country in Asia).

We have tried the cloud service with EA 11. But not much success with this.

Hence, thinking to solve the problem with MySQL Master-Master replication or Having configuration management tool.

Please share your thoughts.

[Geert Bellekens]

I'm not sure if replication is going to solve your issue.
How will you deal with simultaneous changes to element in both databases?

You might want to explore the option of version control.

Using a central version control system and local databases might be the best solution for you.

Geert

[Sreedhar]

Well, when it comes to configuration management tool. I have few worries like...

1. As per the information provided in EA, We can only checkout the artifact at package level.

If i modify the element in the current package depends on other element  available in another package. What would be consequences ?

2. Once you checkout the package, Can other colleagues checkout element and able to modify within the package ??

Please suggest me.

[Geert Bellekens]

Checkouts in EA are exclusive. So if you check something out your colleague will not be able to check it out.

Usually inter-package dependencies pose no problems except for some exceptional circumstances.

Geert

[qwerty]

except for some exceptional circumstances.

I happened to encounter especially those cases in the past. Likely because the people that setup the initial model were not aware of the problems arising from that locking problem. Anyhow, I learned a lesson and used a central repository with EA locking with absolutely not issue from that time on. I would use a fallback to VC and distributed EAPs where needed.

q.

[Sreedhar]

Is it a worth try attempting VC in my case

[qwerty]

It depends - heavily. There are many pros and cons to weigh. For a distributed model with one main center it's a good idea to run the central system with just EA locking and have an integration team that decouples parts for the external teams which can access those parts via VC. It is possible to have a mix where you use VC also in the central system knowing those parts are meant for work off-site. You will not find the best solution in a first attempt. For a really large system you should hire consultancy that has done a similar job and help getting it up and running (I guess Geert would be a good candidate). Anyhow, prepare for a workshop to gather the requirements regarding config management...

q.