JAQ Stack

Java – jAvascript – sQl / nosQl Technology Stack at http://jaqstack.com


This article introduces the concepts of building micro-services, problems associated with building such applications and some solutions. We also discuss the an example of a complete end-end web applications using Java & Jakarta as a backend, Angular as frontend with NoSql or SQL as data store (aka JAQ Stack). Also the concept of how to build web applications using tech stacks instead of frameworks.

The Problem

As the development of modern web applications is becoming more sophisticated and challenging, developers often face trouble identifying the core platform and building on top of it. While using Java as the primary technology to render a web application, but extending/integrating it with some of the latest javascript technologies is a big hassle. And there are more trends with teams and enterprises using more of Javascript frameworks, especially Angular to build the UI and UX of web applications.

Coming from a Java developer’s perspective, bringing in a application, for example built with Angular into a Java based web application and deploying it together is a very time consuming process and there are no standard procedures or technology that enables them to do it. A quick example of this is applications built on java based CMSes (like Adobe Experience Manager), the web application need to be deployed as single jar package with the UI embedded into the jar.


JAQ Stack fills in this gap and simplifies the process for developers to build a complete web application using angular as frontend, Java as backend and with capability to connect to any database. All of this without the need to learn any new technology or a framework. Applications with JAQ Stack cane built as (A) Monoliths – where the application stack comes with pre-built maven profiles and examples projects that enable developers to bring in an Angular application into a Java EE based web application to build a single deployable War/Jar file. This helps DevOps to manage the entire application as one deployment, as in most standard monoliths; and (B) MicroServices – where the application can be built as micro-services with the frontend and backend deployed as separate entities and communicating with each other using standard RESTful architectures.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s