I'm not sure I understood your comment... is intellectual property evil? Are the free software guys on the wrong track? The way I read it there is a bit of self-conflicting points in the comment. Can you elaborate a bit for this poor soul?
Well, if you had a closed-source product, let's say a distributed KV-store just to say something ... well, I gotta say Redis in the KV-store example I guess... would you stick with Redis because it's -nowadays "somewhat"- open source even if you could get a several "X" advantage in performance and flexibility for the same buck?
I mean, I understand "why" the rise of "BSL" and similar licenses... some players have been a little bit nasty xD, and that's driving a bunch of younger companies that I have been talking to away from open-source as a mean to protect their products... And I'm curious about the community's perception of running "generous" (as in generally free for small business or tryouts) but not actual "open-source" solutions as part of their stack (as in ASL2, BSD or similar hyper permissive licenses).
That's gold, thanks! So, what I understood from the MemoryDB story is... value-for-money ... and try to avoid lock-in. But -from the Doppler bit-, a "soft" lock-in is acceptable if the price is right.
Thanks @Eridrus! Can you give me some insight into how would you look at it when making a recommendation about it? I don't know you so it's hard to give an example, an old example that comes to mind quickly for me is JBoss vs BEA if you're old enough to remember that xD
Instead of capturing traces all of the time which has a CPU, memory and storage overhead that can be quite brutal, we "backtrace" errors. Think of it as following an exception bubbling-up a program execution stack... but through the network. That is then correlated to the services impacted all the way to your public API's.
We are working on the PoC's for async processes too! (queues, pubsubs, fanouts, streams); and session/user-level impact metrics, coming out real soon! :)
By the way... this will also be used to build better context in our discovery / knowledge application, because.... well... why wait until something goes wrong to understand the impact of what you are doing? :)
Hi taubek! Everything we build is about streamlining the experiences we provide, from monitoring and troubleshooting to discovery (no need to wait for something to go wrong, right? ;)). We found such integrations (including native desktop notifications) to be lacking in terms of context presentation, interactivity and actionability. We know it's not the usual stuff... but that's kind of the point! Let us know your thoughts when you take it for a spin! :)
Production-grade, we are currently supporting AWS EKS and GCP GKE is coming next week! But we will have AKS and others going strong before July ends! :)
Hey there! Anibal here, CTO @ Kerno!
We do support multi-cluster, multi-region and multi-account. We build abstractions of your components and workflows independently of the environment and help you keep things in check across the line :) ... versioning drift tools coming soon! :)
Where is the added value for the end user in your opinion?