22 ms·
We also use Java/Jetty with raw servlets, a custom DSL, and JDOM for the REST endpoints. As for performance, our customer-facing sites are quite a bit faster t
by davidhansen 15y ago
We also use Java/Jetty with raw servlets, a custom DSL, and JDOM for the REST endpoints.
As for performance, our customer-facing sites are quite a bit faster then a typical DB-coupled site because page objects are fetched from a local memory cache that is invalidated by MQ processing.
Our application is not small, but not large, either. For a large application, Amazon.com is well-known for also using a SOA architecture to deliver customer-facing sites, none of which directly call the DB.
- chrislomax 15y agoThanks for the feedback. I think the first port of call for us, like other have mentioned also, is to look at the RESTful interface. I have been looking and we can quite easily translate a lot of our current code into WCF rest endpoints which leverage caching and you can put sql dependencies on them which means we don't have to re-work a lot. I am going to look at putting 64gb ram into our db server so we can confidently store a lot more of the db in ram cache. We currently cache at web server level which we were moving to network caching anyway so this move is not putting us out, if you will. This appears to give us the chance to move our front end to a different language. This also gives us the chance to play with different language using our real time data Our success in the coming years will be defined by the decisions I make in the next two weeks so I appreciate the comments you have made