1
2 Comments

Business logic/diagram to code execution

We've built an internal tool that allowed our business owners to create and edit the logic, that becomes executable, and no longer depends on engineering resources to modify.

Here is an example of what we use for business logic on selecting a driver for delivery from the pool (it is slightly simplified - it's essentially the set of basic operations, ifs, cycles, and set of input data, process variables, and output data).

Diagram to executable code

We maintain this in the versioned diagram that can be pushed to Lambda + API gateway, and essentially the platform code relies on that endpoint to provide a response.

For the project we are using it for, it allows us to make adjustments to the process without depending on engineering; another use case is pricing -- override and experimentation.

Again, the engineering team thinks it is cool and wants to productize it. I would really appreciate any feedback or ideas.

on April 6, 2021
  1. 1

    Who is the customer niche? The persona that buys this product?

    1. 1

      We do not have a product yet. I’m just evaluating it.

      As for the buyers, currently we work with business functions - Product and Operations - that need to add business logic without engineering resource and iterate on that.

      We also like to look at the problem from the lenses of user stories that require engineer resources to iterate, experimental or have a 4+ variable components that might have to be adjusted in the process.

      Whether it holds or not after customer development - I do not know yet.