We started the workshop with a brainstorm of potential topics. Here is the full list (in no particular order) for topics the group came up with. Some of these topics were consolidated due to similarity. Four of these broader, consolidated topic areas were discussed during the breakout sessions using these brainstormed ideas as seeds for the discussion.
- API Design
- Guidelines vs. Standards vs. Culture
- How to grow an organization
- Service discovery
- Redundancy
- Management of services
- Governance
- Testing - scenarios, units
- Legacy micro systems
- Large data sets, chatty services
- Big data
- how big, how small?
- How is team size related?
- Conway's Law
- Are microservices sticky? Will they still be cool next year? In 5 years?
- Single responsibility
- Versioning
- Dependencies
- Cloud intertwined? PAAS
- How do we classify microservices?
- What Quality attributes are promoted?
- Microservices own their own data vs single shard database
- What is a microservice
- Agility to the next level - are microservices required for this?
- Business drivers, value proposition, ROI
- Automated deployment
- Relationships to DevOps
- What is the killer App
- Conversations between services
- Beyond microservices - what might be next?
- Democratic / emergent vs. command and control
- composition and economy API
- Mash-Ups
- CQRS - command query response separation
- Understanding / Enforcing systemic properties
- Security
- Stereotypes for services - characterizations (e.g. controller, translator, authorizer)
- Beyond bounded context
- Internet of things -- requires / implies microservices?
- big lessons from the past that should not be repeated
- REST
- Synch vs. Asynch communication
- Statefull vs. stateless
- Eventual consistency of data
- polyglot architectures
- what are the boundaries / limits of microservices? Where does it fit in?
- visualizing and understanding the design
- domain modeling
- What skills required?
- Anti-patterns 50 Applicable domains
- How sophisticated / disciplined must a team be? Is there a microservices fluency?
- Logic in the endpoints
- Symatic translation
- All we have ard Bad examples -- moving from model to implementation
- Bad domain examples -- e.g "customer", "loan", ...