As we covered in part 1 of this blog series, Snowflake’s platform is architecturally different from almost every traditional database system and cloud data warehouse. Snowflake has completely separate compute and storage, and both tiers of the platform are near instantly elastic. The need to do advanced resource planning, agonize over workload schedules, and prevent new workloads on the system due to the fear of disk and CPU limitations just go away with Snowflake.

Today SEO is much more than just finding high converting keywords for better ranking. Most marketers and content writers nowadays rely on different strategies to stay in the game. Imagine handling such intricate tasks manually or shuffling through several tools daily to get this done. Sounds hectic, right? But what if we told you, there’s a single package out there to make your work easier.

This post is about Kafka and the process I have been through recently writing a performance test for an application that subscribes to messages from this technology. The test I ended up with was in the end very straightforward but there were several hurdles that took a while to resolve. I hope that reading this post will hopefully help you avoid them.