dmitribodiu

using System;
using System.Configuration;
using System.Data;
using System.Data.SqlClient;
using System.Diagnostics;
using System.Threading.Tasks;
using System.Threading.Tasks.Dataflow;

namespace ServiceBrokerQueueProcessorTPL
{

dmitribodiu

FROM node:13.3.0 AS compile-image

RUN npm install -g yarn

WORKDIR /opt/ng
COPY .npmrc package.json yarn.lock ./
RUN yarn install

ENV PATH="./node_modules/.bin:$PATH" 

dmitribodiu

Keybase proof

I hereby claim:

• I am dmitribodiu on github.
• I am dmitribodiu (https://keybase.io/dmitribodiu) on keybase.
• I have a public key ASBqQuimbJ661Cf7_pH5k9X962hxmNZ7JGuq9WXP_xdtCQo

To claim this, I am signing this object:

dmitribodiu

public class MessageIdentity
{
    public Guid NameSpace;
    private readonly byte[] _namespaceBytes;

    public MessageIdentity(Guid guidNameSpace)
    {
        NameSpace = guidNameSpace;
        _namespaceBytes = guidNameSpace.ToByteArray();
        SwapByteOrder(_namespaceBytes);

dmitribodiu

Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.

Data Structure Basics

###Array ####Definition:

• Stores data elements based on an sequential, most commonly 0 based, index.
• Based on tuples from set theory.

dmitribodiu

auth with microservices

Authorization and Authentication are hard. when you only have to implement them once (as you do within a monolith) instead of over and over again, it makes the developer happy :-), and maybe leads to less implementation failures.

When you have a bunch of microservices, this is something that has to be considered.

Implement it once or in every microservice, or something in between?