Home→Search ResultsOrchestration Big Ideas Kubernetes, OpenShift, and Cloud FoundryThis video discusses platform orchestration from a broad scope. Specifically, Principal Consultant Jaime Niswonger takes a technology-agnostic look at the “big ideas” integral to platform orchestration for the enterprise. He introduces three popular orchestration platforms, Kubernetes, OpenShift, and Cloud Foundry, and discusses scaling container deployments in the enterprise. RecordingThis one-hour video was …
Keyhole Consultants worked with a team of client business managers and developers to develop an internal client application that focused on bi-reporting, cost analysis, and price forecasting for connecting wind, solar, and fossil fuel projects to the United States power grid.
The goal of the project was to take data that was strewn around the company and create one system of record that the company could use to forecast if current and future projects were going to be profitable. This custom application synchronized 150 employees across five different departments.
Given the maturity of the .NET Framework and the automated nature of its memory management, many developers are guilty of glossing over (or even outright ignoring) whether their code is optimal in terms of CPU and memory usage. Personally, I have caught myself making sure my code is maintainable, testable, and extendable while forgetting to consider memory management in terms of nonfunctional aspects.
While the .NET runtime does a great job and memory corruption is extremely rare, we should still be concerned with memory management, particularly in large-scale .NET base applications.
This concern isn’t limited to on-premise applications. It’s easy to forget about memory usage with cloud computing. Azure Functions and AWS Lambda have billing structures based upon the average memory size per second of function execution. The direct correlation between memory usage and cost couldn’t be more transparent.
Fortunately, there are many great tools to help profile and analyze your memory footprint. JetBrains has a fantastic tool called dotMemory which makes it easy to profile processes, auto detect issues, perform deep analysis, and determine traffic. dotMemory can be installed as either a stand-alone tool or as a part of the ReSharper package integrated into Visual Studio.
In this post, we’ll show how to use dotMemory to generate a memory profile and analyze a memory leak in a .NET Core application.
Over the last few years, I have worked on several .NET and JavaScript projects. My go-to IDE for Angular, Node, and (in starting to learn) React has been Visual Studio Code, along with Visual Studio Enterprise for C#.
Recently, I started on a new team and project that was in Java. Our initial thought was to switch back over to Spring Tool Suite or IntelliJ. But, there are some really good extensions now for Java in VS Code that made that transition unnecessary. So we decided to take a look at what Visual Studio code could do for us – we were very pleasantly surprised!
In this post, I provide links and information to get you started down the right path for Java in Visual Studio Code.
My favorite new technology as a developer is serverless computing. The convenience and cost make it a very compelling choice for running options in the cloud. Especially for proof of concepts or quick ways to prove out ideas. Using serverless computing to get up and running takes very little effort and the costs of running an application in the cloud are minimal. Serverless really empowers developers to act on ideas as quickly as possible.
In this post, I’m going to briefly touch on what serverless computing is and the pros and cons of using it. Then I will build a Node.js service to do CRUD operations using AWS Lambda, DynamoDB, and the Serverless Framework. You can view the finished product on Github.