What is involved in Microservices
Find out what the related areas are that Microservices connects with, associates with, correlates with or affects, and which require thought, deliberation, analysis, review and discussion. This unique checklist stands out in a sense that it is not per-se designed to give answers, but to engage the reader and lay out a Microservices thinking-frame.
How far is your company on its Microservices with .Net Core journey?
Take this short survey to gauge your organization’s progress toward Microservices with .Net Core leadership. Learn your strongest and weakest areas, and what you can do now to create a strategy that delivers results.
To address the criteria in this checklist for your organization, extensive selected resources are provided for sources of further research and information.
Start the Checklist
Below you will find a quick checklist designed to help you think about which Microservices related domains to cover and 142 essential critical questions to check off in that domain.
The following domains are covered:
Microservices, Amazon Standard Identification Number, Application programming interface, Case study, Cloud application, Communications protocol, Computer network, Continuous delivery, Continuous deployment, Conway’s law, Cross-cutting concern, Distributed software, Domain-driven design, Everything is a file, Fallacies of distributed computing, Fault tolerance, Function call, Hewlett Packard Labs, Load balancing, Loose coupling, Message format, Modular programming, Monolithic application, Monolithic system, Network latency, Network traffic, Representational state transfer, Resource-oriented computing, Self-contained Systems, Serverless computing, Service-oriented architecture, Service granularity principle, Shared memory, Software component, Software deployment, Software development, Software ecosystem, Software interface, Software library, Software testing, Unix philosophy, User interface, Web-oriented architecture, Web service:
Microservices Critical Criteria:
Pilot Microservices strategies and oversee Microservices requirements.
– Do we aggressively reward and promote the people who have the biggest impact on creating excellent Microservices services/products?
– What are the usability implications of Microservices actions?
– Are we Assessing Microservices and Risk?
Amazon Standard Identification Number Critical Criteria:
Win new insights about Amazon Standard Identification Number management and don’t overlook the obvious.
– A compounding model resolution with available relevant data can often provide insight towards a solution methodology; which Microservices models, tools and techniques are necessary?
– What may be the consequences for the performance of an organization if all stakeholders are not consulted regarding Microservices?
– What other jobs or tasks affect the performance of the steps in the Microservices process?
Application programming interface Critical Criteria:
Participate in Application programming interface issues and diversify disclosure of information – dealing with confidential Application programming interface information.
– Which customers cant participate in our Microservices domain because they lack skills, wealth, or convenient access to existing solutions?
– What are the barriers to increased Microservices production?
Case study Critical Criteria:
Have a meeting on Case study management and point out improvements in Case study.
– Who is responsible for ensuring appropriate resources (time, people and money) are allocated to Microservices?
– Is Microservices Realistic, or are you setting yourself up for failure?
Cloud application Critical Criteria:
Read up on Cloud application quality and integrate design thinking in Cloud application innovation.
– Are there any easy-to-implement alternatives to Microservices? Sometimes other solutions are available that do not require the cost implications of a full-blown project?
– What do I need to do specifically in my cloud application so that it can restore itself back to original state in an event of failure (hardware or software)?
– Are we Working with cloud applications?
– Is the scope of Microservices defined?
– What are our Microservices Processes?
Communications protocol Critical Criteria:
Track Communications protocol projects and report on the economics of relationships managing Communications protocol and constraints.
– What are your current levels and trends in key measures or indicators of Microservices product and process performance that are important to and directly serve your customers? how do these results compare with the performance of your competitors and other organizations with similar offerings?
– How do your measurements capture actionable Microservices information for use in exceeding your customers expectations and securing your customers engagement?
– Will Microservices have an impact on current business continuity, disaster recovery processes and/or infrastructure?
Computer network Critical Criteria:
Deliberate Computer network tactics and customize techniques for implementing Computer network controls.
– At what point will vulnerability assessments be performed once Microservices is put into production (e.g., ongoing Risk Management after implementation)?
– Who will be responsible for deciding whether Microservices goes ahead or not after the initial investigations?
– Is the illegal entry into a private computer network a crime in your country?
– Why are Microservices skills important?
Continuous delivery Critical Criteria:
Ventilate your thoughts about Continuous delivery outcomes and describe which business rules are needed as Continuous delivery interface.
– A competitive edge, excellent. Focus on continuous delivery. Move on to continuous deployment because that is going to provide your business value. But look at your individual business. Look at your environment and say is that what gives us the competitive edge?
– Does Microservices create potential expectations in other areas that need to be recognized and considered?
– Does your organization run a Continuous Integration and Continuous Delivery (CI/CD) process?
– Can Management personnel recognize the monetary benefit of Microservices?
– Are accountability and ownership for Microservices clearly defined?
– Does your organization hope to achieve continuous delivery?
Continuous deployment Critical Criteria:
Audit Continuous deployment tactics and report on developing an effective Continuous deployment strategy.
– What Agile Management Method do you use when your Development DevOps team is working in Continuous Deployment mode?
– What is the total cost related to deploying Microservices, including any consulting or professional services?
– Think about the functions involved in your Microservices project. what processes flow from these functions?
Conway’s law Critical Criteria:
Incorporate Conway’s law governance and finalize specific methods for Conway’s law acceptance.
– What are our best practices for minimizing Microservices project risk, while demonstrating incremental value and quick wins throughout the Microservices project lifecycle?
– How can skill-level changes improve Microservices?
Cross-cutting concern Critical Criteria:
Investigate Cross-cutting concern leadership and look in other fields.
– Who are the people involved in developing and implementing Microservices?
– How is the value delivered by Microservices being measured?
Distributed software Critical Criteria:
Extrapolate Distributed software projects and reduce Distributed software costs.
– Will new equipment/products be required to facilitate Microservices delivery for example is new software needed?
– Do you monitor the effectiveness of your Microservices activities?
Domain-driven design Critical Criteria:
Explore Domain-driven design engagements and question.
– Can we add value to the current Microservices decision-making process (largely qualitative) by incorporating uncertainty modeling (more quantitative)?
– How do we Lead with Microservices in Mind?
– What is our Microservices Strategy?
Everything is a file Critical Criteria:
Bootstrap Everything is a file failures and assess and formulate effective operational and Everything is a file strategies.
– In a project to restructure Microservices outcomes, which stakeholders would you involve?
– What tools and technologies are needed for a custom Microservices project?
– What is our formula for success in Microservices ?
Fallacies of distributed computing Critical Criteria:
Probe Fallacies of distributed computing decisions and define what our big hairy audacious Fallacies of distributed computing goal is.
– Marketing budgets are tighter, consumers are more skeptical, and social media has changed forever the way we talk about Microservices. How do we gain traction?
– What prevents me from making the changes I know will make me a more effective Microservices leader?
– How do we Improve Microservices service perception, and satisfaction?
Fault tolerance Critical Criteria:
Check Fault tolerance leadership and frame using storytelling to create more compelling Fault tolerance projects.
– Why is it important to have senior management support for a Microservices project?
– What are the fault tolerance, failover, and disaster recovery plans?
– Who needs to know about Microservices ?
– How to Secure Microservices?
Function call Critical Criteria:
Troubleshoot Function call goals and achieve a single Function call view and bringing data together.
– Is there any existing Microservices governance structure?
Hewlett Packard Labs Critical Criteria:
Do a round table on Hewlett Packard Labs planning and handle a jump-start course to Hewlett Packard Labs.
– Do those selected for the Microservices team have a good general understanding of what Microservices is all about?
– Are we making progress? and are we making progress as Microservices leaders?
– Have the types of risks that may impact Microservices been identified and analyzed?
Load balancing Critical Criteria:
Set goals for Load balancing strategies and oversee implementation of Load balancing.
– How does the organization define, manage, and improve its Microservices processes?
– What is a feature of dns server load balancing?
– Why is Microservices important for you now?
– What load balancing technique should we use?
– Do we have past Microservices Successes?
Loose coupling Critical Criteria:
Focus on Loose coupling leadership and maintain Loose coupling for success.
– Where do ideas that reach policy makers and planners as proposals for Microservices strengthening and reform actually originate?
– How do we Identify specific Microservices investment and emerging trends?
Message format Critical Criteria:
Participate in Message format visions and suggest using storytelling to create more compelling Message format projects.
– How do mission and objectives affect the Microservices processes of our organization?
Modular programming Critical Criteria:
Pilot Modular programming results and give examples utilizing a core of simple Modular programming skills.
– What are the record-keeping requirements of Microservices activities?
Monolithic application Critical Criteria:
Do a round table on Monolithic application management and achieve a single Monolithic application view and bringing data together.
– Record-keeping requirements flow from the records needed as inputs, outputs, controls and for transformation of a Microservices process. ask yourself: are the records needed as inputs to the Microservices process available?
– To what extent does management recognize Microservices as a tool to increase the results?
– Who sets the Microservices standards?
Monolithic system Critical Criteria:
Have a session on Monolithic system strategies and find out.
– How likely is the current Microservices plan to come in on schedule or on budget?
– Do Microservices rules make a reasonable demand on a users capabilities?
Network latency Critical Criteria:
Scan Network latency results and create Network latency explanations for all managers.
– Meeting the challenge: are missed Microservices opportunities costing us money?
– Is the Microservices organization completing tasks effectively and efficiently?
– What are all of our Microservices domains and what do they do?
Network traffic Critical Criteria:
Set goals for Network traffic engagements and prioritize challenges of Network traffic.
– What is the source of the strategies for Microservices strengthening and reform?
– Is network traffic screening possible?
– How can we improve Microservices?
Representational state transfer Critical Criteria:
Guide Representational state transfer goals and suggest using storytelling to create more compelling Representational state transfer projects.
– How do we ensure that implementations of Microservices products are done in a way that ensures safety?
– What are the Essentials of Internal Microservices Management?
Resource-oriented computing Critical Criteria:
Inquire about Resource-oriented computing management and change contexts.
– Who will be responsible for making the decisions to include or exclude requested changes once Microservices is underway?
– Is Microservices dependent on the successful delivery of a current project?
Self-contained Systems Critical Criteria:
Focus on Self-contained Systems planning and adjust implementation of Self-contained Systems.
– What are specific Microservices Rules to follow?
Serverless computing Critical Criteria:
Accelerate Serverless computing planning and track iterative Serverless computing results.
– Is there a Microservices Communication plan covering who needs to get what information when?
– Are there recognized Microservices problems?
Service-oriented architecture Critical Criteria:
Frame Service-oriented architecture goals and get going.
– In the case of a Microservices project, the criteria for the audit derive from implementation objectives. an audit of a Microservices project involves assessing whether the recommendations outlined for implementation have been met. in other words, can we track that any Microservices project is implemented as planned, and is it working?
– What are your key performance measures or indicators and in-process measures for the control and improvement of your Microservices processes?
Service granularity principle Critical Criteria:
Add value to Service granularity principle issues and use obstacles to break out of ruts.
– How will you measure your Microservices effectiveness?
Shared memory Critical Criteria:
Demonstrate Shared memory strategies and define what our big hairy audacious Shared memory goal is.
– Have you identified your Microservices key performance indicators?
– What business benefits will Microservices goals deliver if achieved?
Software component Critical Criteria:
Grasp Software component issues and point out improvements in Software component.
– Can we answer questions like: Are all identified requirements allocated to software components?
– What are the top 3 things at the forefront of our Microservices agendas for the next 3 years?
– Do the Microservices decisions we make today help people and the planet tomorrow?
– Who will provide the final approval of Microservices deliverables?
Software deployment Critical Criteria:
Refer to Software deployment strategies and diversify by understanding risks and leveraging Software deployment.
– What are our needs in relation to Microservices skills, labor, equipment, and markets?
Software development Critical Criteria:
Paraphrase Software development visions and oversee implementation of Software development.
– How do you take an approach like CMM that is heavily about management control and measurement and make it light on its feet?
– Among the Microservices product and service cost to be estimated, which is considered hardest to estimate?
– How do scaling issues affect the manner in which you fulfill your goal of identifying your initial scope?
– Will Agile advantages be able to overcome the well-known existing problems in software development?
– Is open source software development faster, better, and cheaper than software engineering?
– What kind of enabling and limiting factors can be found for the use of agile methods?
– What other types of systems might be able to benefit from this component?
– Do we ask in the sprint retrospective: What went well during the sprint?
– Should you have a strict project sequence, or should you be flexible?
– How good are the designers and programmers in the development team?
– What is your favorite project managment interview question?
– what is the minimum we can do to produce a quality product?
– Are there SaaS tools for allocating workers to tasks?
– What does it mean to scale agile solution delivery?
– How can a conceptual agile framework be developed?
– What is and why Disciplined Agile Delivery (DAD)?
– What Can We Learn From a Theory of Complexity?
– How do disciplined agile teams work at scale?
– How do engineers feel about it?
– When should we not use it?
Software ecosystem Critical Criteria:
Cut a stake in Software ecosystem planning and assess and formulate effective operational and Software ecosystem strategies.
– Which Microservices goals are the most important?
Software interface Critical Criteria:
Discourse Software interface quality and pay attention to the small things.
– What is the purpose of Microservices in relation to the mission?
– What vendors make products that address the Microservices needs?
Software library Critical Criteria:
Discuss Software library leadership and stake your claim.
Software testing Critical Criteria:
Discourse Software testing engagements and adopt an insight outlook.
– How do we know that any Microservices analysis is complete and comprehensive?
– How do we manage Microservices Knowledge Management (KM)?
Unix philosophy Critical Criteria:
Be clear about Unix philosophy goals and pioneer acquisition of Unix philosophy systems.
– How will we insure seamless interoperability of Microservices moving forward?
– What are the short and long-term Microservices goals?
User interface Critical Criteria:
Test User interface risks and perfect User interface conflict management.
– What if we substitute prototyping for user interface screens on paper?
– Does a User interface survey show which search ui is better ?
Web-oriented architecture Critical Criteria:
Communicate about Web-oriented architecture failures and look in other fields.
– What are the business goals Microservices is aiming to achieve?
Web service Critical Criteria:
Focus on Web service failures and triple focus on important concepts of Web service relationship management.
– Expose its policy engine via web services for use by third-party systems (e.g. provisioning, help desk solutions)?
– How does this standard provide users the ability to access applications and services through web services?
– What is the best strategy going forward for data center disaster recovery?
– Amazon web services is which type of cloud computing distribution model?
– Which individuals, teams or departments will be involved in Microservices?
This quick readiness checklist is a selected resource to help you move forward. Learn more about how to achieve comprehensive insights with the Microservices with .Net Core Self Assessment:
Author: Gerard Blokdijk
CEO at The Art of Service | http://theartofservice.com
Gerard is the CEO at The Art of Service. He has been providing information technology insights, talks, tools and products to organizations in a wide range of industries for over 25 years. Gerard is a widely recognized and respected information expert. Gerard founded The Art of Service consulting business in 2000. Gerard has authored numerous published books to date.
To address the criteria in this checklist, these selected resources are provided for sources of further research and information:
Microservices External links:
Azure Service Fabric—Building Microservices | Microsoft Azure
Amazon Standard Identification Number External links:
Amazon Standard Identification Number Pictures, …
http://photobucket.com/images/amazon standard identification number
Case study External links:
[PDF]Title of case study – UNFCCC
[PDF]Case Study Titles and Descriptions – Feng Shui …
Guidelines for Writing a Case Study Analysis – Ashford …
Cloud application External links:
Morpheus | Cloud Application Management & …
Cloud Application Manager | CenturyLink
Communications protocol External links:
Modbus-Simple Communications Protocol
Computer network External links:
What is a Computer Network? Webopedia Definition
Continuous delivery External links:
Continuous Delivery – CA Technologies
What is Continuous Delivery? – Continuous Delivery
Continuous Delivery (eBook, 2014) [WorldCat.org]
Continuous deployment External links:
Continuous delivery is sometimes confused with continuous deployment. Continuous deployment means that every change is automatically deployed to production. Continuous delivery means that the team ensures every change can be deployed to production but may choose not to do it, usually due to business reasons.
Conway’s law External links:
Demystifying Conway’s Law | ThoughtWorks
Conway’s Law for Product Organizations | – Rich …
Conway on Conway’s Law – Mel Conway’s Home Page
Cross-cutting concern External links:
What is Cross-Cutting Concern | IGI Global
Aspect4Log – one cross-cutting concern less to worry about!
What is CROSS-CUTTING CONCERN? What does …
Distributed software External links:
[PDF]IBM Distributed Software PT64366 Passport …
[PDF]Distributed Software RAID Architectures for Parallel …
Domain-driven design External links:
What is Domain-Driven Design?
Domain-Driven Design Belgium (Brussels, Belgium) | Meetup
Everything is a file External links:
linux – Everything is a file? – Unix & Linux Stack Exchange
Everything is a file
http://”Everything is a file” describes one of the defining features of Unix, and its derivatives — that a wide range of input/output resources such as documents, directories, hard-drives, modems, keyboards, printers and even some inter-process and network communications are simple streams of bytes exposed through the filesystem name space.
Everything is a file | Opensource.com
Fallacies of distributed computing External links:
[PDF]Fallacies of Distributed Computing Explained
Fault tolerance External links:
[PPT]Fault Tolerance – IIT-Computer Science
Function call External links:
Function Call (C) – msdn.microsoft.com
Function Call (C++) – msdn.microsoft.com
Hewlett Packard Labs External links:
Hewlett Packard Labs | Home
Load balancing External links:
Traffic Manager – Cloud load balancing | Microsoft Azure
AWS | Elastic Load Balancing – Cloud Network Load Balancer
Application Gateway–Load Balancing Solution | Microsoft Azure
Loose coupling External links:
What is loose coupling? – Definition from WhatIs.com
Message format External links:
How to Set the Default Message Format in Outlook
U.S. Navy ditches its ALL CAPS message format – CNN
i need help with text message format | Verizon Community
Modular programming External links:
SLC QBASIC Modular Programming Video Tutorial – …
The Benefits of Modular Programming | WebReference
What is Modular Programming? – Definition from Techopedia
Monolithic application External links:
MONOLITHIC Application | Aluma EasySet
Monolithic system External links:
[PDF]3 Dimensional Monolithic System on a Chip (3DSoC)
Doka Lebanon – Doka OneGo The Monolithic System | Facebook
Network latency External links:
What is Network Latency? – Definition from Techopedia
Large mailbox migrations are slow because of network latency
Global IP Network Latency
Representational state transfer External links:
Representational State Transfer (REST) – reddit
Self-contained Systems External links:
SCS – Self-Contained Systems – SCS vs. Microservices
Self-Contained Systems | Daikin Applied
Vertical Self-contained Systems – Mammoth
Serverless computing External links:
Serverless Computing | Microsoft Azure
What is Serverless Computing? | Cloud Computing – Quora
Serverless Computing | 2017-09-18 | Cloud Strategy …
Shared memory External links:
How to list processes attached to a shared memory …
Software component External links:
Implemented software component checks – docs.infor.com
Software deployment External links:
[PDF]Automating Software Deployment – New York University
Software Deployment Jobs, Employment | Indeed.com
Software development External links:
Online Education and Software Development | Smart Horizons
Software ecosystem External links:
What is Software Ecosystem | IGI Global
Software library External links:
Software Library: MS-DOS Games – Internet Archive
StdLib — Function as a Service Software Library
ABB Substation Automation Software Library – Home
Software testing External links:
Software Testing Certification Information – ASTQB …
Software Testing Strategies and Best Practices | Atlassian
Software Testing, Monitoring, Developer Tools | SmartBear
Unix philosophy External links:
The Unix Philosophy | Linux Journal
Unix Philosophy – hairwigs.store
Unix Philosophy – dubaiuae.store
User interface External links:
Datatel User Interface 5.3
EWS User Interface
User Interface: Hyper-V Manager – technet.microsoft.com
Web-oriented architecture External links:
Web-Oriented Architecture (WOA) – Techopedia.com
Web-oriented Architecture images on Photobucket
Web-Oriented Architecture (WOA) – Gartner IT Glossary
Web service External links:
TVInformation Web Service – Chelsea Reservations
Tax Data Systems – Sales Tax Rates Web Service
Amazon.com – Marketplace Web Service