Backend testing

>For example, consider an IoT application that ingests many events into a message-bus like Kafka/RabbitMQ, which then flow into some data-warehouse and are eventually queried by some analytics UI. Should we really spend 50% of our testing budget on writing unit tests for an application that is integration-centric and has almost no logic?

There's almost no unit testing here. Write a tiny bit of integration and e2e if its critical, if not forget it.. This still follows the pyramid. Its relative to amount of unit test (domain model/business logic) code required. You want ~100% of the behavior of business logic (unit) according to the pyramid. In this case 100% of zero is zero.

[ref](https://www.youtube.com/watch?v=EZ05e7EMOLM)