Skip to main content

[part 1] Spring State-of-the-art microservices full project

In this blog I want to introduce something I've been working on for a while last month, it's a java, spring boot 2, microservices application to demonstrate best of breed, state of the art spring tech stack.

the app itself is not new, it's good old Nutracker (a macro nutrition log & diary) I wrote this app as a monolith before and now I split it into different microservices with my focus on the architectural components that becomes essential with moving to a distributed system.

In microservices you basically leave the easy-to-debug and easy-to-write monoliths behind you to embrace a new mindset of thinking, one that is more complex and challenging to code, test, debug and deploy. and the reason why you may want to do that is to achieve more flexibility and scalability gains that will become more costly when the application gets beyond the early development stages.

Software starts simple but over time we add more features, we change old ones and we adapt new technologies, and if we are successful we receive more traffic, because all of that and other reasons, we need to write code in a way that:

1- allows good definitive boundaries between our different domains, and allows each domain to grow in somewhat isolated autonomous manner.

2- allows ease of change and replacement, code is as alive as we are, it's an abstraction of our thoughts and behaviors and needs, you can't write code, leave it, and expect it to live forever, it should grow, and then it should die, to be replaced, it's a natural life cycle that we should embrace.
monoliths can be hard to be let go because we then have to rewrite the whole thing, which is impossible.. we can only rewrite small chunks at a time.

3- Reactive: reactivity according to the reactive manifesto means being:
responsive, elastic, message driven & resilient. our app, infrastructure, processes to write and ship code should revolve around those concepts. we should be able to respond quickly, scale up and down, react to and publish events that drive our app behavior and be resilient to failures in a way that the whole app doesn't collapse in case of the unexpected.

more resources about this in case you need a start:

- Building Microservices: Designing Fine-Grained Systems

The code

 In this repository you can find the code, you should be able to pull and run with docker.

here is the description and highlights of this architecture :

  • Domain services: entries, food-catalog, identity
  • Support services: config-server, eurka discovery, boot admin, OAuth2 auth-server
  • frameworks: spring boot 2 stack, webflux (reactive).
  • docker for containers, docker-compose for local dev env
  • concerns and design goals:
    • Isolated and autonomous
    • Resilient, Fault tolerant
    • Responsive
    • Efficient
    • Scalable/ Elastic/ Highly available
    • Monitored & traceable
    • Developer quality of life (strong tooling and fast workflow)
  • patterns:
    • service registry & discovery (Eurka)
    • central runtime-changable configurations (spring config server)
    • circuit breakers (resilience4j)
    • client side load balancing (Ribbon)
    • reactive async I/O flow (reactor)
    • stateless token based authentication (OAuth2 + jwt)
    • Api gateway as single point of entry (spring cloud gateway)
    • Monitoring:
      • health checking
      • logs aggregation
  • Technologies:
    • Spring boot 2: spring data, webflux, test
    • Netflix OSS: eurka, ribbon
    • resilience4j, circuit breaker
    • Monitoring: Elastic stack (filebeat, elastic search, kibana) , spring actuator & admin, Zipkin, slueth
    • containerization: docker
    • spring security 5, oauth2 + jwt tokens
    • data stores: mongo db
    • junit 5, mockito, embedded dbs
    • kafka as message bus (currently used by zipkin & slueth for traces)
    • maven, git, shell scripts
    • java 11
There is a lot here and a lot to explain and talk about, however that will be the topic of other posts as part of this series.


Popular posts from this blog

Android RecyclerView - Adding Empty View

So RecyclerView was introduced to replace List view and it's optimized to reuse existing views and so it's faster and more efficient as stated in the documentation: While using it, I faced the issue of missing a useful functionality that is implemented in ListView. that feature is setting an empty view in case there was no records. In ListView it was as simple as this View emptyView = findViewById(; ListView  myList = .... myList.setEmptyView(emptyView); but this method doesn't exist for recycler view so we need a work around until android team fixes this. and here are the screen shots of both list view and recycler view fix List view : Recycler view : here is how I fixed it: here is the content of empty_view, it can be anything. Enjoy.

Microservices 101, Docker & spring boot sample [Windows 10, home]

This is a very simplistic article :) if you are looking for a deep dive in microservices, see my state-of-the-art microservices full archeticture here:   What are micro services? It's an architectural model for web services that basically requires each service** to be completely independent and loosely coupled from other consumer services, or services that it depends on. and it's not a new idea but it's catching pace in today large scale web applications. ** (by service we mean a component that controls and implements the business logic in a self contained manner, like orders service, products catalog service, accounts management service, all of these have their domain and can be clearly separated)   Why micro services emerged ? 1- Easy to scale services: if you have a single application and all the services share the same code base and war (package) then if you receive high demand on one

[PART 5] NuTracker ReactJS app - Add Login & Profile using Router

In the previous part we finished the dashboard read functionality, now we want to add the skeleton for other pages: - Login   In this page the user will be able to login to their account and the dashboard won't show unless the user is logged in. - Profile In this page the user will be able to update their daily nutrition goals that they can track in the dashboard. to be able to have multiple 'pages' in react and navigate from one to one, we need something that can switch the rendered content based on what we want, we can do that with if statements in the App components and store some location state, but why invent the wheel. React Router every major single page app web framework has the routing concept and functionality to interact with the usual browser urls and switch the content based what user should see. for example on the profile page I want the url path to be /profile, and for login to be /login and so on. in more advanced cases you want the users