![]() ![]() ![]() Ideally, we’d have dozens of architecture diagrams - from various views, from various proposals, from various teams. Some teams and projects will have a diagram and point to it as “here is the architecture” - but it’s not the architecture, it’s just one particular view. It’s not wrong to have a big box representing your backend it’s just one way of viewing an abstraction. That means all architecture diagrams are views into an abstraction. The people focused on backend had the reverse - a huge box just labelled frontend!Īctual relationships do exist between systems (e.g. network calls, shared storage) but an architecture diagram can’t give all details without becoming the code it’s meant to represent. The people focused on frontend had things like Jira, Embedded Marketplace, Commerce, Provisioning, Atlassian Connect, then an arrow to a huge box - just labelled Marketplace backend. When my previous engineering manager joined the Atlassian Marketplace team, he asked everyone to draw an architecture diagram. ![]() Probably the best form of communication is a diagram, with boxes representing systems (or components) and lines representing relationships between them. For the past few years I’ve been the most senior developer on my teams in Atlassian, in both position (Principal Engineer) and time (almost 9 years) - this means I usually take on the responsibility of managing our software architecture.Īrchitecture is the relationships between systems, which can be fairly tricky to talk about. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |