are there any prerequisites to learn GraphQL and can someone suggest the best course to learn graphql?
From my point of view:
SQL knowledge must needed one. Other than this no special techniques are needed for learning GraphQL. Initial stage you must go through the official documentation for better understanding.
official documentation Link: https://graphql.org/learn/
Related
I have to set up Elasticsearch search engine in my job website enterprise. We've choosen this solution becasue it's scalable powerfull and personalizable. As a beginner of ES, I've only set up basic functionnalities such as simple research on a test website, but nothing to complex. My goal is to implement step by step more complicated functionnalities like synonyms, multilingual results, filters... And so on.
I would like to know if you had to implement something like this, and if you have any tips and tricks about bests practices. Also note that I've already red a lot about ElasticSearch but there's so many content that any "roadmap" or learning resources is welcome.
I'll be happy to read your advices and experiences with this amazing tool, best regards.
Anyone knows if Socrata has plans to add GraphQL to their stack? Attribute=value querying + SoQL is very impressive and useful but GraphQL is starting available everywhere now.
We haven't ruled it out, so maybe at some point in the future we will support GraphQL, but it's not currently on our roadmap. Awesome tech though!
I'm building an API using KOA and have read some best practise on versioning. This answer pointed out that versions should be hidden from the client.
My question is, how would I go about doing this? I've read some mentions of using an API proxy. Would I be using something like "Squid" as a reverse-proxy, or are there better Node/KOA specific solutions for this type of work?
I think GraphQL is the perfect tool to avoid pain in the ass with API.
Yes, in some point it breaks the REST philosophy but gives flexibility.
All you need to build a flexible API with no worry about version is: Koa, Objection + GraphQL.
I'm looking for documentation about documenting an ElasticSearch deployment (you can see why this is challenging to Google!).
My question is really two questions. Are there best practices for documenting an ElasticSearch installation? -and- Are there any tools that aid in the visualization of an ElasticSearch installation. I guess it would be akin to a sql db schema (ER diagram or whatever). I've scoured Google without much luck and I didn't find anything on SO.
Documenting ES may be a bit more challenging than documenting a sql db since you probably want to be able to show the relationship between end user queries and indexing to explain the context of each mapping. Furthermore, it would be useful to visualize the cluster (perhaps a separate problem that could be solved with existing tools).
Thanks for any help.
If not, are there standards in existence for rules engine storage?
or
Is there a C# implementation of the Oracle Rules Engine syntax?
No.
I only have a little experience with Rules Manager and Expression Filter, and it's difficult to say if something is not based on a standard, but here's my reasoning:
Oracle seems to love talking about standards in their documentation. For example, there are many standards mentioned in the SQL Reference but there are none mentioned in the Rules Manager and Expression Filter guide.
As #Adam Hawkes mentioned, Oracle Business Rules Engine uses various standards, like JSR-94, and also the Rete algorithm. (But I'm in no position to judge how well they follow those standards.) However, Oracle Business Rules Engine and Rules Manager/Expression Filter are completely unrelated products. (Even though they're made by the same company and do almost the same thing.)
If there was a standard, someone on here would know about it and would have answered by now.
For similar reasons I'm also guessing the answer is No to the other questions.
The Oracle Business Rules Engine is supposedly an implementation of the Java "JSR 94" API. Not sure that there is a standard for the "storage" of the rules, but there is a standard for expressing/using the rules.