Service-Oriented Architecture & Editorial Manager
Like many world-scale Web presences (Amazon, Google, etc.), the Editorial Manager (EM) system is built around Service-Oriented Architecture (SOA) – why is this so important?
- SOA has emerged as an enterprise-critical concept, specifically to rationalize the robust development, maintenance and evolution of large-scale software systems like EM
- This modern, foundational software framework means that EM is intrinsically flexible, extensible and adaptable, even over long periods of time (decades) and dozens of software updates
- SOA has allowed EM to accommodate publishers’ evolving workflow automation needs for more than 18 years, and promises accommodation into and beyond the foreseeable future
- Use of SOA improves system reliability and availability, as demonstrated by the 99.9%+ up-time provided by EM
- A major benefit of SOA is the ability to scale-out EM implementations, supporting the needs of individual journals as well as publishers with thousands of journals, all within a single software code base
- Use of SOA also facilitates efficient integration and interaction between EM and third party solutions, reflected in the dozens of third party solution implementations available to EM customers
- SOA allows continuous, incremental enhancement of the EM user interface (UI) and user experience (UX), while not subjecting users to wholesale and confusing changes to the UI/UX
- Software development in an SOA environment is intrinsically agile, allowing for frequent, functionally rich software updates that keep pace with a publisher’s emerging business requirements
- Systems built on a SOA framework are “future-proofed”, assuring EM customers that their workflow investments today will continue to deliver ROI and value (for publishers and their constituents) into the indefinite future
- Read more about SOA at https://en.wikipedia.org/wiki/Service-oriented_architecture
To learn more, contact us.