How do you stay competitive in the new era of IT? You have to transform. Nearly every enterprise in every industry is exploring digital transformation to drive new pathways to their customers, create new business opportunities, and improve operational efficiency. Modern applications require faster, more flexible infrastructure to meet the needs of today’s customers.
Traditional infrastructure is designed for a world where each application is built like a vast monolith, rolling out a new version once or twice a year in a large change window. Six months of changes would have to be done before you could roll out a new version. This made it possible to plan infrastructure with plenty of time before each upgrade.
Today’s enterprises want to be able to roll out new versions several times a day. A new means of development is needed, where each application is broken down into microservices, small parts of an application that fulfill their roles individually. At the same time, enterprises are introducing container platforms where small microservices are ideally suited to run as containers independently of each other.
In a traditional infrastructure, a company would have a development department for a large application, and once or twice a year, a complete version would be submitted to the operations department. Operations would then make sure that the application ran properly and securely. In order to manage multiple applications, a small number of platforms and databases were standardized. The operations department had significant influence on standards and infrastructure.
With microservices, things work differently. Instead of 2 departments, development and operations, a small team is built up around 1 or 2 microservices. The team is responsible for developing the microservice and for ensuring the code is up to the expected quality. Each team features a combination of development and operations, which is now commonly referred to as DevOps. It’s up to each team to roll out new versions of its microservice in a secure manner, and the team makes its own decisions on rolling back changes, should something go wrong.
So how does this effect the teams and the way they work?
Fredrik Nygren has spent his career designing and implementing solutions that store, protect, optimize and leverage information to drive successful business. As a Solutions Engineering Manager for NetApp in Sweden, Fredrik leads a team of engineers who are passionate about realizing the value in technology and information. Fredrik spends a lot of his free time cooking and trying out new recipes on his wife and children.
Brush up on the latest trends and developments in cloud, on premises, and everywhere in between. This is where it all gets real, with a cherry on top.
Explore a wide range of open forums where you can post questions, share answers and just generally get smart on all the NetApp technologies that matter most to you.