StackExchange.Redis – 2.0 release now on nuget (…ish; it is taking a while to validate); THIS IS A BREAKING CHANGE: please see release notes: https://t.co/5HpHmRhFkp
— Marc Gravell (@marcgravell) September 4, 2018
Been waiting for this to be released. Since this is a breaking change, it will be interesting to see what kind of madness occurs when in a diamond dependency where one of your dependencies requires 1.0 and another upgrade to 2.0.
With a microservices arhcitecture system behaviour gets spread out across many, many narrowly focused microservices. Much of the functionality in the system depends on those services collaborating. In this talk I explore different modes of collaboration between microservices, how they compare, which are preferable, and how to keep it all simple. Along the way I will show how to use HTTP for the different types of collaboration and how to use Nancy to implement them on top of ASP.NET Core.
Interesting seeing events exposed simply as an HTTP resource where consumers can query the event stream. The consumer would keep track of which events it has processed. Simple approach if you don’t want to introduce a message broker.
Spend more time programming. One command for an instant, secure URL to your localhost server through any NAT or firewall.
Every once and awhile I need to provide an external service with a URI to my localhost. An example is if you were doing any local development with AWS SNS. I’ve used a few other similar services but ngrok seems to be the one that never fails me.
The Power of the Angular CLI. The Convenience of an App. Spend less time looking up command line arguments, and more time shipping incredible products.
With CLI being all the rage (which I enjoy), I thought this was fairly interesting for those who are not.