User talk:Marvin The Paranoid

I greatly appreciate, if you could provide valid reasons for rejecting my contributions. It needs an introduction. Since you rejected my introduction, please provide one. Please find a better more concise introduction. Keep in mind that the introduction must be in laymen terms.

I am disappointed that people don’t have good understanding of basics of the MSA deciding what is right and what is wrong. Can you tell me, what is MSA? There is no dispute that the Microservices must be loosely coupled, for example, by employing a mechanism for such as SoA for loose coupling.

I never heard anyone using decomposing of monolith. Decomposing means decaying in laymen terms. More appropriate terms include “partitioning”, “dividing” or “breaking-up” of a monolithic application (by employing a suitable methodology).

The core idea behind MSA is (1) partitioning a monolithic application into multiple microservices (by employing a suitable methodology), and (2) deploying the application by loosely coupled all the microservices, after designing, development and testing each of the microservices individually (usually in parallel by separate teams).

Who doesn’t know this? How is it original research? It is like blind leading blind. Kindly don’t give a confusing introduction to lawmen, who is new to MSA and wish to know, what is MSA. — Preceding unsigned comment added by Arjunvarma1p (talk • contribs) 19:09, 6 October 2019 (UTC)

@Arjunvarma1p: - Hi. I had put an explanation into the edit reverting your changes, but let me explain more. Wikipedia policies dictate that an article cannot be an original source of information. If an expert were to explain a subject here, they would have to cite authoritative / journalistic references to where their statements were sourced from. Your edits did not meet this criterion - which is why they were flagged as "original research". It doesn't matter how well settled the information the knowledge is - a lay person outside the field needs to be able to follow the source of the information.

The other aspect to your edits were that the same information was present in the subsequent paragraphs. The partitioning of an application into smaller blocks for the purposes of improving scalability and development velocity are items that were already covered in the existing introduction. I didn't see anything new being introduced, and your edits made for awkward reading. If you want to add something knew, by all means, do so, but please merge in your ideas with the existing content instead of writing that is disjoint from whats already there.

Regarding the point of your terminology, I believe this is probably due to where in the world you are working. I've been working in the USA for the past 25 years, and I can assure you that "decomposition" is indeed used in the software industry as described within the article. In fact, in the field of microservices where I am a practitioner, the correct phrase is indeed "decomposing a monolith". If you want to change the terminology, please make it neutral, and make sure that it is reflected consistently within the article. Please don't assume that just because you aren't familiar with the term, that its invalid.

Grayfell - if you'd like to add anything, please do so. A really paranoid android (talk) 19:48, 6 October 2019 (UTC)

@Grayfell: - adding a ping to Grayfell because I'm not sure the previous edit did it right. A really paranoid android (talk) 20:01, 6 October 2019 (UTC)

arjunvarma1p - Let me explain, why I feel introduction is misleading. Kindly Keep in mind that an introduction cannot start with “there is no consensus on what is MSA” or “There is no single definition for this processes.”. Please tell what the processes are.

There is a clear consensus about “What is MSA”, which certainly includes at least two processes (1) a variant of the service-oriented architecture (SOA) architectural style that structures a monolithic application as a collection of loosely coupled services by (2) partitioning the monolithic application into multiple services known as microservices.

I respectfully disagree, if you say there is no consensus on what is MSA. It is clearly wrong and misleading information. I agree that there is no consensus or clear definition for processes such as methodologies for partitioning or mechanisms for loosely coupling.

Kindly keep in mind that large percent of software engineers not yet know what is MSA. The go to place to get basic introduction is Wikipedia. Likewise, many non software engineers or laymen refer to Wikipidea to know, what MSA is. The introduction gives an impression that there is no consensus on what is MSA.

Since you don’t like my introduction, please give an accurate introduction start by using things that have consensus and list few processes that have no definitions. Kindly consider my inputs to give accurate introduction.

arjunvarma1p - Non-MSA approach for building an application it building it as a large monolith? Isn’t it a fact: MSA requires partitioning the monolith into multiple services, referred to as microservices?

Can you tell me, what is the single most defining difference between MSA and non-MSA approach? The single most defining requirement for the MSA is partitioning the monolith into multiple microservices.

Although it is not perfect, since it is close to the fact about MSA, I am paraphrasing a statement from the first paragraph: a variant of the service-oriented architecture (SOA) architectural style that structures the application as a collection of loosely coupled microservices.

Even the first paragraph assumes that the reader already has knowledge about the MSA. It must give correct introduction to laymen. I agree, there are many things that has no consensus, but there are few things that do have consensus.

Where did this page mentioned the defining characteristic of MSA, compared to traditional non-MSA monolithic applications? Isn’t it an essential information? Kindly fix the misleading and missing information. If you can’t fix, let other’s fix the mistakes and fill the essential information that is missing.

This statement in the first paragraph is confusing to any laymen: The benefit of decomposing an application into different smaller services is that it improves modularity. This assumes that a layman already knows that the application must be decomposed into services.

Where did it mention that the essential requirement of MSA is decomposing an application? When I mentioned it in introduction, you think it is original research (that requires reference). Isn’t it a contradiction? There are so many mistakes or missing information.