tag:blogger.com,1999:blog-5400765672405463592.post4120121295744178967..comments2024-03-28T06:33:03.563+00:00Comments on So, you want to write software?: The Architecture Doesn't WorkChris Turner (he/him)http://www.blogger.com/profile/09141108967081921802noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5400765672405463592.post-92212774082511168522011-02-08T19:55:40.738+00:002011-02-08T19:55:40.738+00:00Thanks for your comment. I do agree with you that ...Thanks for your comment. I do agree with you that this architecture can be applied successfully. I've delivered many webapps using this model. Perhaps broken is a bit too sensationalist ;-)<br /><br />However I would have to say that on pretty much every non-trivial app I've built using this architecture, I've hit some form of performance or scalability issue. To solve them I've always had to drop back to a combination of shared state, caching, concurrent programming and compromises in my domain model. An approach that allows me to deliver performance and scalability using well structured code and without all these difficulties is long overdue.Chris Turner (he/him)https://www.blogger.com/profile/09141108967081921802noreply@blogger.comtag:blogger.com,1999:blog-5400765672405463592.post-91076785274355220662011-02-08T17:51:56.743+00:002011-02-08T17:51:56.743+00:00Hi Chris,
not sure you can call this architecture...Hi Chris,<br /><br />not sure you can call this architecture broken. Its worked for countless webapps over many years.<br /><br />Perhaps what you are trying to say is that there are certain apps where this architecture is not good enough. That I feel may be a minority.<br /><br />Please don't throw the baby out with the bathwater.Anonymousnoreply@blogger.com