Our Experience
More Than 20 Years of Software Engineering
Behind KEME Software stands more than two decades of hands-on experience with software systems across diverse industries and technical environments. This encompasses greenfield developments as well as the ongoing evolution, analysis, and modernization of existing enterprise applications.
A few examples illustrate our approach:
Performance and Existing Systems
Evolved legacy software does not necessarily have to be replaced by a complete rewrite:
In an enterprise application, for instance, the response time of a core process was reduced from around 20 seconds to approximately 2 seconds.
In another project, a risk-controlling application was not only expanded with new functional features.
At the same time, the performance and memory footprint of the existing system were optimized.
Reliability in Live Operations
For us, software does not end with a successful build:
Our experience includes systems where operational reliability is critical.
This includes, for example, the development of a central ID generator for a 24/7 system (a German TV broadcaster).
In another system, the challenges lay at the interface with a third-party component.
Through a complementary integration solution, accurate and actionable monitoring data could be provided.
Productive Engineering Requires Realistic Environments
Not every problem lies within the application code. Development and test environments are equally part of a reliable software engineering process.
In an enterprise project, an existing application was therefore containerized.
This created a reproducible, production-like testing environment for the first time.
Docker was not the ultimate goal itself:
The benefit lay in more realistic testing, reproducible environments, and greater confidence when making changes to the existing system.
Understanding Domain Logic
Enterprise software mirrors real business processes.
Effective software engineering therefore requires understanding business domain requirements alongside the underlying technology.
Our project experience includes, for example, the development of Spring-based microservices for configuring and calculating investment funds, as well as work on banking and risk-controlling applications.
Especially with such systems, mechanically implementing a technical specification is not enough:
Business rules, edge cases, and established processes must be thoroughly understood.
Deploying New Technologies Productively, Fast
To us, long-standing experience does not mean working exclusively with familiar technologies.
In one project, for instance, a complete and beautifully designed application was delivered to the client within just a few weeks of adopting JavaFX. The knowledge acquired was subsequently shared with other interested developers through workshops.
This ability to ramp up rapidly is just as vital today as it was then.
Currently, KEME Software is again actively engaged in modern Android development. With MediTrackr, we are developing an in-house mobile application that serves as a practical implementation of current technologies and architectural patterns.
AI-assisted tools have also become part of our daily engineering workflow.
We view them as support for research, analysis, and problem-solving—not as a substitute for technical understanding, sound architectural decisions, or accountability for the resulting system.
New tools change how we can work.
The capability to critically evaluate results and understand why a solution works