Listen: A new story from The 6 Figure Developer Podcast
"Or you don't have to worry worry about some of the level configuration that you would need to manage an infrastructure environment and to me that's cloud native so picking platforms like instead of again. provisioning a VM. And installing my a sequel server I would rather use a platform based database like azure sequel or Cosmos DB or anything else I can just say if a database this is the size I want want and you manage all the little details you know. Don't you don't need to tell me that you're rolling out new updates every seven days as long as the up time is there. I don't really care so to me. That's what cloud cloud native is really doing target targeting platforms and moving away from infrastructure. A bit and it can be service. I'm a fan of service. Yes I do. Think it's over hyped. Sometimes but I don't think you have to be serviced necessarily be cloud native and then micro services to me are just a way to say A. I need to build a system developed complex and I would like to build up system not by creating one big monolithic team because to me. It's more about teams in the APP. But I'd like to do is have a team of five developers here and a team of five developers over there and have them coordinate what they're building through the usage of API. He is our messages. Or what have you. But they're able to pick their own schedules and their unreleased cadences and their own data persistence and really be isolated. And how the architect and design everything and and not be coupled together to that we have to wait for all these people to come together to produce some new release for QA. Ah You're some new release for the customer customer or production and to me. That's been working out pretty well over the last couple years. I've seen both the good and bad of micro services so the good point is everyone's working independently and they're willing things out whenever they want and then there's the downside which sometimes that type of architecture can be a little bit harder are to see what is happening and what is going on that development time you know like what really happens when I call that service now. I have to go over there and figure out what's happening because something in the system. Some stop producing the right result so little more difficult of development time and also at run time you'll learn pretty quickly things go south for your customers and your customers are seeing the era. There's there's GonNa be a lot of pressure on the teams to come up with an answer right away. So if you don't have your logging events and alert set up properly there's going to be a lot of scrambling in and people trying to diagnose problems by you know running around all over the place trying to put things together but Like with everything in software we try to learn as as we get along and get better so I think the downside to micro services. I think it's easy to scare people about the downsides but I think once you actually actually get into production and see the benefits. You'll you'll realize he can work with those downsides you know you can you can make them work for you so having worked with medicine for or for a number of years and I would imagine transitioning through technologies or at least versions of Microsoft technologies going from I think you mentioned web forms in Dot Net core I presume and into more cloud native architectures has it been tough. Or what are the the ideas to keep even mind when trying to keep an existing system or suite of applications up to speed up to the latest greatest or at at least in some sort of maintainable state. It is definitely a challenge and I again. I think it's an argument for building smaller. Pieces like with micro service beasts approach. Because I do look at one of the Web forms applications which is a complete monolith that was started on twenty years ago and quite. Frankly it'll probably never be rewritten. We have to add features once in a while but We I look at that technology stock and it's based on Espn Dot Net and yes ask the majority of the application in its Web forms but there's ways to wedge other technologies."