Hello Trader,

I just uploaded the next component, Json-DB. This is a "modernized" version of the DataBase engine I developed for EA Studio.

This database is straightforward for me because I understand it completely. This is not the case when I'm using third-party software components. No matter how thoroughly you study something you did not create, there are always questions about how exactly it works or the reasoning behind some solutions.

Link: https://github.com/PopovMP/json-db

I need to update and prepare several more components before assembling the backend server. I'm using parts of my previous projects to assemble the necessary libraries.

Extracting the code into separate modules makes it easy to optimize it or to find problems.

Another essential concept is Unit Testing. A unit test is a small program that tests the main program.

The JSON-DB has 87 unit tests.
Each test has a short description and checks whether a function gets the expected result when given particular parameters. All tests must pass before publishing software.

Example:

✔ dbProjection gets complete doc given {} (0.7249ms)
✔ dbProjection gets complete doc (0.1449ms)
✔ dbProjection gets partial doc (0.1486ms)
✔ dbProjection does not get _id by default (0.0871ms)
✔ dbProjection accepts excluding values (0.1057ms)
✔ dbProjection does not accept mixed values (0.9165ms)
✔ dbQuery gets all _id if the query is empty (1.1526ms)

Have a great holiday season!

Added parseJwtPayload to the JWT module.

It helps to parse the token information from an Authorization header.

I'll start assembling the server backend tomorrow.

It needs at least these essential components:
- configuration—it contains and provides the application's generic settings. It also reads private local settings.
- server - this is the main part of the backend. It will construct the request and the response objects
- server-request - it will parse the incoming request and will hold the properties in a handy way.
- server-response - it will compose and send the request's response.
- router - it will map the incoming requests by URL and will redirect them to the corresponding controller actions.
- public-server - it will deal with all public resources like: javascript files, images, styles, fonts, data files...

I have these components working in my previous apps, but I'll "modernize" them and make them suitable for future products without third-party dependencies.

My next steps are:

1) Make a stand-alone backend app using the previously listed components. It must be able to show a static webpage with the corresponding pages, scripts and stiles.

2) Add DataBase and API. Introduce a "User" model. Implement CRUD: Create, Read, Update, and Remove users remotely.

3) Make the basic frame of the application's client-side user interface. Make a Light and Dark theme

4) Make user forms for sign-up, login, change password, and reset password.

I hope all of these will be read to some extent next week. Then, I'll have the foundation of the new application and can start the work on the main functionality.

Happy Holidays!

I added an API functionality to Json-DB and cleaned up a lot of code.

I can now control the databases with remote requests.

> I think I get it, are you writing all the software from scratch?

I usually write a program once. Then, I rewrite it again for optimization, validation, or code cleanup purposes ten times.
This is not how professional software companies work. However, I consider myself an Independent developer and see programming more as an art than a job.

As for now, FSB Pro, EA Studio, and Express Generator are mature products.
Top 10 Robots App and Prop Firms Robot App are also more or less ready (though there are some issues, and I'm still working on improving the validation workflow).

I started working on a new product, which I'll introduce later.

I'm currently working on the server part of the new application. I'm trying to build a frame around which I'll later add the program's actual functionality.

Programming languages, software tools, technology and knowledge change with time. Therefore, I'm rewriting the components I used in the previous products.

(More particularly, I'm converting the code from CommonJS to ES Modules and applying the strictest possible validation with TypeScript, ESLint, and Unit Testing.)

> Is the specific purpose safety or performance?

I achieve better safety and performance, but this is a side effect of my work.
It happens because my programs use only the necessary code for the purpose.

> Or literally new software for another exporter
When the backend is ready, I'll start the work on the actual exporter