Now that we understand the different pieces of the conceptual model for building a digital twin of the lab, it’s time to turn our attention to implementation. But this isn’t going to be a lengthy tirade about why you should use a certain JavaScript framework or back-end language. Not this week, at least. Instead, I want to discuss some of the trade-offs that go into the overall design. And this week, I’ll start with choosing the right balance between flexibility and consistency.
> a sort of two-stage system where users can add small changes in real time as their needs evolve
This was done by Riffyn Nexus in a 'dynamic schema alteration' like process in 2017. Riffyn didn't exist long enough to release the second part (but it was in development).
> a sort of two-stage system where users can add small changes in real time as their needs evolve
This was done by Riffyn Nexus in a 'dynamic schema alteration' like process in 2017. Riffyn didn't exist long enough to release the second part (but it was in development).