Tektit Consulting GmbH

Our bustling colleague Michał Michalczuk is on his way to Berlin once again. Unlucky us, there will be no time for him to visit the Tektit Consulting GmbH office. Michał will be busy hosting two stages at the WeAreDevelopers World Congress 2024. We wish you lots of fun and success, Michał! And we are already looking forward to your insights...

https://lnkd.in/dqGcrKVZ my summary of the recent FOSS Backstage 2024 conference in Berlin. Thanks to Tektit Consulting GmbH for sponsoring my talk on https://lnkd.in/dqj56dxG

👉 Egal ob Zugriffskontrolle oder Notfallwiederherstellung, egal ob Datensicherung in der Cloud oder im Rechenzentrum – Schlomo Schapiro von der Tektit Consulting GmbH zeigt in seinem Vortrag auf unserer Secure #Linux Administration Conference, wie sich Herausforderungen rund um betriebliche Geheimnisse in modernen IT-Infrastrukturen lösen lassen. Sein Werkzeug der Wahl: Mozilla #SOPS (Secrets OPerationS). 🎟 Jetzt ein Ticket für unsere #SLAC vom 6.-8. Mai 2024 in Berlin sichern und mehr erfahren: https://www.slac-2024.de

Do you have a macro architecture for your development teams? The one thing which came to my mind is that at one point we did not have a shared understanding how we should build our system back when I was working at DHL E-POST. This was in ~ 2014. We split the monolith in multiple services. Every team (we had 10 teams) was doing it how they thought it would be good. Turns out the overall system was harder to use, full of surprises in the APIs (REST) and had different concepts when operating. Documentation was hard to find and different stakeholders had different ideas how things should be done. So we decided what is important in such a system. The main points for us to handle was: - State in applications (only DB, no local data, phoenix system) - Resilience (Loadbalancing, Consul) - Service communication (REST) - Documentation (Swagger, Pivio) - No shared databases between services - Request tracking (defined correlation ID) - Monitoring (Alarm books, health endpoints) - Logging (all to Splunk via syslog, Logformat) - How deployment is done, automated DB updates - Operations (1 VM per service) The only 'restriction' we had for teams in terms of how they write the service was the use of Java. If they wanted to switch they had to talk to the leadership team first. How the service is written, what the services does internally was left to decide to the teams. The main influence on their daily business was that they have to have meaningful documentation (e.g. Swagger, ADRs) and that they should be able to fix critical bugs immediately. Most of the other rules had the goal to make it easier to run in production, to make it easier to find bugs, to track requests. Since our main way of communicating between service, we even did our own version of the Zalando RESTful API Guidelines. This brought a lot of unification and shared understanding to all developers on how to develop REST service and not getting confused when consuming services. So we had to bring everybody together and get alignment how and what we should do. Every team send one person in a working group, we exchanged ideas, concepts and ways of implementing. Out of that we got our 'Rules of Play'. Since this was way before Corona and we were all in the office, I drew up a poster and put it in a few places in the office. This way and always repeating and insisting on it in meetings made our transition possible. Step by step, along user stories, the system changed and made it easier to use. Lots of these things are much easier to use today in off the shelf cloud systems. Yet, I see people sshing into kubernetes nodes to fix things manually, see log files in different formats and not having any documentation. If you have a few development teams and you are creating a distributed system, please make sure you have some guidelines to make the overall system easier to program, use and trace/debug. You need it. What did you put into your macro architecture? #softwarearchitecture

We turned a normal Tuesday into the bloodiest day in the history of Tektit Consulting GmbH: 5 members of the Berlin office crew swapped sandwiches for needles and hit the blood donation centre together! A great experience and more fun than expected for Kristin Wagler, Philipp M. Meschede, Oliver Wehrens, Matthias Paratsch and Carolin Sadrozinski. Every day, over 15,000 blood donations are needed for medical care in Germany. So there are still a lot of plastic bags to fill. We will be back. #BloodDonation #companyculture #lunchbreak #officeadventures

Tektit Consulting GmbH is also happy to grow in 2024. With Schlomo Schapiro, we have a technically high experienced Associate Partner on board. Welcome, Schlomo! We look forward to working together. #newemployee #tktgrowth #companyculture

The last days of the year are the time for donation. Donors in Germany will probably not reach the figures of previous years in 2023. According to the Deutscher Spendenrat E.V., 3.2 billion euros went to charitable organisations or churches up to September, compared to around 3.8 billion euros in the same period 2022. The main reason for the decline: Due to the inflation money is simply tight in many families. However, some potential donors also feel overwhelmed: Wherever you look, hardship and crises - who should you support first? Tektitans have donated to the following organisations this year. Perhaps it will help you to decide in favour of a good cause. Berliner Kältehilfe, Deutsche Krebshilfe, NABU e.V., netzpolitik.org, Plan International, Sea Shepherd Global, Straßenkinder e.V., The Great Orchestra of Christmas Charity, World Bicycle Relief

Our team keeps growing. Tektit Consulting GmbH proudly presents our two newjoiners. Please join us in welcoming Adin Halapic and Bola Oyebo. They are experienced product managers and will support us with their broad skillset in our mission. We are excited to have them in our team! #newemployees #tktgrowth #companyculture 

Are you ready to unlock the secrets behind transforming a business into a powerhouse of innovation and success? It all starts with a solid foundation. In our latest blog post, one of our founder Jacob Fahrenkrug describes the pillars we rely on at Tektit Consulting GmbH: https://lnkd.in/eH-hGt72 #companyculture #purpose #change

Our colleague Jacob Fahrenkrug spends a lot of time on his bike when he is not working for Tektit Consulting GmbH. Find out how we benefit from this as a team and what other companies can learn from this in our latest blog post: https://lnkd.in/e6kcpwDC #buildingbusiness #rebuilding #enduranceracing #biking