With this guide, you will know how JWTs work in-depth, including having a good understanding of the cryptographic primitives that they are based upon, which are used in many other security use cases. 

No matter how hard we try to design and develop applications, errors will always occur. There are two general categories – syntax or logical errors can be either programmatic errors or consequences of incorrect database design. Otherwise, you might get an error because of the wrong user input. 

There are various techniques that could be implemented to achieve asynchronous interactions among microservices. In this article, I shall talk about a use case where we would be using a message broker – RabbitMQ – and “Fanout” technique to implement the asynchronous messaging pattern in action. 

  There are fixes available for a number of blocking issues and adds support for push and list for compliant V3 servers. We also added support for the command line client to interact with v3 servers as well as project.json managed projects.

Welcome to the November 2018 release of Visual Studio Code. There are a number of significant updates in this version that we hope you will like, some of the key highlights include:

• Multiline search improvements - Easily create multiline search patterns without using regex.
• Custom title bar on Linux - The custom title and menu bar is now the default on Linux.
• References view - Find All References view includes history of recent searches.
• Snippet comment variables - Snippet variables insert correct comment per language.
• JS/TS callback display - Now you can see the context of anonymous callbacks.
• JSDoc Markdown highlighting - Including syntax highlighting for Markdown code blocks in JSDoc.
• Simplified debug configuration - Better defaults and Quick Pick UI for initial launch configuration.
• Run tasks on folder open - Configure tasks to run when you first open a project folder.
• Choose extension version - Install earlier versions of Marketplace extensions. 

Over the last few updates to Visual Studio 2017, we’ve been hard at work adding new features to boost your productivity while you’re writing code. Many of these are the result of your direct feedback coming from the UserVoice requests, Developer Community tickets, and direct feedback we’ve encountered while talking to developers like you. 

Today, we are releasing React 17! We’ve written at length about the role of the React 17 release and the changes it contains in the React 17 RC blog post. This post is a brief summary of it, so if you’ve already read the RC post, you can skip this one. 

"So you shouldn't feel pressured to move off .NET Framework, but just know that it's going to be much more highly targeted compatible fixes kind of going forward and we recommend that all new development that you start on .NET is on .NET Core if possible," 

It has only been about a year since .NET Core 1.0 RC came out. We are now getting close to .NET Core 2.0. We have been playing with .NET Core since the betas and feel like the quality of the 1.0 runtime was very good. Our only complaint has really been odd Visual Studio behavior. We would expect that with 2.0, the adoption of .NET Core is likely to skyrocket. 

Here are their suggestions for keeping development moving forward quickly