Photo by Alexander Andrews on Unsplash Lately, I’ve been thinking that most of the software I’ve done consist of stitching of API’s. Imagine you work on the team that is in charge of handling payments. It doesn’t matter if you’re working on the front-end or the back-end, it usually goes like this: We (the company you work for) have a new payment provider. We must integrate with their API. We must accommodate our business logic to their API....
Resilience means the capacity to recover quickly from difficulties. Circuit breaker pattern is a good practice for resilience. When working with distributed systems, you want resilience. If you’re working with “micro-services,” you probably have faced with the problem of a service going down. When X service goes down, and Y and Z depend on X, every internal exception could potentially start taking other services down. If you don’t work with micro-services, you might still have an integration with a payment provider (PayPal, Stripe, Google Play, etc....
In this blog post, I will try to demonstrate how to setup a working environment with StackExchange.Redis package is communicating to a Redis box using SSL through STunel. By the end of this post, you will have a working environment on Vagrant like this: ...
Last night I was reading this post: ES6 arrow functions, syntax and lexical scoping and going through the comments I saw this question: so arrow functions always inherit scope? The answer was by Barney: always. I went to the console and typed: nvm use 4 node var doSome = () => { console.log(this.x) } doSome.call({x: 'hello'}); global.x = 'hello'; doSome.call({x: 'good bye'}); Could you guess what is going to be printed?...