Given the recent rise in text-based language models, sometimes called AI tools, I wanted to share my thoughts and experiences in using them,
especially in the context of blogging.
Now that we have talked about the benefits of running your own server
and how to run your own server let’s take a look at some things you could run on your own personal server
and some things you should better not.
In the world of technology, we are moving further and further away from operating directly on servers,
but there are still significant benefits to be gained from running a personal server.
I have been running some kind of personal server for many years now and I strongly believe anyone working in technology can benefit greatly from doing so.
Here’s why:
Running any kind of personal infrastructure sometimes requires your attention based on certain events or failure states,
no matter how much you automate tasks.
Over the years I have used E-Mail, Telegram bots and a variety of other tools for this purpose.
However all of them have the drawback that they mix with other kinds of information and are not easilly usable in scripts.
Ever since diving into the software development world I was troubled by a duality:
On the one hand I have built and operated many services described as monolithic with relative ease,
on the other hand I’m always told I, and others, should build microservices because they are better in a variety of ways.
With this post I’m going to compare both software architectures by looking at the key benefits often associated with microservices
and additional considerations I think are important.
