The previous post, Why ERP Needs a Definition-Driven Frameworkhttps://coderlegion.com/33030/day-1-why-erp-needs-a-definition-driven-framework, ended by promising this one would be about which decisions a framework should make on its users' behalf. T...

> The complexity of an ERP is not in how hard any single feature is. It is in how many times the same fact gets restated, multiplied by how many tables, multiplied again by how many customizations. A thirty-post series written for iThome Ironman 202...

This is the first post in a thirty-part series, ERP Architect's Notes: Designing a Definition-Driven Framework. What follows is not about building one form with some framework. It is about designing a framework that can drive hundreds of forms: whic...

JSON-RPC 2.0 is a small specification: the client sends {"jsonrpc":"2.0","method":"...","params":{...},"id":1}, and the server answers with a result or an error. REST makes you decide on routes, HTTP verbs and status codes; JSON-RPC only cares about ...