search

pep1 / kitchenoffice

Gentics Kitchen Office
7 stars 4 forks source link

Why JAVA? #1

Closed florianbeer closed 10 years ago

florianbeer commented 11 years ago

I'd prefer an HTML5/JavaScript (Backbone.js maybe) frontend, talking to a RESTful server app which connects to a NoSQL DB.

npomaroli commented 11 years ago

Since this is going to be an application, and not a framework or library, I think it's a good move to use a robust, full featured UI framework for web clients, that heavily uses AJAX calls and makes the development easy. +1 for giving Vaadin a go!

florianbeer commented 11 years ago

But having a fixed UI framework won't allow us to easily develop clients for other devices than desktop browsers. A RESTful backend would provide us with the necessary flexibility to build e.g. mobile web, Android (JAVA) and iOS clients easily.

npomaroli commented 11 years ago

Vaadin supports mobile browsers. See https://vaadin.com/features.

npomaroli commented 11 years ago

Maybe it would be a good architecture to abstract the business logic and data model in a way that it can be exposed as RESTful service and write the (default) UI in Vaadin, using this business logic (in Java). Then we can have both: The web UI in Vaadin, without the need to mess around with JS AND the possibility to implement additional clients that communicate with the RESTful service.

florianbeer commented 11 years ago

That sounds good! Pro MVC abstraction ;)