Remove Code Remove Engineering Remove Java
article thumbnail

SRE Best Practices for Java Applications

DZone

Site reliability engineering (SRE) plays a vital role in ensuring Java applications' high availability, performance, and scalability. This discipline merges software engineering and operations, aiming to create a robust infrastructure that supports seamless user experiences.

article thumbnail

SKP's Java/Java EE Gotchas: Clash of the Titans, C++ vs. Java!

DZone

As a Software Engineer, the mind is trained to seek optimizations in every aspect of development and ooze out every bit of available CPU Resource to deliver a performing application. Considering all aspects and needs of current enterprise development, it is C++ and Java which outscore the other in terms of speed. Ahem, Slow!

Java 214
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Unlock end-to-end observability insights with Dynatrace PurePath 4 seamless integration of OpenTracing for Java

Dynatrace

Cloud-native technologies and microservice architectures have shifted technical complexity from the source code of services to the interconnections between services. Deep-code execution details. You get code-level insights into application code without code changes. Dynatrace news. The app is powered by Kubernetes.

Java 264
article thumbnail

Optimizing Java XPath CPU and memory overhead by 98%

Dynatrace

This first step clearly shows that the code that powers getFamilyCondition is using a lot of CPU – much more than any other of the top services combined! It can be your own code, 3 rd party code or your runtime that executes for certain tasks such as Garbage Collection. So – we found the culprit!

Java 246
article thumbnail

Progressive delivery at cloud scale: Optimizing CPU intensive code with Dynatrace

Dynatrace

Our Cluster Performance Engineering Team in collaboration with our Autonomous Cloud Enablement (ACE) and development teams quickly identified the root cause and fixed the problem in no time! And the code-level root cause information is what makes troubleshooting easy for developers. Step 3: Identifying root-cause in code.

Code 246
article thumbnail

Big / Bug Data: Analyzing the Apache Flink Source Code

DZone

Naturally, such applications must be highly reliable so that no error in the code can interfere with data processing. To achieve high reliability, one needs to keep a wary eye on the code quality of projects developed for this area. This engine is written in Java and Scala.

Code 159
article thumbnail

Handling Flaky Unit Tests in Java

Uber Engineering

It warns software engineers of bugs in newly-implemented code and regressions in existing code, before it is merged. It also … The post Handling Flaky Unit Tests in Java appeared first on Uber Engineering Blog. Unit testing forms the bedrock of any Continuous Integration (CI) system.

Java 134