microservices

I'm developing Spring Boot + Authorization Server + OAuth Resource Server . In this example I can easily query though postman over spring-microservices-oauth-server and get the protected data. I created the client to access the data which postman is doing. But I am getting below error, which doesn't get clear to me. Using Spring Boot v2.1.1.RELEASE and spring-cloud-dependencies version Greenwich.RC2 . Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is error="access_denied", error_description="Access token

I am using kafka as a message bus for Micro Service architecture, hence multiple services listen on a topic for a message. Therefore, the services are highly dependent on the topic to be live. But, there are many instances where I get leader not available , broker not available and leader= - 1 on the topics. Now, I am not sure if I can rely on the kafka topics, as services get interrupted when there are issues on the topics with cause issues in the platform. Can someone throw some light on the reliability and dependability on the topics and can we recover if we can across the above issues. I

Along with a few others, I am having issues using a micro services architecture of applications and employing docker-compose the way I want to. Summary: I have X micro service projects (lets call these project A , project B and project C . Each micro service depends on the same containers (lets call these dependency D and dependency E . The Problem: Ideally, project A , B and C would ALL have both dependencies ( D & E ) in their docker-compose.yml files; however, this becomes an issue as docker compose sees these as duplicate containers when in reality, I would like to reuse them. Here is an

Lets say we have 5 microservices (μS) and each microservice requires one database with a few tables. Each of these services needs to be able to scale including the database queries. To do that we have a few options that I know of: 1. 1-μS; 1 instance; 1 DB instance Don't scale horizontally, just vertically. 2. 1-μS; N instances; 1 DB instance Every instance of a service gets to read and write to the same database. Simple way to scale if the service processing is the bottleneck. 3. 1-μS; N instances; HA DB cluster Every instance of a service gets to read and write to the same HA database. Good