![]() The virtual servers have to be built and the software has to be installed and configured. With this ability obviously comes complexity. Today, a developer can have everything they need to develop highly complex applications within a highly complex environment, right in their own backpack. The Production Parity Advantage – it allows the developer to produce higher quality code, because they can do the right things, the right way, the first time. Dev-prod parity basically means that the developer can develop on a system virtually identical to the one the app will end up on when deployed live. Not only does this make developers much more autonomous, there is another big advantage to this kind of local development environment: it is called “ development-production parity” – a concept we discuss at length in the newbie friendly “Jump Start PHP Environment” book. More importantly, they can locally build a complete development environment, which mimics a full web server. In other words, today, with the ability to make virtual machines, developers can carry their own development environments with them and are no longer restricted by another party of people, who have to “give” them a proper environment to work on. These were the main drivers for the virtualization of computing power. More importantly, the computing power could be much better utilized, saving resources. This allowed for totally different things to happen on them at the same time. It was often a fight in a lot of cases and for the “network guys”, keeping servers “in shape” was often like fighting fires.īecause of the growing amount of computing power available, more and more people started to realize that this computing power could be split off into separate “machines”. Servers also always had to be “put up” for testing, which often meant developers had to wait until the “network guys” got a server ready for use with, say, the newest version of PHP. Back then, development was slower and more tedious, and also more error prone. And remember, this was only 10 years ago!Īhhh, how simple life was back then, right? Amazon was just starting their Web Services business. In those good old days, things like continuous integration, virtual machines, cloud computing, infrastructure orchestration, data-center automation and even the term “devops” were basically unknown. This scenario was actually the best technology for web application development back then. When changes were committed to the repository, it would deploy to either a staging or a production system automatically. ![]() ![]() Also, in that not-so-distant past, to get teams of developers to work together, there might have been some form of concurrent versioning system and maybe the team even had an auto-deployment set up. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |