From 25ea263da8df71068a1bc103f77fda44fc2b4015 Mon Sep 17 00:00:00 2001 From: Daimakaimura <17453177+Daimakaimura@users.noreply.github.com> Date: Wed, 1 Nov 2023 07:49:17 +0000 Subject: [PATCH] Update rlog/2023-09-26-wakurtosis-retro.mdx Co-authored-by: kaiserd <1684595+kaiserd@users.noreply.github.com> --- rlog/2023-09-26-wakurtosis-retro.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rlog/2023-09-26-wakurtosis-retro.mdx b/rlog/2023-09-26-wakurtosis-retro.mdx index 3165f15a..ae0cfe9e 100644 --- a/rlog/2023-09-26-wakurtosis-retro.mdx +++ b/rlog/2023-09-26-wakurtosis-retro.mdx @@ -14,7 +14,8 @@ toc_max_heading_level: 5 -The Wakurtosis framework aimed to simulate and test the behaviour of the Waku protocol at large scales but faced a plethora of challenges that ultimately led us to pivot to a hybrid approach that relies on Shadow and Kubernetes for greater reliability, flexibility, and scaling. +The Wakurtosis framework aimed to simulate and test the behaviour of the Waku protocol at large scales +but faced a plethora of challenges that ultimately led us to pivot to a hybrid approach that relies on Shadow and Kubernetes for greater reliability, flexibility, and scaling. Here we will discuss some of the most important issues we faced and their potential solutions in a new hybrid framework. ### Introduction