When a company makes the move from software as a service (SaaS) to an API-first platform, a change in mindset is required. The successful transitions come from those who shift from features to flexibility. Technology teams should look to remove constraints and broaden the possibilities of their platform by constantly exploring ways to make their platform as flexible as possible.

When there is a system outage or other serious problem, most organizations have a critical incident response team to handle communication with all relevant stakeholders. But what happens when communication among the technology experts is not going well? How do you go about understanding the problem and helping each contributor work effectively with the entire response team?

Adopting microservices can be a great way to split up existing monolithic legacy applications in order to gain some flexibility and accelerate the development of new features. But the learning curve is steep, and you may need to make some sacrifices. Andrew Phillips outlines the potential impact this implementation can have on architecture and operations in an enterprise environment.

Managing the configuration of Jenkins—the popular open source, continuous integration and continuous delivery application—is not trivial. Even a small change can make the platform less stable or result in problems. Vishal Sahasrabuddhe talks about his experiences using Jenkins and offers tips to take advantage of its many powerful features to automate deployment and increase productivity and product quality.