IT Governance

The Three Hottest Technology Buzzwords of 2017 Explained

We get new words every day to help identify emerging trends and services that are continually popping up. The fact that “google,” a made-up name for a search engine, is now a grammatically correct verb just goes to show how powerful language can be. And with some new terms popping up in IT, it’s important to figure out what the cool cats are spitting to keep from being whack. In a post at his website, Joe the IT Guy helps decipher three pressing buzzwords:

  • Continuous integration/continuous delivery (CI/CD)
  • Microservices
  • Serverless

What’s Buzzing in IT

Joe explains CI/CD like this:

Continuous integration is what happens with DevOps after a developer checks-in/commits code to a version control system such as the ubiquitous GitHub. This check-in/commit is detected by the CI/CD system and the code is automagically compiled, built, and tested – that is, integrated. Then another check-in/commit, another automagical build – that is, continuously.

Continuous delivery is the whole pipeline from code check-in to production deployment. After continuous integration, there are the staging and production deploys. The goal of continuous delivery is to do the opposite of traditional change management. Instead of bottling up lots of changes into one big release, continuous delivery prefers one change per release…

Microservices are a littler simpler to explain. Instead of having a bunch of services baked inside one program, each service works separately from one another across servers. That means you can implement changes to a single service or aspect of a service without having to trace it through overarching “monolithic” systems. In other words, fewer changes in general are required. Basically, microservices are easier to play around with and are being used by some industry giants, like Netflix, Soundcloud, and Amazon.

Finally, serverless is expectedly deceptive: It is on a server somewhere, but it’s not for a developer to deal with. That’s for the cloud service provider to take care of. Developers instead upload “functions” into the cloud and tell the cloud how to run it. Serverless saves a lot of time and money that would have been spent on maintaining servers–hence, serverless.

You can view the original post here:

Show More

Leave a Reply