Please enable JavaScript.

Coggle requires JavaScript to display documents.

THE PROBLEM Rewriting the DB / CMS (My approach (Horizontally Scalable…

- - - - Every update of the operating system or the software you are using, not only costs a lot of money, but they also put you in front of the questions: "Should i do it? Will it work? Will it be backwards compatible?"
        And sadly most of the times the answer is "NO" ...for all three questions
    - - VBA is a proprietary "scripting" language, very poorly designed and it can only be used within the Microsoft collection of software, which leads you into enclosure.
    - - I do understand the need of an Office Suite and again, there is a better alternative of the entire Suite, for free, called LibreOffice, which has complete compatibility with Microsoft Office documents. The only problem would be a "missing font" (easily fixable)
  - - - No way of seeing how the CMS is interacting with the current database, in order to extrapolate functions and relations. A very economically aggressive approach to "hold you in their pockets". Not even mentioning the fact that you have no way to prove (at least to yourselves) that your data is not snooped.
    - - I really don't think you need me to give you a list on this, you know better how much those licenses cost and let us not exclude the licenses for antivirus software.
    - - It is public domain knowledge that Windows is not friendly with resources, and even less friendly as a server but you do not benchmark this everyday .
    - - Economically speaking, the comfort of the "point and click" environment that Microsoft offers, costs way too much for the quality of service, portability and performance that actually delivers.
- - - - Self explanatory! While licensing may vary, 99% of the software is free to use and free of charge.
    - - Linux Servers and services are inherently hardened and easily encryptable ( you wouldn't want your work to be snooped or compromised - say for instance - by a ransomware) and they are well known to run on very "thin resourced" devices. It is also very worthy mentioning that you are free of viruses.
    - - Here are just a few of the arguments that describe the efficiency
        of the technologies that i would use but the list can go on and on. This is what is defined as Scalability. See it as a vector, one direction, only forward.
    - - The importance of the OpenSource philosophy resides in the concept of having the code of a software, open to the public (normal users and developers) which can audit the software and enhance it where possible! On top of this, FANG companies heavily rely on Open Source software.
  - - - The choice is really massive here but CentOS is known as the free version of the Red Hat Enterprise Linux OS, which is the highest-end server and desktop operating system for big companies and enterprises. It is stable and very well documented!
    - - Both the Linux distributions and the software, often go under the umbrella name of LTS, which means that the software reached a certain stability and advancement that will not require updates (unless you want it to) for a very long time (usually 4 years) and you are guaranteed to get support for the entire LTS time span.
    - - Another aspect of the Open Source community is to deliver a decentralized software, which can work as efficient as possible on all Operating system platforms.
        Pyhton, for instance, works the same way on Linux as it does on Windows! (Unlike VBA which not only works exclusively on Windows, but it is strictly related to MS Office)
  - - - MongoDB is a NoSQL database and it works under the form of document storage in a very fast machine (and human) readable file format, called JSON, which at it's turn can be compiled into an even faster format called B(inary)SON.
        BSON is 10 times faster on iterating an SQL command than a traditional table based database.
        Highly used by services which handle big data and real time applications
        
        .
    - - Drop in replacement for MySQ, very well documented and cross platform support. I think it is enough to say that Google uses it. This is the perfect replacement for a traditional type of database. Full of features and very good for complex transactions.
        
        In order to make the right choice here ( both are strong ) it is important to ask:
        
        What is the cardinality of your current database? How many 1:1 or 1:N relations do we have? How many of them are actually legitimate and are not there just by commodity or lack of optimization.
        
        We are making accountability - do we use double entry bookkeeping? If yes, how much do we use it? ( e.g. one function every 10 operations or 8 out of 10 )
        
        The first question is aimed at optimizing the database since the very beginning, whether is MongoDB or MariaDB.
        The second question is fairly important as if you indeed make lot of use of DEB then MariaDB is preferred and encouraged to use.