You are not likely to benefit from a Microservices architecture if all the services share the same database tables. This is because you are effectively tightly coupling the services. If a database table changes all the services will have to change. You have to understand that the whole reason for a Microservices architecture is to … Read more
Instead of outright suggesting AGAINST this idea mainly due to separate stack requirements I will lay out the trade offs and provide some restrictions which will make this possible. the page consists of several components which would be running autonomously We all know this is offered out of box in Angular components with clear demarcation … Read more
Gist (for those who want just the gist) Kafka – Publish & Subscribe (just process the pipeline, will notify once the job is done) REST – Request & Await response (on-demand) Kafka – Publish once – Subscribe n times (by n components). REST – Request once, get the response once. Deal over. Kafka – Data … Read more
As I was expecting – people try to fit everything into a concept even if it does not fit there. This is not a criticism, this is an observation from my experience and after reading your question and other answers. Yes, you are right that microservices architecture is based on asynchronous messaging patterns. However, when … Read more
Edit: Since Oct 23,2018 the gRPC-Web project is GA, which might be the most official/standardized way to solve your problem. (Even if it’s already 2018 now… 😉 ) From the GA-Blog: “gRPC-Web, just like gRPC, lets you define the service “contract” between client (web) and backend gRPC services using Protocol Buffers. The client can then … Read more
This is subjective but the following solution worked for me, my team, and our DB team. At the application layer, Microservices are decomposed to semantic function. e.g. a Contact service might CRUD contacts (metadata about contacts: names, phone numbers, contact info, etc.) e.g. a User service might CRUD users with login credentials, authorization roles, etc. … Read more
This is a very important question because a few people get lured by all the buzz around microservices, and there are tradeoffs to consider. So, what are the benefits and challenges of microservices (when compared with the monolithic model)? Benefits Deployability: more agility to roll out new versions of a service due to shorter build+test+deploy … Read more
This is a very open question but I will try to illustrate why Elixir/Erlang may be the best platform out there for developing distributed systems (regardless if you are working with microservices). First, let’s start with some background. The Erlang VM and its standard library were designed upfront for building distributed systems and this really … Read more
When performance or latency doesn’t matter too much (yes, we don’t always need them) it’s perfectly fine to just use simple RESTful APIs for querying additional data you need. If you need to do multiple calls to different microservices and return one result you can use API Gateway pattern. It’s perfectly fine to have redundancy … Read more
It is easier to think about them if you realize they aren’t mutually exclusive. Think of an API gateway as a specific type reverse proxy implementation. In regards to your questions, it is not uncommon to see both used in conjunction where the API gateway is treated as an application tier that sits behind a … Read more