Gremlin Free – Run chaos experiments to prevent outages
gremlin.com
gremlin.com
I can definitely relate with GP, though. It feels frustrating to learn about an interesting product only to find that it's priced way outside of your budget.
At least Gremlin has a public sticker price. Sometimes enterprise services just skip that completely and require you to setup a call with someone in their sales department, which usually means the service is outside of your budget.
I wonder if this is true though.
Maybe it puts off people who otherwise might be able to have a product tailored to their budget???
How does the Gremlin platform interact with one of my hosts? Do I need to install an agent or something? Does it need root access to my host, hypervisor, cloud console?
Check out more info at https://www.gremlin.com/docs/infrastructure-layer/installati... .
One game changer for Rust is the treatment of Errors as first class citizens. It's literally built into the native types that Rust wants you to work with. That's huge for our product, given it runs in an inherently error-prone environment.
Take a look at our docs for more: https://www.gremlin.com/docs/application-layer/overview/
Regarding your app running in Fargate, you can do either. Hop over to our #support slack channel and we can help out more!
How does Gremlin handle this?
https://www.gremlin.com/chaos-monkey/chaos-monkey-alternativ...
What happens to the in-flight requests? Don't a few users run into random errors whenever a host is killed unexpectedly?
You could have your loadbalancer retry everything that fails, but then wouldn't every single request in your app have to be idempotent?
It's an entirely different story when you are killing processes constantly.
your service has a few ways to deal with a dependency going down -- maybe it's a retry, maybe it's opening a circuit breaker and returning a default payload instead of calling that service.
It really depends on what specifically the service is and what it's calling (so it's a very case by case issue).
One of the very neat features of istio is that you can do this tuning in real time -- spin up your services, simulate faults, and then test your service while tuning your retry logic to see what the best user experience is.
not perfect, but having a server crash is not much different than having a connection reset by a wifi status change or an upload timing out due the mobile network going away or the user navigating away or closing the browser.
I really don't like the idea of saying that it's simply okay to give random users a bad user experience like that when you are actually killing servers yourself all the time.
It's nice to know that you can kill a process and the only impact is that in-flight requests fail, rather than having a more significant outage if a process crashes and the failover doesn't work, or the process doesn't automatically restart, etc.
If you accept that requests will fail you can build retries into the system. It's a lot harder to make a system more resilient if you avoid testing the failure scenarios.
You can decide what happens when an in-flight request is dropped, whether you hold onto the state somehow and retry or the client could fail gracefully with a relevant error message.
Check out our security page for more: https://gremlin.com/security
1. When you go from one machine running the code to more than one 2. Any system that may experience failures and detection of such failures and recovery is desirable 3. Most distributed systems due to the failure scenarios inherent in such systems.
[0] https://www.cbsnews.com/pictures/worlds-15-ugliest-cars/7/
Read up on your trademark, IP and copyright law. The use of similar marks is not permitted when there is potential for confusion, such as two different software projects, esp with overlapping audiences.
NB: TinkerPop is NOT a "graph database", it is a collection of software libraries for connecting to, using, and managing graph databases and distributed processing platforms. Gremlin is a primary part of that stack -- Gremlin proper is the programming language, and the Gremlin GTM is the runtime.
And for a company name, you decide to use the name of an established programming language and registered mark of a top-level Apache project [2], which has been in use since its inception over a decade ago, and incidentally it's a project and programming language that both your previous employers know well [3].
That's some inspired work, overflowing with creative originality. And to top if off, you have animated graphs floating in the background. Yeah, no possibility for confusion there. There's a name for that you know? Google it and see if you can find the word -- its definition has to do with siphoning goodwill. Who advised you on this and agreed these were wise choices and that this would be a good way to begin?
[1] https://www.underconsideration.com/brandnew/archives/new_log...
When a new third-party project site goes online, SOP is to review the new site/code, understand what it is and how it fits into the overall ecosystem, and then put their project lead in touch with TinkerPop's resident artist and illustrator, Ketrina Yim [2], who is available to create custom artwork/logos and Gremlin character illustrations tailored around the new project's theme.
However, when I dug into this site's docs to see how it was related, I couldn't find a clear connection. And when I checked with our team, they said Apache Legal has been aware of the issue since last year.
[1] Branding https://tinkerpop.apache.org/policy.html
[2] Ketrina Yim, Illustrator https://tinkerpop.apache.org/index.html#committers
Only trademarks registered with various legal jurisdictions are enforceable, such as the "Apache TinkerPop Gremlin" name you registered. Unregistered marks used by an Apache project are simply claims on the mark, which in many cases are not enforceable. One example is the Apache Groovy project, where its PMC members erroneously claim the exclusive use of "Groovy" for their programming language, when in fact their only valid claim is to "Apache Groovy" (and its previous monikers "org.codehaus.groovy" and "Codehaus Groovy").