Timeline for How to architecture and expose an API for creating custom data filters?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2017 at 8:27 | comment | added | Merott | @COMEFROM that's actually what I'm leaning towards. It makes it possible to delegate further filtering responsibility to external micro services. I just don't know of a service that does something similar to that, and I don't know how good/bad of an idea it is! :) | |
| Feb 14, 2017 at 8:12 | comment | added | COME FROM | Is it ever necessary to apply a custom filter to all of the data? Perhaps the service could always fetch 10000 or so persons near a given location and further filtering could be done on the client side. | |
| Feb 10, 2017 at 12:32 | comment | added | Merott | Thank you @KaseySpeakman. OData seems interesting, but it appears to be too limited for my use case. It provides some ideas though, thanks. | |
| Feb 7, 2017 at 15:13 | comment | added | Kasey Speakman |
@Merott If you read the link, you will see that OData has a filter specification. If you setup an OData service, then any client can filter data with $filter syntax. Assess whether it meets your needs. I do not what you mean "from an architectural point of view". I haven't seen any architectural questions. Exposing read-only data through an OData endpoint should not require much architecture on modern platforms.
|
|
| Feb 7, 2017 at 2:23 | answer | added | Vir | timeline score: 2 | |
| Feb 7, 2017 at 0:56 | comment | added | Merott | @COMEFROM please see my EDIT 2 | |
| Feb 7, 2017 at 0:40 | comment | added | Sophie Swett | @Merott Well, here's my one idea. A custom filter consists of a Lua program that runs on the server. The Lua program has access to an API for constructing and executing database queries. There are two challenges here: designing and implementing the API; and ensuring that the API has no security vulnerabilities (since executing untrusted code on a server, and giving it database access, is dangerous). A much, much easier (but less powerful) way would be to think of a couple of allowed filter criteria, and have a custom filter simply consist of a list of these criteria. | |
| Feb 7, 2017 at 0:25 | history | edited | Merott | CC BY-SA 3.0 |
add some clarifications
|
| Feb 7, 2017 at 0:17 | comment | added | Merott | @TannerSwett I fully appreciate that this is not a trivial challenge. I'm here because I thought there might be a genius solution to it that I just haven't thought of. If you believe this an impossible challenge, or that it's too costly, I'm still interested to hear your thoughts as an answer. | |
| Feb 7, 2017 at 0:15 | comment | added | Merott | @KaseySpeakman could you please help me understand how OData helps from an architectural point of view? | |
| Feb 6, 2017 at 16:09 | comment | added | Sophie Swett | It sounds like you're pretty much asking how to expose a public interface for making database queries. That sounds like the sort of thing that could be extremely difficult compared to the amount of benefit you're getting out of it. Consider only implementing features that you actually know are needed--do you want to take the risk of spending time and money implementing a feature that turns out to be unnecessary? | |
| Feb 6, 2017 at 16:00 | comment | added | Kasey Speakman | Have you considered OData? Some platforms have prebuilt libraries or templates to create OData services. | |
| Feb 6, 2017 at 15:08 | comment | added | COME FROM | How many records the database will contain at most? | |
| Feb 6, 2017 at 14:59 | history | edited | Merott | CC BY-SA 3.0 |
a better example
|
| Feb 6, 2017 at 14:39 | history | edited | Merott | CC BY-SA 3.0 |
added 179 characters in body
|
| Feb 6, 2017 at 14:35 | review | First posts | |||
| Feb 15, 2017 at 17:45 | |||||
| Feb 6, 2017 at 14:33 | history | asked | Merott | CC BY-SA 3.0 |