Hexagonal Microservices
Would you like to talk a closer look at establishing the technical architecture of a Microservices platform? Join Vlad Mettler and James Gardner who will share their experiences and how they weighed up the options.
In addition they'll explore the testing strategy for hexagons (acceptance/regression/unit; mocking strategies) and how it fits into the the development process (sequence diagrams, workflows definition, role-play component testing); agile vs waterfallish.
(RESTful HTTP vs RPC, Ports and adapters with strict interfaces (aka hexagonal architecture) vs components vs layers, universal naming vs service isolation, tell don't ask vs chatty, threads vs async, monitoring, logging, caching, authz).
YOU MAY ALSO LIKE:
- Acceptance Criteria driven hexagonal microservices (SkillsCast recorded in February 2016)
- Domain Models in Practice with Marco Heimeshoff (Online Course on 30th November - 4th December 2020)
- Microservices Architecture with Jorge Ortiz‑Fuentes (Online Course on 15th - 17th February 2021)
- The Death of Silos (Online Meetup on 3rd December 2020)
- Practical Property Testing (SkillsCast recorded in November 2020)
- Strategic Domain-Driven Design Tools For Non-DDD People (SkillsCast recorded in October 2020)
Hexagonal Microservices
Vlad Mettler
Vlad Mettler is a Python coder turned team lead, turned technical architect. He has worked for various internet related companies since 1998 using technologies from classic ASP through PHP to Python and Django.
James Gardner
James Gardner is a technical architect. He has worked as an open data consultant and technical lead for the Open Knowledge Foundation working on projects including data.gov.uk. He is also the co-founder of the Pylons web framework which powers sites like reddit.com as well as open data portals all over the world.