This is a guest blog from a member of the MuleSoft community. Brad Cooper is a senior developer with more than 20 years professional experience in a variety of tools and languages, including Anypoint Platform. He holds numerous MuleSoft certifications, – including MuleSoft Certified Developer: Integration Professional – and hopes to add MuleSoft Certified Architect: Solution Design Specialist in the near future.
A lot of people in the industry have been talking about the three “T’s” of sales recently––territory, timing, and talent. It got me thinking about the way that these three “T’s” shape the MuleSoft sales experience, and just how special those concepts are here.
In the past decade, higher education institutions have invested heavily in procuring modern information systems, in order to provide new and innovative digital experiences for their students, faculty, administrators, and other stakeholders.
In a previous life, I worked primarily with the operational side of the IT business, which is concerned with monitoring and operational alerting. The requirements we implemented were variations on a theme that typically started with the business asking IT to provide an SLA for “availability” of a service as well as an SLA for the responsiveness of a service. On the surface, these requirements were clean and simple, but in practical terms, things got murky very quickly.
To survive today, companies need tech-savvy leaders. The convergence of cloud, SaaS, mobile, big data and more is turning every company into a technology company. As a result, CIOs need to step up and partner closely with business leaders to drive strategic initiatives and growth opportunities. In some cases, CIOs are even stepping up into the CEO role itself.
Traditional security models—such as firewalls and DMZs—were designed to protect the perimeter. The thinking was that if the four walls of a company were protected, then threats would be neutralised before they come anywhere near core IT infrastructure. However, when bad actors inevitably made their way inside, they were often left undetected and free to move about as they extracted sensitive business data.
With the decentralization of IT and the adoption of APIs and microservices, enterprises are struggling to keep up with an accurate view of deployed APIs and their dependencies. This lack of visibility often translates into quality issues––whether it is failed deployments, lengthy processes for identifying and diagnosing of production issues, increased technical debt, or less reuse of available assets.
A daily problem CIOs face is how to deal with legacy systems—systems built decades ago in what now feels like prehistoric times. Buried deep down in the depths of organizations live these scary, monolithic fossils—Mainframe-otops, ERP Rex, COBOL-odons and more—created in a much different world than the one we live in today. The challenge has now hit the radar of CEOs, as company leaders realize that they cannot innovate fast enough thanks to the cost and complexity of legacy systems.
As an intern for the past month at MuleSoft in San Francisco, I’ve had the awesome opportunity to experience the company’s culture firsthand. While collaborating with the Field and Marketing teams on my projects, I find myself constantly learning from the people around me. Everyone here is whip-smart and eager to help out, so when I learned that MuleSoft had been named a best workplace in the Bay Area for the sixth year in a row,
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.