Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 days ago.
Improve this question
We have a portal where we have bunchof microservices revolving technical capabilities instead of business capabilities or sub-domain.
For e.g. we have a pdf-microservice which hardly generates 2 pdfs. email-microservice, notification-microservice, payment microservice (multiple vendors 6-7), chatbot microservice, crypto-microservice.
Since these MS are revolving around technical capabilities instead of business capabilities, can we group them under for e.g. ancillary or supporting microservice.
The advantage of reducing the microservices is to reduce number of pods and therefore cost savings.
What is recommended pattern here?
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I need to know some efficient way / tools in golang that will help us to detect memory leak in the micro service that is live and running on production
One thing you can do is to compare 2 heap pprofs. You can do it like this:
Extract a heap profile heap0.pprof
Add some load to the application
Extract another heap profile heap1.pprof
Compare them with go tool pprof -base heap0.pprof heap1.pprof
This way you can see exactly what is increasing over time.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
If you have 2 applications that share a lot of code. What is the general guideline before splitting the 2 applications into two different repositories?
Say they share about 80% of code and forms etc. Is it a good idea to split them or keep them together?
If they share 80% of the same code, then yes, split them into three repositories:
the common code becomes a library
first application, including the library
second application, including the library
https://en.wikipedia.org/wiki/Don't_repeat_yourself
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
As I am interested in the concept of graphql I want to understand the benefits of graphql and when to use it?
There are many excellent online resources on this subject, for example https://philsturgeon.uk/api/2017/01/24/graphql-vs-rest-overview/
Main points from this article:
REST and GraphQL are totally different
GraphQL isn't a magic bullet, nor is it "better"
You can definitely use both at the same time
GraphQL is dope if used for the right thing
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
In software engineering project and research a lot of model have been made.
Is there a framework or methodology for evaluating software engineering models and meta-model especially in qualitative perspective?
Yes, there is. In fact, there are a lot of evaluation models, such as: Medvidovic, N., Taylor, R.N. A classification and comparison framework for software architecture description languages, Software Engineering, IEEE Transactions on (Volume:26 , Issue: 1), 2000. and this, and that.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I have a question in my exam that I don't know how to answer it:
Consider that you have a machine for personal use and you are developing various programs. Before going to lunch you want to leave five large programs to compile. In this scenario justifies what / which of the following scheduling algorithms would select: First Come First Served, Shortest Job First, Round Robin or Priority scheduling.
I'd honestly chose Shortest Job First for the simple reason that when I come back from lunch I want to have as many programs available to debug and test as possible.