You can use a single shared database with tables that owned by different microservices if your data is heavily related. Also in case you have strong requirements on data consistency and availiblty of a service. There is pros and cons. Pros Reliability You can have totally consistent incremental backup of the entire system without downtime … Read more
Microservices in my own, hopefully simple terms Monoliths Traditionally web applications are big. You write one piece of software that runs on a server and answers requests in form of HTML, XML or JSON. If you want your web application to do something new, you add that functionality to the existing application. Such big systems … Read more
A message queue is a data structure, or a container – a way to hold messages for eventual consumption. A message broker is a separate component that manages queues.
Architecture is one of those things that isn’t simply a trivia question (e.g., design pattern uses) and is a lot more subjective than other interview topics. There often isn’t a single correct architecture so that makes it trickier to evaluate someone. The most you can get is an idea of how the interviewee thinks. I … Read more
Pros Sam Newman in Building Microservices, enumerates the key benefits of Microservices as following: Technology Heterogeneity With a system composed of multiple, collaborating services, we can decide to use different technologies inside each one. This allows us to pick the right tool for each job, rather than having to select a more standardized, one-size-fits-all approach … Read more
Part of the question, you already answered that Certification is not the only criteria to become a better architecture or designer. You must have real architectural experience by designing some real world application. I think, you can start by 1- Designing a component from ground 0 this may be in your current project, a module, … Read more
ArgoUML has been my friend for many years when it comes to drawing UML. ArgoUML is a tool and you’re asking about both tools and the processes used (i.e. “which artifacts do you create with the tools). We generally stick to user stories (agile project) and do not make “classical” use cases and use case … Read more
Wikipedia explains it better then I could From the article – Top is 1st Tier:
Out of these, I would say #3 is actually the worst, because “CRUD” on its own is not a use case at all; you always CRUD something. Don’t confuse use case <<extend>> with class inheritance. Option #2 is not very good either, because running through a “manage user” use case does not mean you perform … Read more
You’ll have to make a call to each microservice and do the join manually or pass in the relevant user ids to each service. UserMicroservice: SELECT * FROM Users WHERE some condition is true Get list of Users back including their ids. ProductMicroserivce: SELECT * FROM Products WHERE some condition is true AND userId IN … Read more