Skip to content

Details

Two exciting topics, two very experienced speakers and much networking opportunity. We are very much looking forward to the next DevOps Meetup Zurich.
Here's what's planned for the evening:
17:30 - 18:00 - Arrival and first drinks
18:00 - 18:45 - Taming the Testing Beast by Peter Farkas
18:45 - 19:30 - Reintroducing "Infrastructure as Code" for Corporate IT by Torsten Boettjer
19:30 - 20:30 - Networking, Open Space & More drinks

Taming the Testing Beast
A once-mighty test framework, once the pride of a software department, had fallen into disrepair. Complex, unpredictable, and demanding, it had become a burden rather than a boon.

As development of the framework stalled, quality issues with the application it supported began to creep back. The team faced a daunting challenge: to tame the beast or be consumed by it.

This talk will explore the journey of the tech squad tasked with confronting this legacy system. We'll delve into the challenges encountered, the strategies employed, and the lessons learned. Ultimately, we’ll uncover the fate of the test framework: was it tamed into a powerful ally, or did it turn against its keepers, crushing them under its own weight?

Peter Farkas
Hi, I'm Peter. I'm an unyielding test automation engineer.

My passion for automated testing began during my master’s thesis, where I discovered the liberating power of unit tests. Since then, I've led testing initiatives in five large-scale projects across automotive, medical, and insurance industries.

Website: https://testgroove.ch/

Reintroducing "Infrastructure as Code" for Corporate IT
With a small team, we developed an alternative approach for Infrastructure as Code that enables a selective out-tasking of service operations to a cloud provider and enables enterprise operators to to benefit from the shared responsibility model for IaaS, PaaS and SaaS. A cloud domain controller exposes a single interface for a hybrid cloud to a DevOps team and integrates resources from multiple providers into an end-to-end deployment workflow. Per default, these workloads are distributed across four domains, an edge network, access services, the service backbone and core services. This reduces the attack surface for internal applications while employing robust, monitored and secured cloud resources for internet facing applications The controller is delivered as an appliance that can be deployed in the internal network to ease user management and secret handling. A landing zone is automatically defined based on the records in the application inventory, which is a massive reduction of efforts for every DevOps team. Separating service definitions and settings simplifies configuration adjustments when the portfolio evolves. Exposing configurations with a playground avoids CI/CD chains for infrastructure components, enables a fast onboarding process and allows developers and application managers to become agile, while operators remain in full control over their resources. The API eases the development of self-service portals, centralizes policy management, includes contract and cost management in the change process, and allows for continuous auditing, risk and compliance reporting.

Torsten Boettjer
IT executive and cloud expert, experienced in service design, implementation and operation. I’m passionate about digital transforming traditional and driving innovation with a commercial perspective. For nearly two decades I have been building clouds and digital platforms for companies like Deutsche Telekom, Swisscom, Cisco and Oracle. My personal fokus is on regulated industries like financial services, telecommunications or public services where cloud adoption is not simple.

Many thanks to our sponsors:

Related topics

Events in Zürich, CH
Infrastructure as Code
Quality Assurance
Software QA and Testing
DevOps

You may also like