Nats provides a nice CLI that can help with debugging: https://github.com/nats-io/natscli
Besides that I'm also working on a UI solution, that will help to get better overview of your cluster: https://qaze.app/
35 karma · joined April 8, 2013
Besides that I'm also working on a UI solution, that will help to get better overview of your cluster: https://qaze.app/
Jetstream is also much easier to operate than Kafka IMO. Just a simple single binary with an easy to understand config.
This is a joke, right? The management overhead for the JVM in production environments is huge. It's really hard to get it right.
Exactly. You have to compare these kind of frameworks/libraries in "real world" situations and not just build two subpages and create some simple components to form an opinion. Real world single page applications need much more than just the view layer and a router.
No, it's not. You use providers on a component when you want to have a new instance of that Service when a new Component instance of that type gets created. So you have complete control over the DI. More details here: https://angular.io/docs/ts/latest/guide/dependency-injection...
That's wrong. You can split the routing configuration just like in react-router or Aurelia. It also supports lazy loading of child routes and components. So you don't have one giant application to serve at bootup time. It is also documented really well: https://angular.io/docs/ts/latest/guide/ngmodule.html#!#lazy...