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 139 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:
Scan Microservices management and remodel and develop an effective Microservices strategy.
– Does Microservices include applications and information with regulatory compliance significance (or other contractual conditions that must be formally complied with) in a new or unique manner for which no approved security requirements, templates or design models exist?
Amazon Standard Identification Number Critical Criteria:
Trace Amazon Standard Identification Number visions and forecast involvement of future Amazon Standard Identification Number projects in development.
– Can we do Microservices without complex (expensive) analysis?
– How do we go about Comparing Microservices approaches/solutions?
– Why should we adopt a Microservices framework?
Application programming interface Critical Criteria:
Scrutinze Application programming interface projects and modify and define the unique characteristics of interactive Application programming interface projects.
– Do the Microservices decisions we make today help people and the planet tomorrow?
– Are there recognized Microservices problems?
Case study Critical Criteria:
Check Case study projects and integrate design thinking in Case study innovation.
– What management system can we use to leverage the Microservices experience, ideas, and concerns of the people closest to the work to be done?
– Is Microservices dependent on the successful delivery of a current project?
– What are our Microservices Processes?
Cloud application Critical Criteria:
Depict Cloud application adoptions and differentiate in coordinating Cloud application.
– How do your measurements capture actionable Microservices information for use in exceeding your customers expectations and securing your customers engagement?
– 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)?
– Meeting the challenge: are missed Microservices opportunities costing us money?
– Do Microservices rules make a reasonable demand on a users capabilities?
– Are we Working with cloud applications?
Communications protocol Critical Criteria:
Inquire about Communications protocol outcomes and develop and take control of the Communications protocol initiative.
– What is the source of the strategies for Microservices strengthening and reform?
– How do we measure improved Microservices service perception, and satisfaction?
– What threat is Microservices addressing?
Computer network Critical Criteria:
Demonstrate Computer network adoptions and look at the big picture.
– what is the best design framework for Microservices organization now that, in a post industrial-age if the top-down, command and control model is no longer relevant?
– Is the illegal entry into a private computer network a crime in your country?
– How can skill-level changes improve Microservices?
– How do we keep improving Microservices?
Continuous delivery Critical Criteria:
Have a session on Continuous delivery failures and balance specific methods for improving Continuous delivery results.
– 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?
– What prevents me from making the changes I know will make me a more effective Microservices leader?
– Does your organization run a Continuous Integration and Continuous Delivery (CI/CD) process?
– Does your organization hope to achieve continuous delivery?
– How do we Lead with Microservices in Mind?
Continuous deployment Critical Criteria:
Depict Continuous deployment management and pay attention to the small things.
– Can we add value to the current Microservices decision-making process (largely qualitative) by incorporating uncertainty modeling (more quantitative)?
– What Agile Management Method do you use when your Development DevOps team is working in Continuous Deployment mode?
– How to deal with Microservices Changes?
Conway’s law Critical Criteria:
Analyze Conway’s law outcomes and pioneer acquisition of Conway’s law systems.
– Do we cover the five essential competencies-Communication, Collaboration,Innovation, Adaptability, and Leadership that improve an organizations ability to leverage the new Microservices in a volatile global economy?
– Do we have past Microservices Successes?
Cross-cutting concern Critical Criteria:
Own Cross-cutting concern leadership and ask what if.
– How do we ensure that implementations of Microservices products are done in a way that ensures safety?
– How can we improve Microservices?
Distributed software Critical Criteria:
Give examples of Distributed software issues and clarify ways to gain access to competitive Distributed software services.
– Think about the functions involved in your Microservices project. what processes flow from these functions?
– Who is responsible for ensuring appropriate resources (time, people and money) are allocated to Microservices?
– What are all of our Microservices domains and what do they do?
Domain-driven design Critical Criteria:
Co-operate on Domain-driven design planning and probe using an integrated framework to make sure Domain-driven design is getting what it needs.
– In what ways are Microservices vendors and us interacting to ensure safe and effective use?
– What potential environmental factors impact the Microservices effort?
Everything is a file Critical Criteria:
Wrangle Everything is a file risks and define Everything is a file competency-based leadership.
– Is there a Microservices Communication plan covering who needs to get what information when?
– Will Microservices deliverables need to be tested and, if so, by whom?
Fallacies of distributed computing Critical Criteria:
Demonstrate Fallacies of distributed computing tasks and raise human resource and employment practices for Fallacies of distributed computing.
– How can we incorporate support to ensure safe and effective use of Microservices into the services that we provide?
– Do several people in different organizational units assist with the Microservices process?
– Are assumptions made in Microservices stated explicitly?
Fault tolerance Critical Criteria:
Start Fault tolerance results and suggest using storytelling to create more compelling Fault tolerance projects.
– What will be the consequences to the business (financial, reputation etc) if Microservices does not go ahead or fails to deliver the objectives?
– What are the fault tolerance, failover, and disaster recovery plans?
– How much does Microservices help?
Function call Critical Criteria:
Distinguish Function call governance and transcribe Function call as tomorrows backbone for success.
– At what point will vulnerability assessments be performed once Microservices is put into production (e.g., ongoing Risk Management after implementation)?
– Does Microservices create potential expectations in other areas that need to be recognized and considered?
– How is the value delivered by Microservices being measured?
Hewlett Packard Labs Critical Criteria:
Accommodate Hewlett Packard Labs leadership and clarify ways to gain access to competitive Hewlett Packard Labs services.
– Where do ideas that reach policy makers and planners as proposals for Microservices strengthening and reform actually originate?
– Why is it important to have senior management support for a Microservices project?
– What are the record-keeping requirements of Microservices activities?
Load balancing Critical Criteria:
Track Load balancing tasks and get answers.
– When a Microservices manager recognizes a problem, what options are available?
– Who will be responsible for documenting the Microservices requirements in detail?
– What is a feature of dns server load balancing?
– What load balancing technique should we use?
Loose coupling Critical Criteria:
Prioritize Loose coupling planning and correct better engagement with Loose coupling results.
– What tools and technologies are needed for a custom Microservices project?
Message format Critical Criteria:
Consolidate Message format outcomes and probe Message format strategic alliances.
– Does the Microservices task fit the clients priorities?
– What are the business goals Microservices is aiming to achieve?
– What is Effective Microservices?
Modular programming Critical Criteria:
Adapt Modular programming management and work towards be a leading Modular programming expert.
– 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?
– Are there Microservices problems defined?
Monolithic application Critical Criteria:
Consult on Monolithic application tasks and ask what if.
– What role does communication play in the success or failure of a Microservices project?
– What about Microservices Analysis of results?
Monolithic system Critical Criteria:
Prioritize Monolithic system projects and gather practices for scaling Monolithic system.
– Who is the main stakeholder, with ultimate responsibility for driving Microservices forward?
– Why are Microservices skills important?
Network latency Critical Criteria:
Guide Network latency visions and assess what counts with Network latency that we are not counting.
– Which customers cant participate in our Microservices domain because they lack skills, wealth, or convenient access to existing solutions?
– What is the purpose of Microservices in relation to the mission?
Network traffic Critical Criteria:
Tête-à-tête about Network traffic tasks and transcribe Network traffic as tomorrows backbone for success.
– What are the usability implications of Microservices actions?
– Is network traffic screening possible?
– Is Microservices Required?
Representational state transfer Critical Criteria:
Guide Representational state transfer projects and learn.
– Do we aggressively reward and promote the people who have the biggest impact on creating excellent Microservices services/products?
Resource-oriented computing Critical Criteria:
Drive Resource-oriented computing risks and plan concise Resource-oriented computing education.
– How do mission and objectives affect the Microservices processes of our organization?
– What are the Essentials of Internal Microservices Management?
Self-contained Systems Critical Criteria:
Interpolate Self-contained Systems issues and look at it backwards.
– Can Management personnel recognize the monetary benefit of Microservices?
Serverless computing Critical Criteria:
Pay attention to Serverless computing decisions and tour deciding if Serverless computing progress is made.
– Will Microservices have an impact on current business continuity, disaster recovery processes and/or infrastructure?
Service-oriented architecture Critical Criteria:
Look at Service-oriented architecture results and perfect Service-oriented architecture conflict management.
– Will new equipment/products be required to facilitate Microservices delivery for example is new software needed?
– What new services of functionality will be implemented next with Microservices ?
Service granularity principle Critical Criteria:
Unify Service granularity principle quality and perfect Service granularity principle conflict management.
– Think about the people you identified for your Microservices project and the project responsibilities you would assign to them. what kind of training do you think they would need to perform these responsibilities effectively?
– What are the Key enablers to make this Microservices move?
Shared memory Critical Criteria:
Co-operate on Shared memory quality and adjust implementation of Shared memory.
– What tools do you use once you have decided on a Microservices strategy and more importantly how do you choose?
– How do senior leaders actions reflect a commitment to the organizations Microservices values?
– What business benefits will Microservices goals deliver if achieved?
Software component Critical Criteria:
Confer over Software component management and achieve a single Software component view and bringing data together.
– Can we answer questions like: Are all identified requirements allocated to software components?
– Who are the people involved in developing and implementing Microservices?
– Who sets the Microservices standards?
Software deployment Critical Criteria:
Audit Software deployment goals and define what our big hairy audacious Software deployment 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?
– Does Microservices analysis isolate the fundamental causes of problems?
– Are accountability and ownership for Microservices clearly defined?
Software development Critical Criteria:
Substantiate Software development tactics and grade techniques for implementing Software development controls.
– Much of the agile advice is oriented towards small teams of up to ten people, who are either co-located or near located, who have ready access to their primary stakeholders, and who are working on software that can be easily organized into a series of small releases. What about large teams?
– Does the software Quality Assurance function have a management reporting channel separate from the software development project management?
– Are meetings viewed as ways for managers to micromanage their teams: what have you done in the last 24 hours?
– Do you think you could provide every last detail the developers need to know right off the bat?
– Is our organization clear about the relationship between agile software development and DevOps?
– Why should a client choose a project team which offers agile software development?
– 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?
– Will the organizational culture support new values of the agile team?
– Should you have a strict project sequence, or should you be flexible?
– What is the best online tool for Agile development using Kanban?
– Will the broader project community be populated appropriately?
– Has Your Organization Adopted One or More Agile Techniques?
– How Agile are Industrial Software Development Practices?
– What does software development maturity really mean?
– What is and why Disciplined Agile Delivery (DAD)?
– How Extreme Does Extreme Programming Have to Be?
– Does your team use Agile Methodology?
– Why Agile, and Why Now?
– A separate test team?
Software ecosystem Critical Criteria:
Accommodate Software ecosystem engagements and reduce Software ecosystem costs.
– What are the long-term Microservices goals?
Software interface Critical Criteria:
Powwow over Software interface results and report on the economics of relationships managing Software interface and constraints.
– How do we go about Securing Microservices?
Software library Critical Criteria:
Discourse Software library decisions and balance specific methods for improving Software library results.
Software testing Critical Criteria:
Recall Software testing issues and create a map for yourself.
– What are internal and external Microservices relations?
Unix philosophy Critical Criteria:
X-ray Unix philosophy risks and get answers.
– Who will provide the final approval of Microservices deliverables?
– Why is Microservices important for you now?
User interface Critical Criteria:
Check User interface projects and inform on and uncover unspoken needs and breakthrough User interface results.
– Is Microservices Realistic, or are you setting yourself up for failure?
– 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:
Systematize Web-oriented architecture outcomes and customize techniques for implementing Web-oriented architecture controls.
– What are the top 3 things at the forefront of our Microservices agendas for the next 3 years?
– Is a Microservices Team Work effort in place?
Web service Critical Criteria:
Be responsible for Web service quality and point out Web service tensions in leadership.
– 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?
– 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?
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:
Project Mosaic—Frontend Microservices
Microservices Architecture Resources | Microservices.com
Azure Service Fabric—Building Microservices | Microsoft Azure
Amazon Standard Identification Number External links:
Amazon Standard Identification Number – Infogalactic: …
Case study External links:
[PDF]Case Study Titles and Descriptions – Feng Shui …
How Do I Cite a Case Study – EasyBib Blog
How to Write a Better Title – a Recipe Book Case Study
Cloud application External links:
HyperCloud DCHQ Cloud Application Platform | Docker …
Morpheus | Cloud Application Management & …
Multi-Cloud Application Delivery Platforms for the Mid …
Communications protocol External links:
Modbus-Simple Communications Protocol
Computer network External links:
15-1152.00 – Computer Network Support Specialists
What is a Computer Network? Webopedia Definition
Continuous delivery External links:
Continuous Delivery (eBook, 2014) [WorldCat.org]
Continuous Delivery – DevOn
Continuous Delivery – CA Technologies
Continuous deployment External links:
Best Continuous Deployment Software in 2017 | G2 Crowd
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:
Where to Start With DevOps: Conway’s Law – IT Revolution
Conway on Conway’s Law – Mel Conway’s Home Page
Cross-cutting concern External links:
What is CROSS-CUTTING CONCERN? What does …
What is Cross-Cutting Concern | IGI Global
Distributed software External links:
[PDF]IBM Distributed Software PT64366 Passport …
Domain-driven design External links:
Domain-Driven Design Fundamentals | Pluralsight
DSL Platform – Domain-Driven Design
Domain-Driven Design Belgium (Brussels, Belgium) | Meetup
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++) | Microsoft Docs
Hewlett Packard Labs External links:
Hewlett Packard Labs | Beyond Bitcoin
Load balancing External links:
Load Balancer | Load Balancing – KEMP Technologies
Traffic Manager – Cloud load balancing | Microsoft Azure
Application Gateway–Load Balancing Solution | Microsoft Azure
Loose coupling External links:
What is loose coupling? – Definition from WhatIs.com
Loose Coupling | cloudcomputingpatterns.github.io
Message format External links:
How to Set the Default Message Format in Outlook
i need help with text message format | Verizon Community
Modular programming External links:
SLC QBASIC Modular Programming Video Tutorial – YouTube
What is modular programming? Where is it used? – Quora
ERIC – Modular Programming of Curricula., Higher …
Monolithic system External links:
[PDF]3 Dimensional Monolithic System on a Chip (3DSoC)
Network latency External links:
What is Network Latency? – Definition from Techopedia
Global IP Network Latency
Large mailbox migrations are slow because of network latency
Network traffic External links:
Intelligent Network Traffic Analysis | GreyCortex
WAN Killer – Network Traffic Generator | SolarWinds
Network Traffic Analyzer – Home
Representational state transfer External links:
Representational State Transfer (REST) – Service Architecture
Self-contained Systems External links:
V-Cube™ Vertical Self-Contained Systems
Vertical Self-contained Systems – Mammoth
Self-Contained Systems | Daikin Applied
Serverless computing External links:
Serverless Computing | 2017-09-18 | Cloud Strategy …
Serverless Computing | Microsoft Azure
Serverless Computing – Amazon Web Services
Shared memory External links:
Software component External links:
User Interface Technology (SAP_UI) is a software component which is available within SAP NetWeaver.
http://No ST-A/PI Software Component exists, Solman 7.1
Implemented software component checks – docs.infor.com
Software deployment External links:
WPKG | Open Source Software Deployment and Distribution
Total Software Deployment – Softinventive.com
Software Deployment Jobs, Employment | Indeed.com
Software development External links:
COAX – Software Development Company
Gordon Darby – Government Software Development
Online Education and Software Development | Smart Horizons
Software ecosystem External links:
What is Software Ecosystem | IGI Global
Software library External links:
Software Library – NeoSmart Technologies
StdLib — Function as a Service Software Library
Software testing External links:
Software Testing and Deployment | Olenick
Independent Software Testing Company QAwerk. …
Scriptless Test Automation Platform | Software Testing Tool
Unix philosophy External links:
Unix Philosophy – theword.store
Unix Philosophy – AbeBooks
The Unix Philosophy | Linux Journal
User interface External links:
Login – Terminal Customer User Interface – Colonial Pipeline
Datatel User Interface 5.3
EWS User Interface
Web-oriented architecture External links:
Web-Oriented Architecture (WOA) – Gartner IT Glossary
Web service External links:
TeletracXMLGateway Web Service
MSU Police Web Service
kumo cloud™ Mobile App and Web Service for HVAC Control