The idea is that FMS allows...
- High performance
- High availability
- Load balancing
... and it is not limited to a machine. ... although FMS uses an extremely powerful machine. ,..this is still just A machine (1).
Yes of course! These are coming slowy with the fail-over backupserver stuff.
But i've always wondered what would be next steps? Maybe then they would think about offering their own "iCloud?" FileMaker Server Auto-scaling instances service (something like AWS).
Currently you can split DB and WebDirect to two machines and use a backup one standby.
So we can currently have three.
Would be nice if FMS16 could have two DB server connected to each other, so both can serve users and keep data synchronized.
Than add two standby servers to take over in case of emergency.
And of course allow several servers to run WebDirect and use another DB server for databases.
You'll have it, and much more when we'll get this
Rewrite of Filemaker engine in SQL
I use FM because I don't want to use SQL.
The SQL structure is ONE of the paradigms with high rates of indexing speed (the oldest).
If the "developer" experience is maintained, I don't care if it is SQL, NoSQL, Columnar, Key/Value, etc...etc.
Hopefully FMS will be as powerful as the databases they comment on (especially when updating schemas). But what should not be touched is the paradigm that the "developer" user experiences.
If the creation of "Select, Insert, Update,...etc" indexes the schemes in a certain way, we must not forget that a graphical FM relation (depending on the number of attributes) is equivalent to : n x m Select (with a single relation). I think this is one of the things that makes FM so special.
I would think in a first phase, to improve the graphical interface of the E/R, or to improve the conditions of the components. For example: The condition dropdown lists can display your data without the need to add more table occurrences to the E/R model.
As I stressed multiple time, the experience would be exactly the same. There's no point changing the experience (except if you want to, and only if you want to, you'll be able to do queries in SQL)
Retrieving data ...