3 ms·
My current projects are using GWT and I'm quite happy with it ... it has a steeper learning curve (plus it requires Java skills) but type-safety at compile time
by smoyer 15y ago
My current projects are using GWT and I'm quite happy with it ... it has a steeper learning curve (plus it requires Java skills) but type-safety at compile time is great and it results in a Javascript application.
Under programming methodologies, how about CI/CT, artifact management and code quality analysis? We're using Jenkins (with Maven) for CI/CT, Nexus as an artifact repository, and Sonar for code quality metrics.
Our operational back-end is CouchDB, but our "documents" are defined by EJB3 annotated models, then generated into code that handles the same objects in JSON format. The benefit of this is that we can (and do) export the operational data into an RDBMS (PostgreSQL ... it is great) for reporting and dashboarding. We clearly fall into the NoSQL camp that defines the term as "Not only SQL".
Great start and I hope I've added some useful information to your pool.