Increasingly, organizations are being disrupted by the rapid changes in technology and market dynamics brought about by cloud computing, SaaS applications, mobile adoption and big data applications. To keep pace with these changes, organizations need to rapidly connect their systems and open up their platforms to external applications, vendors and community.
Organizations realize that building an API layer that can serve all of their applications is the fastest way to drive adoption of their platform.
In this 4 part blog series, I describe in detail how one might go about modernizing a functional, but legacy Supplier Relationship Management (SRM) application without redeveloping (or even touching) it. Why? The release cycle for the legacy app is too long and it doesn’t scale in a way that will meet the needs of newly required mobile application.
Additionally, an aspect of SOLID software design is the Open/Closed Principle which in our case can be applied as we are extending and providing functionality without actually modifying the core application.
What a world cup! I do feel bad for 50% of the MuleSoft team though (given that we’ve got a big office in Buenos Aires). It’s exciting though, because this was a very exhilarating competition that truly reached a fever pitch here in the US where “football” is traditionally a game with pads, helmets, and ball that doesn’t really roll.
What was really interesting was how this was truly a, “World Cup powered by APIs.”