You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
☂️ How to plug your Umbrel's Nextcloud into the official Nextcloud mobile app? (using Tailescape & some docker commands)
☂ How to plug your Umbrel's Nextcloud into the official Nextcloud mobile app? (using Tailscale & some docker commands)
tags: umbrel, nextcloud, tailscale
Why you could want to do that?
You could want to use the Nextcloud app to make saving your phone data easier or to get documents from your cloud easily (without a Tor browser, connect via onion etc.).
💭 How I became a FullStack Java developer with Vaadin?
💭 How I became a FullStack Java developer with Vaadin?
tags: blog, java, vaadin
What is Vaadin?
Vaadin is an open-source framework for building modern web applications. It allows developers to create rich, interactive user interfaces using Java, without the need to learn JavaScript or any other client-side programming language.
Vaadin was first released in 2002 and has since become a popular choice for building enterprise-level applications. It is used by companies such as Nokia, Goldman Sachs, and the United States Air Force, among others.
🚌 Make your Kafka bus more robust with Apache Avro & Confluent Schema Registry
🚌 Make your Kafka bus more robust with Apache Avro & Confluent Schema Registry
tags: kafka, avro, blog
In this article, you will learn how to use Apache Avro and Confluent Schema Registry to make your Kafka bus more robust.
Introduction
Apache Kafka is a distributed streaming platform. It is used to publish and subscribe to streams of records, similar to a message queue or enterprise messaging system. Kafka is often used as a data bus to connect different systems and applications. It is a very powerful tool, but it is not without its challenges. One of the most common challenges is the lack of data validation.
Why You Should Avoid Using @transactional in Integration Tests
When working with integration tests in a Spring-based application, it can be tempting to annotate your tests with @Transactional for the sake of convenience. After all, the idea of automatically rolling back changes after each test sounds practical. However, this approach can lead to misleading test results and ultimately harm the reliability of your integration tests. In this article, we'll explore three key reasons why you should avoid annotating integration tests with @Transactional.
1. Integration Testing Means Real-World Scenarios
Integration tests are designed to validate that different parts of your application work correctly when combined. This means simulating an environment that is as close as possible to the real conditions under which your application runs. In production, your application typically doesn't run inside a global transaction that rolls back at the end of each execution. Annotating your integration tests with @Transactional imposes an unrealistic execution context.