This content originally appeared on DEV Community and was authored by Ted Ngeene
Lately, I've been tending to lean more towards employing a monolithic approach in system architecture. On paper, using micro-services seems like an ideal solution. The fact that you can decouple a project into smaller manageable bits is good. However, from experience and a couple of blog posts and videos I've watched, they do introduce a lot of complexities. Just to mention a few would be; giving database access to a microservice poses major security risks if not properly implemented, error handling, and especially if the said microservice is down would essentially make the system fail, connection error, read timeout, resource not found...you have to deal with many error scenarios.
I'm not completely against them, for example I believe a microservice should do one thing and do it really well. A good example would be sending sms notifications. This wouldn't really need to interact with any database. Just accept a list of phone numbers and send out the messages.
So my question is; when are my microservices appropriate and do we really need them as much as folks preach?
This content originally appeared on DEV Community and was authored by Ted Ngeene
Ted Ngeene | Sciencx (2021-11-30T23:52:25+00:00) When are microservices appropriate?. Retrieved from https://www.scien.cx/2021/11/30/when-are-microservices-appropriate/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.