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
https://www.amazon.ca/Building-Microservices-Designing-Fine-Grained-Systems/dp/1491950358/
- https://12factor.net/
- https://www.amazon.ca/Cloud-Native-Java-Designing-Resilient/dp/1449374646


The code

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

https://github.com/blabadi/nutracker-microservices

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.



Comments

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:

https://developer.android.com/training/material/lists-cards.html

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(R.id.mylist_empty_view);
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.

Creating your own OAuth2 server and clients using spring security - part 1

In this series of posts, I'll try to put together a simple working example on how to create your own OAuth2 server.

if you want to know more on OAuth2 and when to use it as authentication and authorization protocol then you can search about it on google and i'll put some URLs later.

Now I assume you are familiar with java web applications using Spring and maven.

to get started we need to create the server side with all dependencies required and i'll list them here, i'll use maven 2 to ease downloading dependencies for us.


Steps:

1- Create new maven project with arch type webapp:



2- Add the required depenedencies for spring, spring security, spring-oauth2, hibernate & other libraries (required for this tutorial only you can use other libraries if you like)

https://gist.github.com/anonymous/d33a31ddc3ba84375cf3

3- I used hibernate to automate the creation of the schema required by spring OAuth2 to manage tokens (it's required to have schema created in db if you a…

Android - Multiple themes for one application

Sometimes you want to have multiple themes for your app
one strong example is having the ability to switch between dark and light themes because during night, a white bright screen can really be annoying for users eyes

Android will do most of the work for you but it may be required to change icons between themes to fit colors
In this blog I'll show a simple app with both dark and light themes and how to change icons without having to do that from code and keep things clean and centralized.
first of all let's create our activity, it will look something like this :


In /rest/values/styles.xml, we inherit Theme.AppCompat
 <!--
        Base application theme, dependent on API level. This theme is replaced
        by AppBaseTheme from res/values-vXX/styles.xml on newer devices.
    -->
    <style name="AppBaseTheme" parent="Theme.AppCompat">
        <!--
            Theme customizations available in newer API levels can go in
            res/values…