Thorsten Gawantka
Unter „We proudly present“ möchten wir euch die Autor:innen unserer neuen Rubrik <code> IT vorstellen. Unsere klugen Köpfe teilen in dieser Rubrik gerne ihr Wissen und ihre Erfahrungen mit euch. Diese Woche erwartet euch der Beitrag „MicroService Toolbox als Container-Application“ von Thorsten Gawantka.
So that you can get a first impression of the people who will be giving you useful tips and tricks about development and programming in the future, we are introducing Thorsten Gawantka, Senior Consultant & Chief Architect at objective partner AG, to you today:
Hello Thorsten, how did you start developing?
Hello, I don't really know anymore. It was more of a smooth transition. From using or rather playing on the computer to "how do I fix the things I've broken" to "there must be more I can do".
And what are your core competencies at objective partner today?
I am currently working a lot with container technologies and microservice architectures. I also coach my colleagues and often act as the famous "rubber chicken" who listens and asks the right questions when necessary.
Which IT topics are likely to be of particular interest to you in the future?
All topics relating to container technologies such as Docker and Kubernetes. This also includes many topics relating to cloud-native applications and architectures.
Dann hoffen wir dort noch einiges von dir zu erfahren. Aber nun kommen wir erstmal zu deinem neusten Artikel. Dieser erscheint diese Woche in unserer Rubrik <code> IT. Worauf dürfen wir uns in diesem Artikel freuen?
To an outline of what the future of software looks like. From our point of view, of course. And what Docker and co. offer us in terms of development and operation, keyword DevOps. But without going into the topic of DevOps in particular. We'd rather save that for another article.
And what do you think doesn't work so well in practice with these topics?
There are many competitors who say "we do MicroServices" or "we run our software in a container". But if you then look at the architectures or the container image, you quickly realize that something is not right or is not being used as intended. This often makes the topics of microservices and containers complex, even though it doesn't have to be or shouldn't be complex.
The magic formula here is "Keep it stupid simple". If you stick to it, you'll get most things right.
Finally, we would like to know what characterizes your MicroService Toolbox and how container technologies simplify scalability requirements?
Our MicroService Toolbox, which consists of a set of MicroServices, is characterized by the fact that this set of services is required in some form in almost all projects. The toolbox can therefore be seen as a kind of "accelerator" with which a certain proportion of requirements can already be fulfilled and the rest can then be adapted in the corresponding service or implemented as additional services.
As these services are designed to be stateless, you can use Docker or Kubernetes to scale to almost any size. Load distribution is then handled by Kubernetes or Docker, for example.
Thank you very much for your time.
