I work with our enterprise architecture. In my network, there are almost 400 total applications. I have been working here for almost six months on a network migration and in those six months, I have been working with many of those applications that have been included with the involvement of Azure in the migration.
We are migrating everything from the old network to a new architecture. There are multiple teams that I work with and people work with me throughout the organization. I review all the target architectures and the deployment and everything that comes along with the pieces of the migration that involve Azure. Any issues, large or small, I have to look into. These issues might be simple certificate issues or they may involve multiple interfaces that need to be used for a solution.
Because we have a very complex system, it is not easy to complete the migration. The landscape also has a mixture of different technologies and platforms. If I have to customize, I just get a Terraform script or ARM template from a developer who is assigned to that task. I review all that stuff that they give to me.
When we went to the version of Azure that we use now, there are certain solutions that we created. If we had trouble, we worked with Microsoft to create that solution for our organization and the problems that needed to be solved.
We define our own solutions with Microsoft that are not available in the open market. Because of the way we have used Azure, we do not really have a very focused end-product. It is a highly customized product that we have built using many tools.
Azure is now a mixture of solutions. There are certain applications, which are IaaS (Infrastructure as a Service) applications, where we just go and use them. Then there are certain applications that are a mixture of IaaS and PaaS (Platform as a Service). For certain parts, we use private clouds, public clouds, or hybrid clouds. We originally wanted to use more public clouds, but as we proceed, we are moving into more hybrid mechanisms. In the future, I don't know exactly what direction we will take because the technologies and the climate are changing so quickly.
But right now, we are only using Azure with images being created from the existing architecture. For Azure, we use private cloud, public cloud, and mixed, or hybrid cloud as needed and all of these work together.
In the future, we may go for some specific function-based services or even open-market APIs. We can use open APIs with Azure. API management is also possible. So there are a lot of permutations and combinations that go with each application based on sizing and NFR (Non-functional Requirements) validation.
For Microsoft Azure, we use the product itself as a platform, I work mostly with their services. These can be PaaS services or DNS services, monitoring services, storage services — basically all the supporting services that are available to us with Azure. Anything that is not available, we try to build on PaaS. If the services we want are not available, I have to do a complete fabrication.
So we use mostly PaaS services for most of the supporting services and then we work further in solution optimization, which is something we can accomplish through Azure. Ultimately all that depends on the budget. If a company is ready to spend on a cloud solution, an ROI (Return on Investment) model helps. The amount of customizations and the real need for a solution comes out of the realities of the ROI.
Our contracts are based on supplying solutions for what the customer needs. If they have selected that a particular application will be available and make this a system mandate which we have to flow, then we have to keep those applications. Azure is one of the tools that we are using to help make these kinds of customizations and to meet their expectations after the migration.