Abstract
Scalability problems generally start appearing once a product has rolled out into full-scale production. The goal of a scalable system is that it must be available for use at all times and remain highly responsive regardless of how many people use the system. Scalability, with respect to software architectures, has also come to mean extensibility and modularity. This simply means that when a software system needs to scale upward in complexity, it does not need to be overhauled with each addition. At this stage in the life cycle, making modifications to the software becomes a logistical nightmare. Any changes to the software will necessarily have to be backward compatible with older versions of the product. Many software packages now include an autoupdater that accommodates post deployment updates; however, the best solution is to address scalability issues at the design phase, rather than ending up with a dozen versions of a product and the server downtime caused by implementing updates.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.