The JVM JIT compiler has long been sold as the way Java is able to compete with the performance of compiled languages like C/C++. Every benchmark for Java will tell you to first run your code many times for 'warmup' before you measure its performance, so that its JITed

Our product completely supports Java and we love Java developers. However, internally for our own code, we believe the era of the JVM is coming to an end. We found these 3 things initially attractive about Go: Instant compile times and program startup for faster developmentVirtual threads for dealing with

Lets get one thing out of the way, declaring dependencies like this: implementation 'org.apache.tapestry:commons:5.5.0' is waaaaay better than declaring them like this: <dependency> <groupId>org.apache.tapestry</groupId> <artifactId>commons</artifactId> <version>

Choosing Hibernate when your Java code interacts with SQL databases is widely considered the default choice. We however use the JOOQ code generator instead. Here are some of the reasons why we think it's a better choice. Schema Definition In an ideal case, you write the schema for your database

Today we are open sourcing one of our internal tools kafka-schema-sync. One of the problems we face at Astradot is keeping our staging and prod environments in sync with respect to Kafka topics. Engineers can create tons of Kafka topics, with different configurations for each. We wanted a central place

SetupOur infrastucture is deployed in AWS us-east-1 region. Elastic Load Balancer (ELB) is used for API endpoints. CNAME records were created in CloudFlare DNS to point to ELB instance. TestWe used Datadog Synthetic Monitoring to test our endpoints. Synthetics Monitoring hits an endpoint periodically from around the world. We started