1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
Hi,
For multiple reasons, you want to have multiple microservices and keep them small and loosely coupled. It's all about separation of duties.
Seehttps://medium.com/@chkamalsingh/microservices-core-principles-80e427261bc8 for best practices
Having small microservices (which is a pleonasm ;-) ) has multiple advantages on the side of NFRs (Non-Functional Requirements):
- better security: the execution roles associated to lambda can have reduced privileges
- performances and scalability can be managed in a more granular fashion
- high-availability: you can have different strategies for your different microservices.
Yes, it's more work upfront but, if you build for the long-term, it will pay back multiple times over the course of the life of your service.
Best,
Didier
I see! Thanks man! One final question, if my chatbot microservice needs to access the db to get some data, it should call the main data ingest microservice that is inserting the data into the DB to get the response. Or should the second microservice also map the db and the same table to get that data directly without calling the data ingest microservice?
My take is that you should keep the ingest service independent from read requests: you can separate concerns and avoid write permission when unneeded. So, it is better from my standpoint to reads from the chatbot service.
I see, thanks man!
Interesting project that you are building with leading-edge techs! Good luck. Thanks for accepting my answer.