How do I go about designing this particular application example below?
For example:
I have client, who would like to embed my data feed into this GUI interface. The data is made of names and and descriptions fields. If a user comes along and searches a particular name of a products using the client’s interface, then the name parameter will be passed down my data feed, and it will return a search for that query name, back to the clients interface, from my database.
I assume the my real-time data feed will be constructed as an API service.
What requirements would I need to gather from the client’s system interface?
Would I need to ask them for the list of parameters they require to query through my data feed?
4
Would I need to ask them for the list of parameters they require to query through my data feed?
In a way: yes.
But are probably two ways you can achieve this:
- You ask them what they want to query on;
- You tell them what they can query on;
With the former this can lead to opening a huge can of worms, where your client will want to query on EVERYTHING with no constraints at all. If this approach is agreed upon, be prepared to say No when necessary and use common sense where relevant. If a parameter offers no value to search on, don’t agree to provide it as a searchable field.
With the latter you tell your client that all you provide to query on are parameters A, B, C. If they want more, i.e. customisation, then charge a few extra $$$
I suspect that you will come to some sort of common ground between your client asking for parameters and your decision to see that it adds value to use a field as a parameter.
Lastly, although the YANGI guys might saw something about this, will this be the only customer you have for your data? If you have 10 customers, do you really want to have 10 different custom search parameter criteria, that can take some time to program and configure for each customer? Or would you want to have a single set of possible search parameters that all customers use?
3