It's time to move past the limitations of traditional platforms. Learn the key dimensions to consider when choosing the right software architecture for your business.
Software platforms have come a long way over the years, ping-ponging between converged and distributed systems of processing as technology evolves. It started with mainframes (very converged), then client-server (distributed), then the web server/browser (converged again) and we are now back in a massively distributed era. Information is processed on myriad mobile platforms, voice, AR/VR, and across numerous operating systems and devices. This makes it possible to do a lot of new things for your users, but it also adds tremendous complexity.
It once made sense to try and address your business needs with an all-in-one platform, but these days, do you really need another rigid platform, or everything that comes along with a SOA? That’s the wrong way to think about solving today’s business and technology problems. Many organizations want to move from commercial JavaEE applications servers like IBM WebSphere to open source alternatives like Red Hat. And while this may make sense from a licensing perspective, organizations need to think beyond these technologies to new forms of architecture.
Architectures have developed to the point where you no longer need to consider a closed, restrictive off-the-shelf platform. Platforms like that are liable to become outdated over time and inflexible when it comes to addressing the changing needs of the business. By carefully evaluating on an architecture level instead, you can solve your problems in a more tailored way for your business that enables greater efficiency and long-term success. A MASA is a great example of this kind of architectural design.
At Progress, we believe that instead of picking a monolithic platform, you should be able to pick the right technology for the right business initiatives. There are a number of key dimensions that factor into determining the right architecture for your business. By evaluating along these lines, you’ll be able to ensure that you are choosing solutions that take advantage of today’s technologies and can deliver the success you need for the long term.
Abstraction makes it easier to isolate capabilities and reduce complex dependencies between application code and development teams.
By designing your architecture with microservices, applications are easier to develop, manage and deploy, making teams more efficient.
Teams across your organization have different needs, and an inflexible platform that cannot adapt can’t possibly serve them all well. An architecture that is fit for purpose makes it possible to work together—efficiently.
Scale is more than the idea of scaling up and down based on transaction/user/data volume. Gartner defines Web-scale IT as “a system-oriented architectural pattern that enables the rapid and scalable development and delivery of Web-based IT services leveraging agile, lean and continuous principles.” You need to be able to scale the right organizational and operational processes to move quickly.
These dimensions are deeply embedded into the technology solutions we build at Progress. Our solutions are best-of-breed at every step, and designed to give our customers and partners critical flexibility when designing their architecture. Our industry-leading frontend UI solutions integrate seamlessly with other backends, and similarly our top-ranked serverless backend services works with other frontends. Or customers can simply adopt our whole stack to build their application, including native cross-platform mobile development, data connectivity, cognitive intelligence and more.
It’s time to move past the search for a restrictive platform and consider an architecture-based “conceptual” platform, based on a cognitive-first mindset. You don’t need another “traditional” platform, you need the right technology.
Mark Troester is the Vice President of Strategy at Progress. He guides the strategic go-to-market efforts for the Progress cognitive-first strategy. Mark has extensive experience in bringing application development and big data products to market. Previously, he led product marketing efforts at Sonatype, SAS and Progress DataDirect. Before these positions, Mark worked as a developer and developer manager for start-ups and enterprises alike. You can find him on LinkedIn or @mtroester on Twitter.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.