That is the least of your worries when focusing on self-hosting. Most people would look at the final point, saving money that they have to pay for commercial service. So this was just a quick example of a negative side of self-hosting an important service.īottom line, if you want to self-host any service yourself, you need to be aware of what elements will need to be included in your decision making. Jump on your mobile device and use a 4G connection, problem solved. Sure, if those are down you might be completely unable to use a commercial service as well, but in some cases, you could. Well, that is not entirely true because power and the Internet are two elements that you also can't completely control right? If there is a major problem regarding those two elements your service will not work. You have no dependencies towards any element that makes your service run. From hardware all to way up to the service/app layer.
Well, to self-host a service would mean that you hold all the keys. So, first things first, what is "self-hosting"? Sure, some people will say that's nothing, others will simply say that is not for them and continue to use commercial solutions. There is a lot of things that go into making this work, and to make things more complicated, the more services you add, the more administration and maintenance you need to do. Now don't get me wrong, there is nothing wrong with using a commercial version, but the point of this article is to look at some positive and negative sides of both options.īefore I go further let me just say that I am all for self-hosting. Nowadays this might not be a question many people would ask themselves, but with the increased problems with privacy, security, cheaper hardware, more open source, and free software, it would be worth at least looking at the possibility of hosting your services on your hardware.
0 kommentar(er)
