If your project is considering PaaS, then you may be worried about how this change might impact your team—and rightfully so. Switching to PaaS often results in major shifts in roles and responsibilities.
Let’s look at how this change will affect DevOps, software developers, engineering, and business managers.
DevOps: Be More Productive
Perhaps the role most impacted by the switch to PaaS is DevOps. After all, vendor-managed DevOps is the main benefit of PaaS. If your role is DevOps, you can expect much of your daily routine to be made easier by PaaS. The PaaS now operates the infrastructure, which means fewer pages in the middle of the night. You can manage a larger system without a proportional increase in effort, hit more of your metrics without adding more responsibilities, improve confidence in security, and rather focus on other critical business priorities.
Developers: Focus on Code That Makes Your Project Unique
If you are a developer, switching to PaaS means freeing your time to focus on the code that truly matters to your project – the business logic.
Since your PaaS vendor will handle your platform technology, you should find yourself spending less time (if any at all) on boilerplate infrastructure, scaling, deployments, and other issues that are common to all projects. Instead, you should be able to focus more on what makes your team (and product) unique. And because much of the platform complexity is handled for you, you should see a significant reduction in the amount of code you need to write.
Of course, it’s important to remember that you’ll be trading flexibility for simplicity. You’ll have fewer decisions to make as long as your use case matches closely to what the vendor provides. If you have unique use cases, then you may need to spend time integrating them. In rare cases, you may not be able to accomplish your goal with the vendor’s platform. Therefore, be sure to do your due diligence and build a proof of concept before committing to a specific platform.
Engineering Managers: Focus on People and Process
If you’re an engineering manager, you’ll also see changes when your team moves to PaaS. PaaS solutions often make your life as a manager easier by handling rote tasks that use up time, such as analytics, reporting, cost estimating, and cost monitoring.
Additionally, look for vendors that offer observability into the system operations which can help when diagnosing problems. For example, Heroku offers dashboards for its services to monitor CPU, memory usage, and more. Third-party vendors can provide even more insight through add-ons for APM, logging, and more.
As we mentioned earlier, you also need to investigate the platform to determine how well it supports your technical and business needs before making the switch. This will require work to define the key objectives, indicators, and conduct a proof of concept before making a commitment to switch.
Overall, with the right PaaS solution, you can expect to spend less time on administrative tasks and technical meetings, and more time on what you are good at: managing talent and resources, improving processes, and delivering a great experience to your customers. This is why TriFin Labs, an app-dev consulting company, recommends PaaS to over 90% of the companies they speak with.
Business Managers: Improve Business Agility and OpEx
For everyone on your team, the switch to PaaS typically creates a much faster release cycle and quicker time-to-market overall. Because PaaS handles so much complexity and so many technical details, it tends to reduce costs and time spent on administration, maintenance, staffing, and training.
Moving your team to a PaaS solution will mean big changes. However, your team should see a reduction in costs and complexity overall, and an increase in the ability for team members to focus on their unique skills and the value they bring to the product and the business as a whole.
Previously published at https://dzone.com/articles/how-adopting-paas-will-change-your-team