The presentation by Ned Bauerle discusses the considerations and decisions necessary for planning microservices and a service-based architecture, focusing on aspects such as service size, deployment frequency, and testing strategies. Key topics include roles, packaging, hosting environments, service classification, and monitoring practices for successful implementation. The document emphasizes the importance of a cohesive team and the use of innovative technologies in delivering effective solutions.

1. “MICRODEPLOYMENTS”
FOR
MICROSERVICES
Presented by Ned Bauerle
ned.bauerle@leadingedje.com
http://www.leadingedje.com

2. Topics
⬜ Introduction
⬜ Microservices
⬜ DevOps Decision Roadmap
When planning for microservices or another service-
based architecture it is important to determine the
size of the the services and the frequency of the
deployments. In this presentation we will discuss
some of the devops decisions that need to be made in
order to make the project a success.

3. Ned Bauerle
Director of Technology
Email: ned.bauerle@leadingedje.com
Twitter:
@NedBauerle
In my career I have worked for Leading EDJE,
Resource Interactive, America Online, and
CompuServe.
For over 21 years I have delivered successful
architectural solutions and implementations
for clients including: Crown Equipment,
Chemical Abstracts, Sherwin Williams, Coca-
Cola, Hewlett Packard, Home Depot, America
Online, Netscape, CompuServe, CNN, and
others.

5. UI
Shipping Billing
Inventory Database
Layered Application
(Monolith)
UI
BillingInventory
DatabaseDatabase Database
Shipping
Service-based Application
(Microservices)

6. AIM
SMALL
MISS
SMALL

7. Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope

8. Using a Cloud Environment and managed
services?
Where will the services be hosted?
• On premises
• Hybrid cloud environment
• Which Cloud Hosting Provider
Considerations:
• Cost
• Team Capability
• Business Restrictions
• Existing Infrastructure
• Data Restrictions
Roles:
• Product Owner
• Architects
• Operations
Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope

9. How will services be classified?
Feature, Data, Function, Use Case, etc.
How fine grained will the services be
broken down?
How will services communicate?
How will relational data be handled?
How will state be maintained?
Considerations:
• Versioning (and Lifespan)
• Service Cohesion
• User Management
• Scalability
Roles:
• Architects
• Developers
• Business Analyst
Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope

10. How will services be packaged and
delivered?
How frequent will deployments occur?
Roles:
• Operations
• Architects
• Developers
Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope
Considerations:
• Code Repositories
• Continuous Integration Systems
• Container Image Repositories
• Container Management

11. What types of testing is needed?
• End to end
• Component testing
• Service API testing
• Infrastructure
What testing can be automated?
Roles:
• Business Analyst
• Developer-QA
• Developer
• Architects
• Operations
Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope
Considerations:
• Testing Frameworks
• Team Capabilities

12. How will the application and services be
deployed?
• Blue / Green
• Feature Toggles / Flags (Dark Features)
What gates (approvals) are needed?
• Automatic or Manual
Is Continuous Deployment an option?
Roles:
• Architects
• Developers
• Operations
• Developer-QA
Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope
Considerations:
• Environments (Dev, Test, Prod)
• Testing Gates
• Continuous Delivery vs
Continuous Deployment
• Infrastructure as Code

13. What can be used to monitor:
• Individual services
• Application integrations
• System Health
How will we trace user requests across
services?
How will we aggregate and correlate logs
from the various services?
Roles:
• Architects
• Operations
• Developer-QA
Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope
Considerations:
• 3rd Party Tools
• Data Cleansing
• Shared access to see app statistics
with developers

14. How resilient will the system be?
• Self Healing
• Auto Scaling
Roles:
• Architects
• Operations
• Developers
Packaging Testing Deployment Monitoring Feedback
Hosting
Environment
Scope
Considerations:
• Reactive Frameworks
• Thresholds for alerts

15. Customer UI
BillingInventory
DatabaseDatabase Database
Shipping
Service-based Application
(Microservices)
Database
Users
Point of
Sale
Database
Mobile Sales UI

16. THANK YOU !
Email:
ned.bauerle@leadingedje.com
Twitter:
@NedBauerle
At Leading EDJE, solving business problems
by creating innovative custom solutions
using leading edge technologies is our
sweet spot! We are a WBE certified
consulting firm with a fun forward culture
while promoting high positive energy and
an entrepreneurial spirit. We are made of
exceptionally talented individuals who
deliver exceptional results all while
exercising our core values to the fullest.