The methods that are covered in this video are flattop, concat/merge, switch, switchMap. Main topic of video is more complex structures – higher order observables. Also we’re going to talk about handling of async stuff inside observables with life example of working with real API. Subscribe to our channels! Youtube Facebook Twitter LinkedIn Instagram Google […]
The methods that are covered in this video are map, filter, reduce, take/skip and distinct. Most of them are array-like primitives they will give you the basis of your further work with RxJs and introduce main instruments from this large swiss knife!
Comics. Search of Investments. Marijuana delivery by drones.
Hello, everyone! Last time we have discussed how to use vagrant boxes. Now we are going to make our own vagrant box. This presentation will be useful for big teams starting from 15 developers or just for geeks from dev ops world.
Our today’s heroes are Publisher / Subscriber pattern and the Mediator pattern. Basically, I created this video to explain the difference both to patterns and Observer pattern …
Our today’s topic is a library for working with streams and events. It’s RxJS and it represents the idea of reactive programming. In the simple words, the meaning of this idea semantically is a representation of all operations as the stream, more specifically, as the sequence of events. Programmatically it means for our usage of two patterns: iterator (for establishing of the sequence itself and going through this one) and observer (for changes propagation).
From my experience many times customers asked me to install new environment for myself, help newbies to set the same environment. Another case was to upgrade software packages, e.g. Postgres 5.4 to 5.5. These tasks are not the complexity of ‘rocket science’ but if you are front-end developer it can take much of your time. The best is to give DevOps work to DevOps engineers.
Use when you want to select between different algorithms in the process of task resolving. So basically all that you need to realize this pattern are strategies (each of them in the separated component/class, but with the same interface) and strategy selector (decides what strategy is more effective at the moment and uses it).
The main idea is a creation of simplified interface to application functionality. Basically, when you create components of your application the interfaces of these ones can be really complicated for outside usage. So to resolve this problem and provide easy-to-go solution, you can use Façade.