In part 1 of this blog post series, I talked about one of the most critical “technologies” that people leverage to create microservices, and that is containers. In this post we will discover, the most used product to create and run containers and that is Docker.
As the cloud visionary, your job is to keep your band of pioneers dogmatically cloud native. You will be able to back off the dogma after a while, but one of the best ways to get out of an old groove and in to a new one is to use a well-defined methodology.
With GitHub and Azure DevOps you have a powerful combination of tools to help you develop world class applications where you are an open source or enterprise developer.
Working effectively as remote teams has never been more critical. Remote work brings significant challenges to development teams, especially as more and more organizations place a premium on working remotely.
There are situations where people would like to have a comprehensive view of the feature comparison. Instead of digging into every feature across all three platform, I compiled a list of name spaces in each platform and put them side by side so you can easily see the differences.
The tech industry has made great progress over the last few years building low code environments such as Power Platform. Overall, the robust features can bring great value to business quickly with world class integrations, wide array of user interface templates and outstanding mobile functionality.
One of the challenges of implementing gRPC services is distributing the required ProtoBuf contracts and updates to clients. Delivering the contracts using a URL can make the services easier to use and discover. Learn how you can use ASP.NET Core static files middleware to distribute your proto files.
This post will give an example of creating a callout in SharePoint. The gd-sprest library was recently updated to include the SharePoint Callout Manager helper class, which we will be using for this example.