In the context of this article, Node.js is the JavaScript Runtime that is used to compile and run the front-end framework of choice (React, Next, Angular, Vue) for development.
As you are saying, you can also run Node.js as a server-side Api or system.
I think what was misleading was the way you put it “nodejs or react “ rather could’ve specified that in the choice of react js that node is the runtime (chatty but needed clarification anyway)
“With the data cached at so many levels, how can we guarantee the sensitive user data is completely erased from the systems?”
Every cache entry need a time-to-live so it will time out and eventually a be discarded. Ground truth data storage and backups need a different strategy, likely annotations/metadata around which data is deemed sensitive so it can be deleted directly.
Amazing architectural documents.. But one challenge i see is all these architectures are designed to meet a purpose... But is there a way where we can have validation strategies around the architecture? If an architecture cannot be tested , it is tough to use , maintain , monitor , evolve etc...
I think "Node.js or react is popular for frontend development" is not absolutely correct as nodejs is mostly used for backend development.
In the context of this article, Node.js is the JavaScript Runtime that is used to compile and run the front-end framework of choice (React, Next, Angular, Vue) for development.
As you are saying, you can also run Node.js as a server-side Api or system.
I think what was misleading was the way you put it “nodejs or react “ rather could’ve specified that in the choice of react js that node is the runtime (chatty but needed clarification anyway)
I agree
“With the data cached at so many levels, how can we guarantee the sensitive user data is completely erased from the systems?”
Every cache entry need a time-to-live so it will time out and eventually a be discarded. Ground truth data storage and backups need a different strategy, likely annotations/metadata around which data is deemed sensitive so it can be deleted directly.
Amazing architectural documents.. But one challenge i see is all these architectures are designed to meet a purpose... But is there a way where we can have validation strategies around the architecture? If an architecture cannot be tested , it is tough to use , maintain , monitor , evolve etc...