Skip to main content

How to architect passing data from a server to express routes without a database?

I am running a node.js application which upon startup uses fetch to call an external api (not owned by me) to grab data on a list of devices I own. Once I have this gotten this data from the fetch call I initialise an express server which is located in another file 'server.js' which itself requires an express Router defined in a subfolder 'routes' and mounted on the route '/api'. My question is, the data I initially fetch (which is a javascript object) can be modified by the express server I run, through post requests, and is periodically saved to disk by the primary application. Since the system I am running this on can't handle a database I just use a simple method of saving the data with the fs module.

What is the best way to architect the flow of data so that the main process which starts the express server can both view and modify the data in the javascript object as well as the post and get routes of the express router being able to have the same privileges?

I tested a rudimentary method where I just passed a reference to the javascript object to the express server and so the original object became the one 'source of truth' that could be modified by both express and non express functions. This felt wrong however and I was wondering if there was any better way of managing this data without using a database?

Via Active questions tagged javascript - Stack Overflow https://ift.tt/Jk789W3
Labels:

Comments

Post a Comment

Popular posts from this blog

Prop `className` did not match in next js app

I have written a sample code ( Github Link here ). this is a simple next js app, but giving me error when I refresh the page. This seems to be the common problem and I tried the fix provided in the internet but does not seem to fix my issue. The error is Warning: Prop className did not match. Server: "MuiBox-root MuiBox-root-1" Client: "MuiBox-root MuiBox-root-2". Did changes for _document.js, modified _app.js as mentioned in official website and solutions in stackoverflow. but nothing seems to work. Could someone take a look and help me whats wrong with the code? Via Active questions tagged javascript - Stack Overflow https://ift.tt/2FdjaAW
Post a Comment
Read more

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype
Post a Comment
Read more

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console
Post a Comment
Read more