I received an email from Lucie Fortier, Senior Director of Operations MLS Solutions, CoreLogic about their Matrix MLS system and it configurability ( I guess they been getting a few phone call lately for some reason).
” …I just wanted to confirm that Matrix has used a decoupled front end / back end architecture for more than a decade now. To achieve this flexibility, our engineers designed the system with an abstracted data connection layer that can utilize SQL, RETS, etc. Most any standard data source can be used with proper configuration. Since the early 2000s, MRIS has run Matrix against their own Oracle backend—the system was put together at the direction of, and in collaboration with, David Charron and his team. At MRIS, Matrix uses their Cornerstone relational database system as the sole repository of user-contributed information, including listings, offices, members, open houses… Anyway, this built-in capability of Matrix is not something we tout very often because most of our customers have had little interest in it. It’s just something we have always taken for granted…”
I had a conversation recently with some folks where we listed the top acquisitions in the real estate industry, and CoreLogic’s acquisition of Tarasoft and their Matrix MLS system has got to be number 1.
Lucy is correct. Its been a good relationship and has allowed us to focus loads of resources toward making our Keystone Listing Input module one of the best (OK the best!)
Ditto for NorthstarMLS.
We’ve had Matrix hanging off our Add/Edit and database since 2004.
Same Here, Corelogic is more than supportive in taking a data feed from our back end…and the whole idea that front end of choice means the server platform doesn’t actually function with a back end is silly…all front ends have a back end, but the vendor back end might be taking a RETS pull and then mapping it into the vendors data model for their front end