We are about to embark on an integration project between a Filemaker database and a website. The Filemaker database is all built and is being used on a daily basis. The website will have a mysql database.
The plan is to have the mysql database separate from the Filemaker database for:
2. Only a subset of information is on the website database
3. Ensure the Filemaker database is fast to use
4. Retain offline database capabilities should connectivity be lost.
So, if information is updated in the MySQL database it will be pushed to the Filemaker database and visa versa.
Anyone see any downfalls with this plan? Is this how it is done in the real world with enterprise systems? It could all be built with a single MySQL database but we don't really want to go down that track given the issues outlined above.