Skip to content
/ jiqs Public template

Java stack proposal using a composition of libraries

Notifications You must be signed in to change notification settings

SuppieRK/jiqs

Repository files navigation

JIQS

The work on this software project is in no way associated with my employer nor with the role I'm having at my employer.

I maintain this project alone and as much or as little as my spare time permits using my personal equipment.

JIQS (pronounced as "jicks," rhyming with "kicks") repository offers a template for the alternative highly customizable Java microservice stack with focus on simplicity, modularity and control over dependencies where each piece can be determined individually and excluded / replaced.

It opens a path for platform engineers to craft a bigger abstraction, tailored for specific company business needs to reduce friction during development.

Please, review each module README.md files for more specific information, as well as comments in the codebase.

What contributes to the simplicity?

  • Focusing on Java language, less focus on the annotations / frameworks to stay true to YAGNI principle.
  • Focusing on pure SQL, no ORM for several reasons.

What are the disadvantages?

  • No "plug-n-play".
  • Requires more experience to make right decisions.
  • No textbook definition on how to do things:
    • Potentially a breeding ground for a poorly documented internal framework with non-transferable knowledge.

What are the advantages?

  • Select the tech stack most suitable for your business needs, which usually will perform better than the generic stack.
  • Better control over dependencies, which also improves security posture.
  • Less framework-biased hiring process, leaving more room to explore problem-solving and language skills.

About

Java stack proposal using a composition of libraries

Topics

Resources

Stars

Watchers

Forks

Languages