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.
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.
In this post, Premier Consultant Tim Omta explains how to migrate from SQL CE to SQL Azure.
In this multi-part series, App Dev Manager Jon Guerin and Premier Consultant Daniel Taylor (@dbabulldog) lays out some best practices around setting up and using In-Memory OLTP.
Le DevOps Dojo: Ceinture blanche contient huit modules, chacun aligné sur les concepts clés DevOps tels que l’intégration continue, la sécurité continue, la planification continue et autres.
The DevOps Dojo: White Belt contains eight modules, each aligned to key DevOps concepts such as Continuous Integration, Continuous Security, Continuous Planning, and others.
“DevOps Dojo: Cinta Blanca” contiene ocho módulos, cada uno alineado con conceptos clave de DevOps como integración continua, seguridad continua, planeación continua y otros.
Technical Debt can be defined as as “the concept in software development that reflects the implied cost of additional rework caused by choosing an easy (limited) and faster solution now instead of a using a better approach that would take longer”
