# MicroDoc Computersysteme GmbH - Complete Site Content > This file contains the full content of the MicroDoc website for AI/LLM consumption. > Last updated: 2026-09-08 ## Company Information - **Company Name**: MicroDoc Computersysteme GmbH - **Founded**: 1991 - **Experience**: 35+ years in IT industry - **Team Size**: 64 software experts - **Projects Delivered**: 5,655+ - **Headquarters**: Munich, Germany - **Parent Organization**: Part of Akkodis ## Mission Statement Based on our 33 years experience in the IT industry, we offer project services that help you win the software technology race. Expert solutions for Automotive, Energy, Finance, and Enterprise Software. --- ## Services Overview ### Embedded Development with Rust Maximum performance, absolute security, unmatched reliability. Rust combines efficiency and security for microcontrollers, IoT devices, and embedded systems. Services include: - Consulting and concept development - Driver and application development - Code review and optimization - Training and workshops ### Cloud Development Scalable, flexible, cost-effective cloud solutions. Services include: - Cloud architecture and consulting - Migration and integration - Cloud-native application development - DevOps and CI/CD automation - Managed services ### Embedded Java Platform-independent, powerful embedded solutions using optimized Java runtimes. Services include: - Architecture consulting - Custom software development - Performance optimization - Training programs ### Code Reviews & Quality Assurance Professional code quality services including: - Manual expert code reviews - Automated static analysis - Security audits - Performance optimization - Compliance verification --- ## Industries ### Automotive Vehicle software, telematics platforms, fleet management, connected car solutions, in-vehicle Java runtimes. ### Energy Smart grid integration, home energy management systems, renewable energy platforms, IoT energy devices. ### Finance Banking software modernization, transaction systems, compliance solutions, security implementations. ### Industrial Automation PLC integration, factory automation, Industry 4.0, cloud-connected industrial systems. --- ## Success Stories & Technical Articles ### Pentesting - **Date**: 2026-07-15 - **Category**: automotive, services - **URL**: /Pentest/ A step-by-step look at how a professional penetration test unfolds, from scoping and reconnaissance through controlled exploitation to reporting and remediation, and why it gives organizations proof, not assumptions, about their real-world security exposure. How a Penetration Test Is Conducted: From Start to Finish A penetration test is one of the most effective ways to understand how well an organization’s defenses would stand up against a real-world attack. Unlike a simple vulnerability scan, a penetration test is a controlled, authorized exercise that combines technical analysis, manual testing, and realistic attack simulation to identify weaknesses before criminals can find them. For businesses that handle customer data, support remote work, use cloud platforms, or rely on web applications, penetration testing provides more than a checklist of issues. It reveals how an attacker might think, where your exposure truly lies, and which risks deserve immediate attention. Just as importantly, it helps security teams, IT staff, and leadership align around practical remediation priorities. Below is a clear look at how the process works, from preparation with the client to reporting and remediation. Scoping and Preparation Every successful penetration test begins with planning. Before any testing starts, the security provider and the client define the scope of the engagement. This is one of the most important parts of the process because it establishes what will be tested, how it will be tested, and what should remain off limits. The... --- ### Certificate Dashboard - Simplifying Certificate Management - **Date**: 2025-10-13 - **Category**: automation, services - **URL**: /Certificate-Dashboard/ Browser vendors are tightening certificate lifetimes — dropping from 398 days to as little as 47 days by 2029. Certificate Dashboard helps you stay ahead with automated tracking, renewal, and future cloud PKI integration for secure and effortless device certificate management. The web security landscape is undergoing a significant shift. Major browsers and certificate authorities have agreed to reduce the maximum lifetime of TLS/HTTPS certificates over the next few years. Starting in 2026, the maximum certificate lifetime will drop from 398 days to 200 days, and eventually to just 47 days by 2029. This initiative, led by the CA/Browser Forum, is designed to strengthen security across the internet by limiting the impact of compromised certificates and encouraging better automation practices. Shorter certificate lifetimes mean that even if a private key is exposed or misused, the window of opportunity for an attacker is dramatically reduced. In fast-moving cloud-native environments, this change aligns well with existing automation and DevOps practices. However, for device-centric and industrial systems, the implications are more complex. In many industrial, embedded, and operational technology (OT) environments, certificates are still managed manually. Devices may be deployed in remote locations, operate continuously with limited maintenance windows, or be maintained by teams that already juggle multiple operational responsibilities. In these contexts, certificates are often treated as a “set it and forget it” configuration item, something that works quietly in the background until it suddenly doesn’t. As certificate lifetimes shrink, that approach becomes... --- ### From PLCnext to the Cloud: streaming OPC UA Data to Azure Event Hub and AWS Kinesis with Rust. - **Date**: 2025-09-04 - **Category**: automation, services - **URL**: /from-plc-to-the-cloud/ This article explores how to stream industrial OPC UA data from PLCnext controllers to Azure Event Hub and AWS Kinesis using Rust for seamless cloud integration and real-time analytics. When the line‑manager noticed a sudden temperature spike on a CNC machine, the only thing he could do was stare at the PLC screen and wait for an alarm that arrived minutes later. Imagine that same spike being pushed to a cloud dashboard in real‑time, triggering an automated shutdown before damage occurs. What if every critical sensor reading could be streamed to the cloud in milliseconds? Why Bring PLCnext Data to the Cloud? Industrial plants generate a flood of sensor readings, alarm states, and diagnostic logs. Keeping that data locked inside a factory‑floor controller creates several practical bottlenecks. Moving the data to the cloud solves those problems and adds new business value. Detect anomalies early – cloud‑based analytics can spot patterns that a local PLC would never notice. By using an event‑driven subscription that pushes updates only when values change beyond configured thresholds, we reduce network traffic and minimize the controller’s CPU load, while still preserving enough granularity for effective monitoring. Scale insights – a single Event Hub or Kinesis stream can ingest millions of events per day, far beyond the storage capacity of a PLC. This means you can keep historic data for months without expanding on‑prem storage. Learn across... --- ### GraalVM vs CRaC - **Date**: 2025-07-24 - **Category**: products - **URL**: /GraalVM_vs_CRaC/ When it comes to improving Java application startup performance, CRaC (Coordinated Restore at Checkpoint) and GraalVM Native Image represent two distinctive strategies. CRaC (Coordinated Restore at Checkpoint) and GraalVM Native Image represent two distinct strategies for improving Java application startup performance. Although they are often grouped together, they differ substantially in execution model, optimization strategy, and operational constraints. Existing discussions of CRaC are largely promotional, with limited availability of independent benchmarks and incomplete treatment of trade-offs. Performance claims, particularly regarding the absence of runtime overhead, are frequently presented without sufficient qualification. This post is not a tutorial, and it is not marketing. The goal is to explain, at a high level, how CRaC and GraalVM Native Image differ conceptually, how those differences show up in benchmarks, and when one approach is likely a better fit than the other. Prerequisites and scope This article assumes familiarity with the JVM execution model: bytecode interpretation, JIT compilation, deoptimization, and garbage collection. The focus will be placed on startup behavior and steady-state execution speed, not on JVM internals or framework ergonomics. The startup problem The JVM delivers excellent peak performance, but it takes time to get there. Initialization work, followed by JIT warm-up, can dominate execution time for short-lived processes. When a service starts frequently, scales aggressively, or is billed per CPU-second, that warm-up cost becomes... --- ### MicroDoc signs strategic framework agreement with Daimler Truck AG - **Date**: 2025-07-24 - **Category**: products - **URL**: /Daimler-Framecontract/ The road to the next generation of transportation isn’t just paved with asphalt — it's built on code. And throughout 2028 MicroDoc will be a strategic partner in that future. We are thrilled to announce that Daimler Truck AG and MicroDoc have officially signed a Strategic Framework Agreement, solidifying a partnership that will drive software innovation through the end of 2028. This milestone marks far more than a contract extension. It represents a shared commitment to redefining the Software-Defined Vehicle (SDV) landscape and to building the digital foundations that will power the future of commercial transportation. As the commercial vehicle industry continues its rapid transformation, software has become a central differentiator. From connectivity and telematics to automation, security, and DevOps-driven development pipelines, modern trucks are increasingly defined by the intelligence embedded within them. This long-term agreement establishes a strategic partnership designed to support Daimler Truck’s growing software development needs in an increasingly digitalized and interconnected market. A Legacy of Performance, a Future of Scale MicroDoc is a software licensor specializing in Java technologies and has served as an engineering service provider for Daimler Truck since 2008. Over the past 15+ years, MicroDoc has become a deeply embedded partner—often operating as the engine under the hood of Daimler Truck’s digital infrastructure. During this time, MicroDoc engineers have contributed to a broad spectrum of mission-critical initiatives, including: The development and maintenance of... --- ### Migration of CI/CD Routines from Atlassian Bamboo to Jenkins - **Date**: 2025-07-24 - **Category**: products - **URL**: /Bamboo-Migration/ A strategic approach to migrating CI/CD pipelines from Atlassian Bamboo to Jenkins for a large German financial services provider. In the landscape of modern DevOps, migrating from Atlassian Bamboo to Jenkins represents a significant architectural shift. While both tools aim to solve the same core problem — automated build, test, and deployment pipelines — their philosophies differ substantially. Bamboo relies heavily on UI-driven configuration through “Plans” and “Tasks”, whereas Jenkins promotes a declarative, code-centric model through Pipeline-as-Code using Groovy DSL. This transition becomes especially complex when the inherited infrastructure spans hundreds of legacy build routines accumulated over many years. In such environments, the primary challenge is not the sheer volume of builds, but rather the lack of standardization across teams. Tooling inconsistencies — most notably in the use of Maven — often reflect historical decisions, evolving requirements, and varying levels of DevOps maturity. Addressing these discrepancies while maintaining delivery velocity is the core problem this migration aims to solve. Understanding the Architectural Shift: Bamboo vs. Jenkins Before addressing implementation details, it is important to understand the conceptual gap between the two systems. Bamboo encourages centralized, UI-managed pipelines where logic is distributed across tasks, variables, and shared configurations. Over time, this often leads to implicit behavior that is difficult to trace or version. Jenkins, on the other hand, treats pipelines... --- ### Bringing Intelligence to the Edge: MicroDoc’s New PLC Tools for OPC UA and Cloud Integration - **Date**: 2025-06-02 - **Category**: automation, services - **URL**: /plc/ We are excited to announce our entry into the world of PLC application development with two lightweight, yet powerful tools built specifically for industrial automation environments. As the demand for smarter, more connected edge devices grows, we are stepping up to deliver efficient and developer-friendly solutions that run directly on programmable logic controllers (PLCs). Today, we’re proud to introduce two new applications designed to bring intelligence, visibility, and connectivity to PLC devices: OPC UA Browser for PLC Diagnostic Cloud Azure for PLC These apps mark the beginning of our commitment to empowering industrial systems with modern software tools that are fast, reliable, and ready for the challenges of Industry 4.0. Why Rust Matters in Industrial Edge Computing A key pillar of our development strategy is the choice of Rust as the core programming language for the backend of both applications. Rust’s unique combination of high performance, memory safety, and concurrency support makes it ideal for resource-constrained edge devices like PLCs, where reliability and speed are critical. Unlike traditional languages commonly used in industrial software, Rust eliminates entire classes of bugs related to memory management — a frequent cause of crashes or security vulnerabilities. This means our apps run faster, safer, and with less downtime, empowering industrial operators with dependable tools that will not fail when it matters most. By leveraging Rust, MicroDoc is setting a new... --- ### MicroDoc at JavaOne 2025 and the Java Community Process - **Date**: 2025-06-02 - **Category**: press, products - **URL**: /java-one-jcp/ MicroDoc participated in JavaOne 2025, celebrating 30 years of Java. As JCP Executive Committee members, we help shape Java's future. From March 18–20, 2025, MicroDoc participated in the annual JavaOne conference in Redwood Shores, CA, a premier event that has brought together Java developers worldwide since 1996. This year’s conference was especially momentous as the Java community celebrated 30 years of the platform’s innovation and evolution, highlighted by the release day of Java 24. Java 24 introduces significant language enhancements, new features like Stream Gatherers, Structured Concurrency and Scoped Values. Additionally, the conference spotlighted groundbreaking projects embracing AI, alongside advancements in Post-Quantum Cryptography to future-proof Java’s security. MicroDoc’s involvement goes beyond attending events. As a member of the Java Community Process (JCP) Executive Committee, MicroDoc plays an active role in guiding the evolution of Java technology. The Executive Committee oversees the approval of Java Specification Requests (JSRs), reconciles technical challenges, and ensures the ongoing stability and progress of the Java platform. Participating in both the conference and JCP activities underscores MicroDoc’s commitment to advancing Java and contributing to the broader developer community. --- ### MicroDoc is re-elected to the Java Executive Committee 2024 - **Date**: 2024-11-18 - **Category**: press, products - **URL**: /microdoc-is-re-elected-to-the-java-executive-committee-2024/ MicroDoc has been re-elected to the Executive Committee of the Java Community Process. Alongside other leading tech companies, including Oracle, Alibaba, BellSoft, BNY Mellon, JetBrains, and SAP SE, MicroDoc will play a pivotal role in shaping one of the world’s most widely used programming languages. The JCP Executive Committee (EC) is a group of members that steers the evolution of Java technology within the Java Community Process (JCP). The EC represents both key stakeholders and a broad cross-section of the Java Community. This year, there were 6 Ratified, 2 Elected, and 1 Associate Seats open for election. Detailed election results Voting Period: 5 - 18 November 2024 Number of Eligible Voters: 912 Percent of Eligible Voters Casting Votes: 25.22% Number of Full and Partner Members Eligible to Vote: 415 Percent of Full and Partner Members Casting Votes: 25.06% Number of Associate Members Eligible to Vote: 497 Percent of Associate Members Casting Votes: 25.35% Ratified Seats: Candidate Yes votes (%) No votes (%) Abstentions Alibaba 73 (86) 12 (14) 19 BellSoft 86 (97) 3 (3) 15 BNY 69 (87) 10 (13) 25 JetBrains 95 (98) 2 (2) 7 MicroDoc 70 (90) 8 (10) 26 SAP SE 82 (89) 10 (11) 12 Elected Seats: The top two (2) candidates have been elected. Candidate Votes (%) Eclipse Foundation 86 (46) Microsoft 52 (28) Google 47 (25) Abstain 2 Associate Seats: The top one (1) candidate has been elected. Candidate Votes (%) Deep Netts Technologies 51 (42) A N... --- ### Learning about Function Foreign Memory with a Neural Processing Unit - **Date**: 2024-03-24 - **Category**: products - **URL**: /ffm_test_with_rknn/ Explore Java's Foreign Function Memory (FFM) API in JDK 22 by benchmarking matrix multiplication on a Neural Processing Unit (NPU). Introduction Do you know Foreign Function Memory (FFM)? It’s a part of the Java runtime that allows developers to directly manipulate virtual memory contents. It has been in development for the past few JDKs and is now coming as a fully-fledged feature into JDK 22! We’ve been looking at this latest iteration, and how to do stuff with it. Moreover, the tool jextract generates Java sources from a C header, thus providing a primitive way to call functions provided by the native library. Since we’re working on embedded development at this time, we took an example that is specific to embedded development. We’re multiplying matrices on a Neural Processing Unit (a.k.a., NPU, basically a specialized processor). We’ll compare the performances with similar C++ code. As the JDK Enhancement Proposal for FFM is quite detailed, we’ll try to give you a simpler overview and examples. What is Foreign Function Memory (FFM), and how do I use it? /!\ As the API has been changing over the last few iterations, be sure to check the documentation for the version you plan to use: JDK22 iteration! Very basically, FFM is trying to replace JNI, with a particular focus on safety, performance and generality.... --- ### Future-Proof Home Energy Management - **Date**: 2024-01-01 - **Category**: energy - **URL**: /EnergyBASE/ MicroDoc's role in developing EnergyBASE, an advanced platform for smart home energy management with embedded Java and IoT integration. In collaboration with our client, we played a key role in the development of EnergyBASE – an advanced platform for smart home energy management. Our expertise lay in embedded software engineering, architectural design, and ensuring overall system reliability through rigorous test-driven development. Additionally, we delivered the optimized Java runtime environment required to run critical components on the embedded device. Platform Overview EnergyBASE is built on a Linux-based ARM platform and is designed to monitor and control a wide range of household energy devices in real time: Photovoltaic inverters for solar energy generation Battery storage systems to optimize consumption and reduce grid dependency Wallboxes for electric vehicle charging Heat pumps and heating rods for thermal management Smart power sockets for load control Grid connection monitoring to balance import and export behavior Our Contribution Communication and Integration Our team was responsible for major parts of the system’s communication and integration logic. Together with the client’s engineers, we co-designed a modular and scalable software architecture that ensures maintainability and fault tolerance. A particular focus was placed on integrating energy devices via Modbus, both serial and TCP, allowing the system to reliably read energy values and issue control commands. Cloud Connectivity To enable cloud... --- ### Cross compiling Java application with MicroDoc GraalVM Embedded - **Date**: 2023-11-08 - **Category**: products - **URL**: /building-graalvm-native-images-maven-gradle/ We illustrate how to debug the native image of a Java application, produced by MicroDoc GraalVM Embedded, and running on a remote embedded device. The debugging experience is illustrated both inside the IntelliJ IDEA and VSCode IDE. The embedded device runs Linux on an ARMv8-A processor (running in AArch64 mode), like a Raspberry Pi 4 or 5. Building Java native images using MicroDoc GraalVM Embedded with Maven and Gradle ⏩ TL;DR (too long; didn’t read) Read documentation of Native Image on https://www.graalvm.org/latest/reference-manual/native-image/#build-a-native-executable Configure native-image options to enable cross compilation. 🏗️ Build a native image on the build computer In order to build a native image for a target device, we need to specify some options to native-image. For example: $ <somewhere>/graalvm/bin/native-image \ -O0 -g -cp <somewhere>/bin -o <somewhere>/hello-world --target=linux-aarch64 \ --native-compiler-path=<somewhere>/aarch64-none-linux-gnu-gcc \ --native-linker-options=-L<somewhere>/lib \ -H:+UnlockExperimentalVMOptions \ -H:+UseCAPCache -H:CAPCacheDir=<somewhere>/cap-cache/aarch64-linux-gnu \ -H:-UnlockExperimentalVMOptions \ com.example.HelloWorld This builds the executable <somewhere>/hello-world that runs on the target device. ⚠️ When building debug native images of your application, consider using the following options: -H:-StripDebugInfo and -H:DebugInfoSourceSearchPath=<somewhere>/src Building with Maven We recommend using the official Maven plugin for GraalVM Native Image building. Please follow the instructions on the official documentation and specify the following options in the profile section: <profile> <id>native-aarch64</id> <build> <plugins> <plugin> <groupId>org.graalvm.buildtools</groupId> <artifactId>native-maven-plugin</artifactId> <version>${native.maven.plugin.version}</version> <extensions>true</extensions> <executions> <execution> <id>build-native</id> <goals> <goal>build</goal> </goals> <phase>package</phase> </execution> </executions> <configuration> <fallback>false</fallback> <agent> <enabled>true</enabled> </agent> <buildArgs> <buildArg>--target=linux-aarch64</buildArg> <buildArg>--native-compiler-path=$somewhere/aarch64-none-linux-gnu-gcc</buildArg> <buildArg>--native-linker-options=-L$somewhere/lib</buildArg> <buildArg>-H:+UnlockExperimentalVMOptions</buildArg> <buildArg>-H:+UseCAPCache</buildArg> <buildArg>-H:CAPCacheDir=$somewhere/cap-cache/aarch64-linux-gnu</buildArg> <buildArg>-H:-UnlockExperimentalVMOptions</buildArg> </buildArgs> </configuration> </plugin> </plugins> </build> </profile> In orde to build the target image, you need to specify the profile when ubuilding with Maven: mvn... --- ### Building and debugging Java native images of MicroDoc GraalVM Embedded - **Date**: 2023-10-16 - **Category**: products - **URL**: /debug-graalvm-native-images/ We illustrate how to build and debug the native image of a Java application, produced by MicroDoc GraalVM Embedded, and running on a remote embedded device. The debugging experience is illustrated inside the VSCode IDE. The embedded device runs Linux on an ARMv8-A processor (running in AArch64 mode), like a Raspberry Pi 4 or 5. MicroDoc specializes in the individual development of embedded software solutions using Java and GraalVM technology. From Munich, Berlin and Stuttgart, our teams of experts serve our customers from the following business areas: automotive industry, mechanical engineering, energy supply and telecommunications. The GraalVM is the new technology in terms of platform-independent programming. Not only in terms of performance, but also through the support of other languages such as Python and JavaScript, you have all the possibilities of modern software development in the embedded area at your disposal. An important point in the development of software is always the possibility of debugging your own application. This becomes even more relevant as applications and systems become more complex. Simple and clear debugging directly on the embedded system also reduces the risk of failures and associated costs in production. This article illustrates how to build and debug the native image of a “HelloWorld” Java application, produced by MicroDoc GraalVM Embedded and running on a remote embedded device. The local computer, used for building and debugging the native image, is a Debian Linux/AMD64 system. The debugging experience is illustrated inside the VSCode Integrated Development Environments (IDE). The embedded device runs Linux on an ARMv8-A processor... --- ### Embedded Java - **Date**: 2023-01-15 - **Category**: services, products - **URL**: /embedded-java/ Explore the evolution of Java for embedded devices from 1991 to today, including Java ME, compact profiles, and GraalVM native images. When you search for “embedded Java” or “Java embedded” you will end up with a couple of Wikipedia entries and a link to the Oracle website that provides very generic information about “Java SE Embedded” version 8 - period. Mainstream Java is heading towards version >20 nowadays … so what’s going on with Java in the embedded space? Let’s start with a quick look back in time. The technology called “Java” was initially developed by a couple of smart engineers at Sun Microsystems during 1991/92. Originally it was developed to provide an object oriented and hardware/OS independent programming and runtime environment for embedded systems. The idea was to create a uniform and portable programming platform with automatic memory management and robust execution of code in a virtual environment. By using a VM (virtual machine) programmers would automatically avoid otherwise common problems like crashes caused by buffer overflows and faulty pointer arithmetic. Object oriented programming for embedded systems was a relatively new idea in the 90ies – and the embedded community was very skeptical. The Java programming language was designed to be interpreted during runtime and as such intrinsically slow and resource hungry. And even though the first Java release only... --- ### Modular telematics and fleet management platform for smarter cars and trucks - **Date**: 2022-08-19 - **Category**: automotive, stories - **URL**: /modular-telematics-and-fleet-management-platform-for-smarter-cars-and-trucks/ We know a thing or two about making cars and trucks smarter. Over a period of 15 years, our software experts have made significant contributions to fleet management systems, telematics platforms and infotainment systems for passenger cars and trucks. Our excellent software engineers made the MicroDoc platforms and applications portable, maintainable, and open for extensions in the future. But our strength is not only about technology. Our innovative teams also tackled new business models and engagement forms: from traditional consulting and programming services which developed into a system integrator to helping customers in operating their complex computing environments with DevOps engagements. At the core of our success within the automotive sector, is our capability to create custom virtual machines on non-standard embedded platforms. The first telematics and fleet-management project started over 15 years ago with a porting job of an embedded Java™ virtual machine for a small handheld computer. We were engaged to only implement Java on handhelds for Germany’s leading truck manufacturer, who had spawned a project to optimize logistic processes for their fleet of freight trucks but our profound knowledge in mobile computing led to further cooperation in their application development domain. The decision to use Java as a programming language for the solution as well as the introduction of a proper and extensible component architecture in the software, was a key factor for the client. The customer solution was extended and expanded continuously, supporting multiple generations... --- ### Internships at MicroDoc – We want to give students a chance to gain hands-on working experience - **Date**: 2021-06-16 - **Category**: press - **URL**: /internships-at-microdoc/ Creating a positive and engaging working environment, that attracts and keeps employees, is an important ambition for MicroDoc. Our employees are our most important resources and as employer, we see it as our responsibility to continuously attract new talents and enable a great start into their careers. Our aim is to provide students with the opportunity to gain experience from working within ICT and explore what alternative specializations there are to pursue. The advantage of our internship is that they can do it in a safe environment and rely on a mentor that can guide them with their challenges. Scholarship programs during bachelor or master studies Here at MicroDoc (a leading supplier of Java™ technology), we are always seeking for specialists and full-stack developers, so if you are interested in an exciting challenge, you can read more about how MicroDoc uses scholarly programs to help students gather working experience and build a professional network. We have asked two of our interns, Rahel and Anton, and their mentor, Regine, to share their experience from working at MicroDoc. Three employees share their experience from internships at MicroDoc Rahel Kleineichholzer, 21 years old, studies Computer Science. What is the most important aspect for you to choose MicroDoc as employer? When I was looking for an internship, I mainly focused on diversity in things they do. I wanted to have the possibility to try out many things and have the choice to switch competence-field if I wanted to. In the beginning, I worked with web development, now I focus on hardware. I think it’s outstanding to find this kind of freedom in an internship. MicroDoc has shown a flexible mindset, plenty of possibilities and flat hierarchies. I really feel like every employee is on the same level. This creates a relaxed atmosphere and... --- ### Graal VM™ - Even small devices deserve a great interface - **Date**: 2021-06-14 - **Category**: products, energy, stories - **URL**: /even-small-devices-deserve-a-great-interface/ For devices that are not powerful enough to run a full feature browser or Android system, MicroDoc is developing a user interface framework directly integrated with the Graal virtual machine. Why? Because the number of small devices is increasing dramatically, and although they may be small and low powered they still deserve an up-to-date user interface. The Internet of Things is extending day by day. More and more of the stuff we use in our everyday lives connects to the internet. We will want to interact with a great many of these devices, and we do that through a user interface. However, development in user interface design has for a long time been favoring powerful machines. Just compare your mobile phone to the one you had 5 years ago. It would be impossible to run your current interface on your older phone. Lightweight UIs needed UI technology needs to lose weight, says Bruno Caballero, head of Virtual Machine Technologies at MicroDoc: The main effort within software development regarding UIs has been focusing on two things: Browsers and mobile applications based on Android or IOS. Think about what has happened in the computer world. We started with personal computers, and we communicated with them using a mouse and a keyboard. In the early years of Java the main focus was to design nice UIs for them. Then smartphones began to rule the world, and now everybody uses a web interface for everything. But according to Bruno Caballero, with the advent of IoT and the age of small,... --- ### Java™ Virtual Machine Tool Interface - **Date**: 2021-05-20 - **Category**: products - **URL**: /java-virtual-machine-tool-interface/ Learn how to monitor and control Java applications using the JVM Tool Interface (JVM TI) for debugging, profiling, and runtime analysis. The Java Virtual Machine Tool Interface (JVM TI) is a low-level programming interface which allows the user to create agents, which can monitor and even control Java applications. It is an optional interface, and a Java Virtual Machine (JVM) implementation is not required to provide an implementation for it. The HotSpot JVM, implemented by the OpenJDK project, has an implementation for this interface. One of the most used JVM TI agents might be jdwp, the Java Debug Wire Protocol agent, with which one can debug Java applications. Apart from debuggers, profilers and monitoring tools are two other types of agents for which this interface is designed for. A JVM TI agent is a native library, mostly implemented in C or C++, which is linked with the JVM during runtime. The agent therefore runs in the same process as the JVM and the Java application it is attached to. The JVM can notify the agent about certain occurrences through events. While reacting to those events, the agent can request certain information from the JVM through the JVM TI or the Java Native Interface (JNI). Since agents are written in C or C++, they can utilize operating system APIs as needed and... --- ### The “One VM” Concept - towards the holy grail - **Date**: 2021-02-12 - **Category**: automotive, energy, products, automation - **URL**: /the-one-vm-concept-towards-the-holy-grail/ Would it be fair to say that the GraalVM is a step closer to the holy grail of polyglot programming? Yes, according to the virtual machine experts from MicroDoc. Here’s an overview of what the GraalVM can do for software developers. It was designed to be the programming interface of the future for the Oracle database, and therefore much effort and vast resources have been put into the development of the Graal virtual machine. According to MicroDoc’s managing director Dr. Christian Kuka, this ensures an array of interesting features that will make life easier for developers and project managers. On top of that, you can consider GraalVM to be future proof. As part of the Oracle database product, it has a life cycle of 10+ years. Speaking all languages The polyglot features of the GraalVM give you a whole range of advantages. It can execute software written in different languages in the same controlled environment. It allows you to run Java code and everything that is based on Java bytecode, including Kotlin, Scala etc. It also provides a runtime for Python, Ruby, and JavaScript and has the ability to host C, C++ and even Rust code. This allows for easy integration of machine learning, neural networks and deep learning applications into your usual business applications. Most of the A.I. algorithms are written in Python, but currently, if you want to integrate them into some kind of mainstream software-product, you have to... --- ### New virtual machine for the cars of tomorrow - **Date**: 2021-02-11 - **Category**: automotive, products, stories - **URL**: /new-virtual-machine-for-the-cars-of-tomorrow/ Cars are quickly converting into cyber centers on wheels, and buyers expect new features to be introduced just as fast as in their smartphones and consumer electronics. That puts tremendous pressure on car manufacturers. To relieve some of the pressure, MicroDoc is now introducing GraalVM embedded a virtual machine allowing for faster development cycles while retaining the stability and longevity required by the auto industry. A significant amount of telematics services, connectivity services, and infotainment systems in the automotive industry are programmed in Java. But although Java’s popularity is well deserved, it does come with some drawbacks, notably slower startup performance and a larger memory footprint. GraalVM remedies these shortcomings. It can accelerate startup time by up to a factor of ten, reduce resource consumption, and support multiple programming languages while running different software on the same infrastructure. Solving a challenge “Initially developed by Oracle to be the programming interface of the future for the Oracle database, GraalVM is now being introduced to the embedded world. Especially in the automotive industry GraalVM will make a huge difference.” - Dr. Christian Kuka, CEO at MicroDoc It’s well known that the largest cost of development for a new model goes into software. Essentially, a modern car is a big rolling smartphone and that is a huge challenge to the auto industry. Why? Because, on one hand you have your costumers. They expect to be offered new features as fast as they’re used to from smartphones and other consumer electronics. On the other hand, car manufacturers have strict safety and warranty obligations. That means the software must be... --- ### Graal VM™ – the Swiss Army knife of virtual machines - **Date**: 2021-02-10 - **Category**: automotive, products, stories - **URL**: /graalvm-the-swiss-army-knife-of-virtual-machines/ MicroDoc introduces GraalVM to embedded systems. It accelerates startup 10x, supports multiple languages, and reduces memory footprint dramatically. According to MicroDoc, the GraalVM virtual machine will cure many of the well-known headaches caused by traditional Java virtual machines. And that’s not a small thing, because Java is the world’s most widely used programming language. In the automotive industry for instance, many of the telematics services, connectivity services, and infotainment systems are programmed in Java. In healthcare, high-end medical machines, like those for analysis, have interfaces written in Java. And while there are numerous good reasons for Java being so popular, it carries some significant problems as well, startup performance being one of them and the memory footprint being another. Perfect fit GraalVM is addressing these problems, according to Dr. Christian Kuka, CEO of MicroDoc: The history of Java is a real success story. It’s a rather old language, initially invented by Sun Microsystems for embedded use. Over time it became the mainstream programming language for commercial applications, and it continues to be the most common language for serious programming. MicroDoc alone has sold 40 million Java licenses to the automotive industry. Some years ago, Oracle acquired Sun, and Java became an Oracle product. Oracle launched a number of internal projects to advance the technology. GraalVM was one of... --- ### MicroDoc is re-elected to the Java Executive Committee - **Date**: 2020-12-02 - **Category**: press, products - **URL**: /microdoc-is-re-elected-to-the-java-executive-committee/ MicroDoc have been re-elected to sit on the Executive Committee for the Java Community Process. Together with 18 other companies like Oracle, Alibaba, IBM, Intel, SAP and Twitter, MicroDoc will have key role in shaping one of the most used software languages in the world. Being part of an exclusive committee alongside the world’s largest tech companies, shaping the software language the entire world uses, is a testament to how far we and MicroDoc have come. And this accomplishment is purely based on dedicated specialists being the best in the business. I am very proud of the standing MicroDoc has built in the software community. The JCP Executive Committee (EC) is the group of members guiding the evolution of Java technology in the Java Community Process (JCP). The EC represents both major stakeholders and a representative cross-section of the Java Community. It is composed of 16 JCP members plus a non-voting chair. The chair of the EC is a member of the Process Management Office (PMO). The 16 voting members are selected from JCP members. The EC is responsible for approving the passage of specifications through key points of the JCP and for reconciling discrepancies between specifications and their associated test suites. Being a small operation in the company of giants is a privilege we highly appreciate. And it is also a privilege to participate in the continuous development of Java. Our seat in the Executive Committee allows us to provide our expertise in future... --- ### No Internet of Things without strong cyber security - **Date**: 2020-08-12 - **Category**: automotive, energy, stories, services - **URL**: /no-internet-of-things-without-strong-cyber-security/ The concept of IoT holds great potential: By connecting millions of devices to the internet we can save time and money and become more efficient, we can offer our customers more convenience, better service and much more. But there is no grand vision without a snake pit of problems. With the Internet of Things comes the Internet of Threats. We need to protect our new network-aware systems and devices. There will be no Internet of Things without a strong focus on cyber security. Some security experts compare the current state of IoT security with Asbestos. They predict that in a few years time, we will look back asking ourselves “What were we thinking?” Others draw parallels to the World Wide Web of 1994-95, arguing that IoT will be a security train wreck for years, before we eventually figure it out. Messages like these may paint too gloomy a picture of the challenges within IoT but nevertheless, cyber security is crucial not least because of the close interaction with the physical world. IoT threats can go far beyond the well-known, conventional Internet threats like credit card theft. They could disable home security systems, manipulate navigation systems on connected vehicles, disrupt smart medical devices, or knock out entire energy systems. IoT is speeding up At MicroDoc we have a broad range of experience and a long track record in IoT security. We continue to experience significant demand for customer inquiries and projects in the IoT cyber security domain. It’s no wonder because IoT is coming at us at a rapid speed. We are connecting more and more devices and systems to the Internet, whether they are industrial control systems, cars, cameras, door locks, fitness trackers,... --- ### The 2020s: the decade of software-defined mobility - **Date**: 2020-05-11 - **Category**: automotive, stories - **URL**: /the-2020s-the-decade-of-software-defined-mobility/ Electrification, autonomous driving and all-embracing vehicle connectivity is fundamentally changing the way we move goods and people around. The digitalization of mobility has the potential to help us handle the huge challenges the world is facing regarding urbanization, sustainability, and climate change. No doubt, the 2020s will be the decade of software-defined mobility. To emphasis the challenges ahead, some call it “The Mother of All Tech Battles.” In our effort to digitalize, connect and automate every aspect of mobility, we need to handle steeply increasing system complexity, cyber threats, new business models, and lawmaking issues, just to name a few of the many obstacles ahead. As experts in embedded and IoT solutions, and a trusted and experienced technology partner to the transport and automotive industry, at MicroDoc we face these challenges on a daily basis. And based on that expertise we feel we have a fairly clear view of the things to come in the 2020s, a decade that doubtlessly will bring enormous changes in the mobility sector. A computer on wheels The vehicle industry has come a long way since the introduction of the Cruise Control, the first vehicle feature that integrated mechanical and electrical systems. That was in the 1950s.Now, cars are computers-on-wheels running millions of lines of code. The average new car relies on 70 to 100 electronic control units and hundreds of sensors to monitor itself and its surroundings. Partly, this revolution has been triggered by other technology areas, for instance telecom. There has been exponential growth in memory... --- ### OSPlus Neo – The Modern Platform for Banking Software Development - **Date**: 2018-07-17 - **Category**: finance - **URL**: /osplus-neo/ OSPlus Neo demonstrates our core strength—delivering stable, high-performance software platforms using Java and web technologies, purpose-built for the demanding environments of the financial sector. At the heart of OSPlus Neo lies what sets us apart: deep expertise in Java and modern web technologies combined with a proven track record in building large-scale, mission-critical systems. Developed with the specific needs of the financial sector in mind, OSPlus Neo is a modular and high-performance framework designed to handle millions of users, high data throughput, and strict compliance requirements—without compromising on usability or innovation. Our team played a leading role in the development of OSPlus Neo. From architecture to implementation, we engineered the platform to be robust, scalable, and maintainable—ideal for high-traffic environments such as banking and finance. Java-based backend: Reliable and secure processing of core business logic Modern JavaScript frontend: Responsive, accessible, and aligned with UI/UX standards Optimized for high concurrency: Designed to perform under heavy load Strict quality and testing standards: Ensuring long-term stability and resilience With years of experience in enterprise software development, our engineers understand what it takes to deliver platforms that scale—both in terms of technical architecture and organizational impact. OSPlus Neo reflects this: it’s not just a framework, it’s a battle-tested foundation for modern banking solutions. OSPlus Neo is already in productive use within the Sparkassen Financial Group, forming the foundation... --- ### Java One Submission Accepted: Surviving Immature Technology in IoT [CON3761] - **Date**: 2017-07-20 - **Category**: press, products, energy - **URL**: /java-one-sumission-accepted-surviving-immature-technology-in-iot-con3761/ MicroDoc’s submission for the Java One presentation titled “Surviving Immature Technology in IoT” was accepted by the program committee. Please read the abstract and stay tuned for updates about time and location. “We want to control room light, temperature and playlists with speech-recognition and gestures, nearly every device in our households should play an active role in our private IoT universe. The product manufacturers however provide non uniform platforms, “creative” protocols, hardware related restrictions, and undocumented behavior when we try to communicate and integrate with these devices. Within the last two years we developed a Java and OSGi based energy management systems that integrates solar panels, batteries, and a variety of household appliances. This presentation describes the development process, and the Java based development platform that helped us to overcome the problems with behavioral diversity while controlling IoT devices. “ MicroDoc’s senior specialist Thimo Koenig will be in San Francisco for the presentation. --- ### MicroDoc signs strategic frame agreement with EnBW - **Date**: 2017-07-17 - **Category**: energy, stories - **URL**: /microdoc-signs-strategic-frame-agreement-with-enbw/ MicroDoc signs strategic partnership with EnBW for software development in smart home energy management and e-mobility solutions. MicroDoc is a software licensor for Java technology and has been an engineering service provider for the highly innovative EnergyBASE project of EnBW since 2015. Our engineers support the development of complex software infrastructure for management of an energy mix comprised of solar power, battery storage, and fixed network power grids. This technology portfolio will be of significant importance in the context of the fast-growing electro mobility market. MicroDoc brings in relevant expertise from the energy sector, from smart home/home automation and especially from the automotive industry. --- ### MicroDoc Sportteam participates in Munich B2Run - **Date**: 2017-07-14 - **Category**: press - **URL**: /microdoc-sportteam-participates-in-munich-b2run/ MicroDoc Sportteam participated successfully in the 2017 Munich B2Run. The team was formed by staff from the Stuttgart and Munich office. The MicroDoc Sportteam participated successfully in the 2017 Munich B2Run corporate running event. The team brought together colleagues from both our Stuttgart and Munich offices, demonstrating the collaborative spirit that defines our company culture. B2Run is one of Germany’s largest corporate running series, bringing together teams from companies across the country. For MicroDoc, participating in events like these reinforces our commitment to team building and employee well-being alongside our technical excellence. --- ### MicroDoc team visits “Transport & Logistik” fair in Munich - **Date**: 2017-05-09 - **Category**: automotive, press - **URL**: /microdoc-team-visits-transport-logistik-fair-in-munich/ Part of MicroDoc’s telematics frontend development team went to the Transport & Logistik tradeshow in Munich to visit with our customers. The show was a big success. Telematics has finally become a booming business. Android and Java based solutions are all over the place. Please contact us to learn about our telematics competencies: microdoc@microdoc.com --- ### MicroDoc renews sponsorship agreement with U19 Bike Team - **Date**: 2017-05-01 - **Category**: press - **URL**: /microdoc-renews-sponsorship-agreement-with-u19-bike-team/ MicroDoc renewed the sponsorship agreement with the U19 bike squad of Team Auto Eder, managed by Ralph Denk of the professional World Tour Team Bora-hansgrohe. MicroDoc has renewed the sponsorship agreement with the U19 bike squad of “Team Auto Eder”. The team is managed by Ralph Denk, who also runs the professional World Tour Team “Bora-hansgrohe” with world champion Peter Sagan. “IT projects and bike races have some similarities. Both require professional organization, a great staff of team players, endurance and the will to win. So, we take pride to continue to support the U19 team,” says Hans Kamutzki, Managing Director of MicroDoc. --- ## Technology Expertise - **Languages**: Java, Rust, Python, C/C++, JavaScript - **Platforms**: GraalVM, Spring Boot, Kubernetes, Docker - **Protocols**: MQTT, Modbus, REST, Protocol Buffers - **Cloud**: AWS, Azure, Google Cloud - **Embedded**: ARM, Linux, RTOS - **Tools**: Maven, Gradle, Jenkins, GitLab CI ## Contact Information - **Address**: Elektrastraße 6a, 81925 Munich, Germany - **Phone**: +49-89-551969-0 - **Email**: microdoc@microdoc.com - **Website**: https://www.microdoc.com ## Legal - Impressum: /legal/ - Privacy Policy: /privacy/ - ESG Information: /esg/