Which aproach is better for stablishing a Moodle server, FOSS or Non FOSS?

Re: Which aproach is better for stablishing a Moodle server, FOSS or Non FOSS?

by Tim Hunt -
Number of replies: 0
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
Paying money does not magically make things work. Closed source software is not magically better than open source software. (Often quite the reverse.)

However, setting stuff up to work right does take time, and time from skilled people normally does cost money. And if you are experiencing problems, the the issue is probably that what you have has not been set up optimally, and is not well tuned.

So you are onto something, but I think that your problem is easier to understand if we state the problem more clearly.

You can focus on the 'intellectual property' of the software, and licences, but this is not really want you want.

What you want is a *service*. The service you want is reliable infrastructure that is well tuned to run Moodle. The advantage of building on Open source is that you have many choices for how to get that service.

The modern way to get well set up servers is to go to a cloud provider (e.g. AWS, which many people now use to run Moodle.) Amazon run millions of servers, so they have huge economies of scale, and are very good at it. You pretty directly pay for what you need as you use it.

Alternatively, you could pay a Moodle partner with the right expertise to give you some consulting on your current setup and how to tune it. (For Linux-y performance tweaking like this, Catalyst IT would probably be a good bet, but other partners are available.)

Or, you could hire a sysadmin with the right skills, and have them run your Moodle setup.

There are probably other options too, but paying for closed source stuff to run on-premise would be low down my list.
Average of ratings: Useful (4)