With svcmap.com, you can easily document and visualize how your software components and services map to your teams, infrastructure, processes etc... both now and in the future.
Start Mapping Now
Map your software components beyond just what exists today and capture deprecations and future state including services and components yet to built. With svcmap.com, you can easily map out where you are today, while facilitating discussions about where core concerns, interfaces and teams belong in terms of team ownership, infrastructure or anything else you choose to map.
Components in a service map allow you to capture concerns (or responsibilities), interfaces and dependencies in both current and future states. You choose whether a component represents a service, a team, a process, a piece of infrastructure or anything else you want to map.
With svcmap.com, you can explore these components in terms of layers, tables or graphs. Show as much or as little detail as you need for the audience or task at hand. For example viewing all components by what layer of the architecture they live in, or by what team owns the component or by any other tag you choose to apply.
Conway's law is real, and software built by teams at scale are constantly changing as your organization grows. Mapping your services and components helps identify duplication and ambiguity in your architecture, and helps you plan for growth, both in terms of the what and the who. Use built-in notes and create audience specific views to facilitate discussions between teams and stakeholders.
