aeberhart's comments

On: Show HN: JSON Query

[aeberhart]

We wrote an article on this: "JQ vs. JSONata: Language and Tooling Compared". https://dashjoin.medium.com/jq-vs-jsonata-language-and-tooli...

On: Good read to find YAML data structures that cannot be expressed in JSON

[aeberhart]

* multiple documents in a single stream * any node type can be used as a mapping key * pointers via &anchor and *alias

[jjgreen → aeberhart]

Interesting read, thanks

[aeberhart → jjgreen]

In a way it's a very basic question, but I really had to search a while...

On: Ask HN: Experiences with low-code systems?

[aeberhart]

Disclaimer: I'm the creator of Dashjoin (https://github.com/dashjoin/platform)

Implementing the features you mentioned:

Once you connect your SQL / NoSQL database, you're immediately able to view, query, search, and edit the data. Every record implicitly has a "homepage". On this page, you can add active elements to automate tasks via REST services. We do this using JSONata (jsonata.org) which is a super expressive and concise transformation and query language. You can find some samples in our demo application (https://github.com/dashjoin/dashjoin-demo).

The core philosophy is to get immediate results and refine from there, depending on your cost / benefit calculation.

SDLC:

I think this is a very important point! Even though you're working with low code, it is still a development project with testing, staging, and production, issues, tickets, etc. We allow you to manage the software development lifecycle using GIT. You can view a sample project here: https://github.com/dashjoin/dashjoin-demo. It contains of the DB connectivity information, custom page layouts, queries, and REST function adapters. A developer commits changes to the repository. The production can be configured to pull a certain QAed version.

On: EE380 Talk

[aeberhart]

Great post and really worth reading. Quite shocking insights, for example on the e-waste of BTC: "an average of one whole MacBook Air of e-waste per "economically meaningful" transaction".

On: Show HN: No-code alternative to Retool, Appsmith, Internal, etc.

[aeberhart]

> What do you mean by automate tests? What exactly do you want to test?

One of our customers in the public sector builds a Low Code app that performs automated plausibility checks on forms submitted by clients. These checks can be quite complex since they reflect legislation. In this case it is crucial that you can mock form input and validate the checks against expected results.

On: Show HN: No-code alternative to Retool, Appsmith, Internal, etc.

[aeberhart]

I agree that once a project gets a bit more complex, these points are very important.

In our low code platform (https://github.com/dashjoin/platform), you end up writing several JSONata (https://jsonata.org/) snippets for ETL, actions, and visualizations.

These can be tested using junit. All changes to the app can be managed and deployed via GitHub. You can check out our sample app:

GitHub: https://github.com/dashjoin/dashjoin-demo Live: https://demo.my.dashjoin.com/

On: JSON Schema bundling formalised

[aeberhart]

I think so too. JSON Schema enables very useful tooling such as validation, Swagger-style UIs for interacting with services, or declarative web forms that people would have to build again and again.

On: JSON Schema bundling formalised

[aeberhart]

There certainly are some similarities, but I think JSON-LD and and JSON Schema solve different problems. You might find this article helpful (I ended up writing this after being confused by the various standards in this space): https://dashjoin.medium.com/json-schema-schema-org-json-ld-w...

On: Ask HN: Experience Running Neo4j in Production?

[aeberhart]

A question that can only be answered with "it depends..." :)

You might be able to simplify some of the queries using recursive SQL: https://en.wikipedia.org/wiki/Hierarchical_and_recursive_que...

Neo4J is a very popular DB (ranks #18 here https://db-engines.com/en/ranking) so should be mature.

Side by side would allow you to formulate queries depending on the use case, but of course this comes with quite some cost (keeping data in sync, having another system to take care of).

Neo4J allows you to store properties, so you certainly could model all your info (also the relational aspects) in it.

Hope this helps!

On: Show HN: Graphical ETL Based on JSONata

[aeberhart]

Thanks! No, $doc2data is not a standard function. JSONata allows you to define your own functions (https://docs.jsonata.org/embedding-extending#expressionregis...). JSONata is great for transformation and we added functions for loading data.