If you already have Jenkins as your build server and want to take advantage of services in Azure DevOps without fully switching over, you may find yourself with an existing Jenkins infrastructure, a source control repository, an Azure DevOps subscription, and a lot of questions. Fortunately, there are many extensibility points you can use to tie these solutions together in a way that works best for your business and team’s skillsets.
When renovating your home, you may choose cosmetic or structural changes depending on your needs and priorities. Similarly, those looking to take advantage of the Cloud for their monolithic architecture must decide if they need surface level changes or a deeper overhaul to accomplish their goals. On the one hand, a structural renovation might start with the demolition of your application and operations practices to fully take advantage of DevOps and Microservices. On the other hand, cosmetic changes can take the form of refactoring your operations and applications to utilize Cloud services while maintaining a monolithic architecture.
If you tear down your house, you will have nowhere to live until you rebuild, and you may not have the time or budget to go that route. If you want some of the benefits of the cloud, but time and budget will not allow an immediate overhaul, here are 3 cosmetic upgrades you can make to your server so that you can chip away at renovation while maintaining a livable environment.
There are multiple approaches to getting your application to the Cloud, but many companies are going “all in” to take advantage of a cloud native microservices approach because it makes it easier to deploy, scale, enhance, and maintain applications. In this article, we use an example of the architecture design decisions for our anonymous email tool, DragonMail, to demonstrate some options and capabilities to consider when moving away from a monolithic to a microservice architecture utilizing the dotNet capabilities in AWS.
[fa icon="angle-double-left"] Newer All Posts