react-admin

This looks similar to React application frameworks like react-admin [1] or Refine [2]: const App = () => ( <Admin dataProvider={dataProvider}> <Resource name="posts" list={PostList} /> </Admin> ) const PostList = () => ( <List> <DataTable> <DataTable.Col source="date" /> <DataTable.Col source="title /> <DataTable.Col source="author" /> </DataTable> </List> ); The article mentions XML, but the true revolution is JSX itself, which lets you describe any piece of logic as a React element. This opens the possibility to create DSL for everything, just like in Python. [1]: https://github.com/marmelab/react-admin [2]: https://github.com/refinedev/refine

> "Are there examples of companies adopting this model?" Many examples across the industry: - Autodesk AutoCAD (closed) + Plugins/Addons (many open) - MS Windows (closed) + Many 3rd party programs (open) - Github (closed) + Github Actions (open) - Npm (closed) + Npm modules (mostly open) > "What are the potential benefits or pitfalls?" Benefits: - Harder to replicate, the company gets to keep the "secret sauce" a secret - Opening up a way to "extend" the platform means 3rd party developers add value to your system - The core isn't open, so less effort is required to maintain compare to OpenSource Pitfalls: - Closed-source is hard to verify, company is essentially saying "trust me bro" - Less innovation, as user's can't contribute to the core > "How does it impact community engagement and software adoption?" There's hardcore FOSS advocates

DynamoDB can't even represent SELECT * FROM items LIMIT 25 OFFSET 100. It's just not designed for that. It's not meant to be a relational DB replacement. How would you do it? Assume we want proper pagination, and not rewrite the app for cursor based "Load more" style pagination. Why? Because the React Admin provider API insists. https://github.com/marmelab/react-admin/issues/1510

react-admin https://github.com/marmelab/react-admin

React Admin (https://github.com/marmelab/react-admin) covers parts of what you describe. I have however a similar need for a Retool alternative minus the UI (configured via files).

Thank you all for the many great answers! Definitely a lot to look at! Currently Appsmith (and/or) Lowdefy seem to fit best for me. In case you're interested, these are all the products/resources given so far: http://superset.apache.org https://adsharma.github.io/flattools-programs/ https://adsharma.github.io/fquery/ https://apex.oracle.com https://app.spanrr.com https://arctype.com https://baserow.io https://bubble.io https://deepnote.com https://directus.io https://django-sql-explorer.readthedocs.io https://doc.seekwell.io https://docs.djangoproject.com/en/3.1/intro/tutorial02 https://first-django-admin.readthedocs.io/ https://frappeframework.com https://getzenbase.com https://github.com/appsmithorg/appsmith https://github.com/directus/directus https://github.com/marmelab/react-admin https://github.com/metabase/metabase https://github.c

Here are a few that are in the ball park, but mostly lacking the form bit (you have to make your own though most of these offer a way to have a append-only user for the form to act as): - Strapi (https://github.com/strapi/strapi) - Directus (https://github.com/directus/directus) - React Admin (https://github.com/marmelab/react-admin) - Netlify CMS - a bit off the mark but maybe worth considering (https://github.com/netlify/netlify-cms)

> Next.js APIs can reasonable handle (heavy DB migrations required, an admin panel, etc), You can reasonably handle those in next.js as well! For backend, I use hasura: https://hasura.io/opensource/ It's a GraphQL backend, that wraps a postgresql database, and handles the heavy lifting. GraphQL is very easy to work with in the javascript/typescript ecosystem. For admin UI, they're very easy to build with react-admin: https://github.com/marmelab/react-admin Wrapping them inside next.js is actually doable too, if that's a requirement (or it can be it's own react app, and you can share components between them).

> That said, I am curious if you have found this "linking" aspect of HATEOAS useful for actual implementations? I have been doing integration work with a system that strictly adheres to "REST level 3" and "HATEOAS" principles for the past few years, and I myself have found the "exploitability" of the API super handy. That said, the self-documenting nature only goes so far, and in the end I'm not sure the internal linking stuff is preferable to robust documentation. You're right, this is a reasonable question and the answer is uncomfortable. I personally find it useful when paired with OpenAPI -- generally by using annotations on controllers and models, but it is indeed rare to have usecases that fit the linking functionality well enough to be significantly better than what you would get from just good documentation. The "killer app" of th

React admin is a pretty good framework I've worked with. It's mature and very pleasant to deal with. It's also got data providers for many different databases. https://github.com/marmelab/react-admin

PostgREST: https://github.com/PostgREST/postgrest and http://postgrest.org/en/v6.0/ Sample PostgREST apps: http://postgrest.org/en/v6.0/ecosystem.html React-admin: https://marmelab.com/react-admin/ and https://github.com/marmelab/react-admin React.js: https://reactjs.org/ Combinations: - https://github.com/tsingson/ra-postgrest-client - https://github.com/raphiniert-com/ra-data-postgrest - https://reactjsexample.com/a-react-web-application-to-query-... - https://github.com/tomberek/aor-postgrest-client - https://github.com/priyank-purohit/PostGUI - https://awesomeopensource.com/project/priyank-purohit/PostGU... - https://www.reddit.com/r/learnpython/comments/bzrr1c/how_to_... More links: - https://github.com/topics/postgrest - https://duckduckgo.com/?q=%22postgrest%22+%22react%22&t=ffab... - https://duckduckgo.com/?q=%22postgrest%

Marmelab makes the pretty awesome react-admin library for autogenerating admin interfaces: https://github.com/marmelab/react-admin I'd love to see an official Marmelab adapter so I can build my admin interfaces with ReasonML.

Hasura and React Admin with Hasura RA data-adapter https://github.com/hasura/graphql-engine https://github.com/marmelab/react-admin https://github.com/Steams/ra-data-hasura-graphql

This looks pretty interesting! If anyone is looking for a tool to build a full fledge Back Office I warmly recommend react-admin (https://github.com/marmelab/react-admin/). Been using it for a year now and we went from 0 back office to a feature full one in no time!

I am a fan of opinionated full-stack frameworks, in particular for building B2B web applications which contain lots of CRUDL views. For an open-source solution that largely revolves around the React frontend, consider react-admin [1] + its adapter for Hasura [2]. [1]: https://github.com/marmelab/react-admin [2]: https://github.com/hasura/ra-data-hasura, https://github.com/hasura/graphql-engine/ In Ruby/Rails-land, there is https://bullettrain.co.