I'm sorry to disappoint you, but this is a very bad idea.
Let's see what are the pros and cons of using FT as db layer of a website:
Pros:
- You can use basic geographic functions in your DB. I have to say most common databases have spatial extensions either built-in or provided as a plugin
- You can easily integrate a Google Map in your webpage displaying geo data from FT.
- No setup costs
Cons:
- Awful response times as Jack highlighted in his answer
- You are limited to a 0.5 request/sec on average. This is true for INSERT/UPDATE statements. Without throttling you will get lots of 500 errors back.
- Limited predicates in the WHERE clause. The case of the missing 'OR' !!
- Lack of the ability to create complex WHERE clauses.
- FT uses a NoSQL approach. Forget your typed columns.
- No relations or foreign key constraints. However you can join tables on attribute values.
- Using triggers/stored procedures or any common DB concept except views is not possible.
- Aggregate functions have really bad performace.
- So far no ORM supports FT that i know of. Some people think ORM's are useless but anyway this is something to consider.
And this is far from a complete list. In a nutshell: FT is not designed for what you're trying to use it. Period.