java - Which is scalable? Simple CRUD Webapp vs Webapp talking to a REST service -
java - Which is scalable? Simple CRUD Webapp vs Webapp talking to a REST service -
i think title says clearly. no scalability guru. on verge of creating web application needs scale big info sets , perchance many (wont exaggerate here, lets thousands of) concurrent users.
mongodb
info repository , torn between writing simple play!
webapp talking mongodb
versus play!
app talking rest service app (in scala) heavy lifting of business logic , persistence.
part of me thinks having business logic wrapped service future proof , allows deploying webapp in multiple nodes (scaling). come java ee stack , play! rebel in java web frameworks. approach assures me can move away play! if needed.
part of me thinks play! app + scala service app additional complexity , mayn't fruitful in long run.
any suggestions appreciated.
note: newbie scala, mongodb , play!. pardon me if question silly.
scalability engineering science art. means have lots of parameters , apply experience specific values of these parameters come solution. general advice, without more specific info problem, hard.
having said that, experience, general advice:
keep application clean , simple possible. allows maintain options open. in case, start simple play app. concentrate on clean code can rework have different architectural model (with clean code, that's simpler you'd think :-)) measure, not guess, bottlenecks are. it's simple plenty flood server requests. utilize profiling, memory dumps, whatever, pinpoint bottleneck in scalability.only then, working app in hand (which launch with) , info on scaling bottlenecks are, can create decisions on split off in (horizontally scalable) services.
on outset, services nice , scalable, in mess - services need communicate each other, start introducing messaging, etcetera. maintain simple, measure, optimize.
java scala scalability playframework
Comments
Post a Comment