Essay Writer » Essay Blog » Computer Science Essays Help » Microservices Architecture

Microservices Architecture

Total Required 1000 words

5 main post 100-100 words each&

10 students post reply 50 words each

Due in 2 days

Course: MIS 603 Microservices Architecture

Also read: Influences Of Ancient Architecture

Module 2.1 (main post 100 words, two student reply post 50-70 words each)

Module 2.1 – Learning Activity 1:

Loosely Bounded and High Cohesion

Learning Activity 1: Loosely Bounded and High Cohesion – Discussion forum post

After reading the essential resource from Newman (2015) explain what the terms ‘loosely bounded’ and ‘high cohesion’ mean to you?

Reference

Newman, S. (2015). Building microservices: Designing fine-grained systems. California, USA: O’Reilly Media. Retrieved from  https://ebookcentral-proquest-com.ezproxy.laureate.net.au/lib/think/reader.action?docID=1938300&ppg=50

Feel free to do further web exploration of these terms to broaden your understanding. Describe each of these terms in no more than 100 words.

Post your answer to the Module 2.1 Loosely Bounded and High Cohesion – discussion forum.

Please read through other students’ posts and comment on why you agree, disagree or can provide help with another students’ post. Please reply to at least two other students’ posts.

Student post 1 :

RE: Module 2.1 – Learning Activity 1: Loosely Bounded and High Cohesion

there are two types of designer one who uses the right process and the other ones are those who use the assumption which are not going to to be correct every time.

when you are design on the micro-service system you should take care to the impact of your assumptions.

system will called perfect when your system helps the organisation to achieve its goals. micro services cannot address all the desired outcome some time you have to trade off some. good designers make a list at the start of the system and check which outcome is more important for the organisation.

sketching in system is very important and it should be in easy format because sometimes you have to change it at very last if it took to much time and effort it will be very hard for you to make a new one.

Student post 2 :

RE: Module 2.1 – Learning Activity 1: Loosely Bounded and High Cohesion

COLLAPSE

Top of Form

After studying the article, loosely coupling as it regards to microservice is the aspect of a system where a change to one service does not affect other part of the system. It reduces the chances of a system towards having a problem and reduces chatty communication that might lead to the system having a tight coupling. High cohesion for example according to the article is about finding a solution without having to risk other compartments involved in the system, it ensures that the problem is found in one place and that the compartments involved can communicate with each other as to be able to fix it.

Bottom of Form

Module 2.2 (main post 250 words, two student reply post 50-70 words each)

Module 2.2 – Learning Activity 2:

Splitting the Monolith

More to read: Computer Organization ( Architecture) Homework

Top of Form

Learning Activity 2: Splitting the Monolith – Discussion forum post 

After reading essential readings ‘They say that breaking up monolithic systems is hard to do’ McKendrick (2019) and Newmans’ (2015) ‘Reasons to split the monolith’, compare and contrast these two perspectives.

In your opinion, based on the reasons given by Newman (2015), the benefits we have discussed in Module 1 and the difficulties identified by McKendrick (2019), do you think that microservices are a ‘no brainer’ for ever organisation? Give reasons for the position that you take.

Describe your position in no more than 250 words each.

Post your answer to the Module 2.2 Splitting the monolith discussion forum.

Please read through other students’ posts and comment on why you agree, disagree or can provide help with another students’ post. Please reply to at least two other students’ posts.

Student post 1 :

RE: Module 2.2 – Learning Activity 2: Splitting the Monolith

COLLAPSE

Top of Form

Yes, I do think that micro services are “no brainer” because a lot of reasons can be provided while supporting this statement. The reasons that can support this statement are as follows.

  1. i) One will require to be filled regarding rapid provisioning as well as deployment of apps. With gradual turn of events and nonstop conveyance, microservices cause your association to remain alert. Staff ought to be capable in a flash to arrange assets to stay aware of the speed needed to take advantage of microservices.
  2. ii) Rebost monitoring should be must thing. Since each help depends on its own language, stage, and APIs, and you will arrange numerous groups working all the while on various substances of your microservices project, you need hearty checking to viably screen and deal with the whole foundation.

iii) One must culture of devops. To work in cross-utilitarian groups, your business should join devops practices and culture. In a conventional setting, designers are centered around highlights and functionalities, and the tasks group is on the snare for creation challenges.

  1. iv) testing could get very complex. Alongside microservices, the testing is not as straightforward. Every service holds its separate dependencies, directs as well as others transitives.

Student post 2

I think the monolithic systems are too large and complex to fully understand and made changes fast and correctly.

benefit is that the system will be more scalable, and the challenge is that the complexity will be increased in the system. testing could get very complex. Alongside microservices, the testing is not as straightforward. Every service holds its separate dependencies, directs as well as others transitives.

Due in 2 days

Course: MIS604 Requirements Engineering

Learning Activity 1,2,3

(Main post 100 words, two student reply post 50 words each)

Module 2.1 Learning Activity 1:

Stakeholder Nomination Discussion Forum Post

Top of Form

Consider this reading – why do you think this technique is used? What are some of the potential pitfalls of this technique that need to be considered?

APA Reference:

Cadle, J., Paul, D., & Turner, P. (2014). Business analysis techniques: 99 essential tools for success. Swindon, UK: BCS Learning and Development Limited. Retrieved from https://ebookcentral-proquest-com.ezproxy.laureate.net.au/lib/think/reader.action?docID=1759635&ppg=103

Share your thoughts in no more than 100 words each.

Post your answer to the Module 2.1 Stakeholder nomination discussion forum.

Please read other students’ posts and comment on why you agree, disagree or can provide help with another students’ post.

Please reply to at least two other students’ posts.

Student post 1:

RE: Module 2.1 Learning Activity 1: Stakeholder Nomination Discussion Forum Post

Top of Form

Firstly, this approach is more focused on internal stakeholders only because the project sponsor selects the managers and managers selects the other employees. Secondly, the authority of selecting the stakeholder is at the higher level. Additionally, these managers may select the stakeholder who is leaner towards their ideas, who support their views and perspective which is not a fair method of selecting stakeholders. Moreover, this method of stakeholder nomination is not flexible.

Student post 2:  

RE: Module 2.1 Learning Activity 1: Stakeholder Nomination Discussion Forum Post

Top of Form

The process of identifying an initial collection of stakeholders is relatively simple, and it is primarily accomplished by stakeholder nomination. However, depending on people who have been identified by the sponsor or another senior manager can be dangerous. Furthermore, a more systemic approach, such as the stakeholder wheel discussed below, ensures that all stakeholder perspectives are considered, including those that appear to be irrelevant at first glance.

The pitfalls of stakeholder technique are –

Identifying all the stakeholders, classifying stakeholders, mapping expectations, using appropriate communication methods, engaging stakeholders.

Bottom of Form

Bottom of Form

Bottom of Form

Module 2.1 learning Activity 2:

Defining a Stakeholder Discussion Forum Post

Top of Form

The term ‘stakeholder’ is intentionally broad. Why do you think this is the case?

Share your thoughts in no more than 100 words each.

Post your answer to the Module 2.1 Defining a stakeholder discussion forum.

Please read other students’ posts and comment on why you agree, disagree or can provide help with another students’ post.

Please reply to at least two other students’ posts.

Bottom of Form

Student post 1:

Stakeholder means individual or group that have some kind of interest connected with the company. They can effect or sometimes can be effected by the business. The term stakeholder is broader in the sense that it involves everyone that has some kind of interest affix with the company. This one word could be used instead of mentioning the name of each stakeholder. Typically stakeholders for a company include investors, supplies, customer and employees (Fernando, 2021).

Student post 2:

Stakeholder term referred to any individual, group of persons or company who may actively involve in project or whose interests may be positively or negatively affected with result of the project or activity performed by a project. Stakeholders mainly depend upon the nature of project, job of the project manager is not only identifying the potential stakeholders but also menage the influence of stakeholders to ensure positive outcome (Ajaz, M.,2016).

Module 2.2 Learning Activity 2:

Elicitation Technique Discussion Forum Post

Top of Form

Read through the discussion forum to see what other students have written about and then select an elicitation technique that is different from those that have already been covered. Describe the technique and what is required in its use in elicitation in no more than 200 words – be sure to share any benefits and drawbacks of the technique.

Post your answer to the Module 2.2 Elicitation technique discussion forum.

Please read other students’ posts and comment on why you agree, disagree or can provide help with another students’ post.

Please reply to at least two other students’ posts.

Bottom of Form

Student post 1:

Elicitation techniques are used in engineering, knowledge, science, education, management & in psychology to collect the amount of data. This is a way to collect the knowledge from the people. Information is gathered from people directly by conducting activities such as interviews, surveys, observations, etc. Requirement workshops, interviews, questionnaires, surveys, brainstorming challenges are the methods to collect the knowledge or the information from directly people to analyse that & to make a decision. There are several advantages of elicitation techniques for which it is highly used are listed below:

  1. It gives the rich & detailed data to analyse & to make a decision on things.
  2. It gives the accuracy or the real information as people share their real experience or the knowledge about the subject.

Some disadvantages or the drawbacks are also there of elicitation techniques which are being used in the knowledge gathering given below:

  1. It includes a large number of people to get the effective knowledge.
  2. Rapid data collection methods do not seem feasible.
  3. Qualitative data seems hard to analyse.

Student post 2:

For this activity, I have selected the questionnaire which is a user involvement technique.

The questionnaire is a virtual and asynchronous option that consists of sharing a list of questions (with online tools such as survey monkey or google survey) with stakeholders to elicit requirements. It can be formally designed. In that case, it is conducted closely with researchers and designed by a market research department. BA can also elaborate an informal questionnaire to get solution ideas or assess the impact of a change.

BA requires content and distribution planning to engage stakeholders. It should be a short survey (between 5 and 10 questions) with clear questions. Closed-ended questions are used to ensure quick answers. Questionnaires are tested on a small group of stakeholders before sending out the questionnaire (Champagne, 2020, p. 118).

Advantages

-Giving more time to stakeholder

-No schedule issues (easy time management)

-No location issues

-Large group of people (internal and external stakeholders)

Disadvantages

-Difficulty to observe body language and reaction

-Engagement might be difficult

-Some questions such as multiple choices questions are limiting (not sure that the stakeholder truly agree)

Student post 1: Student post 1: Bottom of Form

Bottom of Form

Bottom of Form

Bottom of Form

Last Updated on March 11, 2021

Don`t copy text!
Scroll to Top