![]() ![]() ![]() I find it very natural to design complex architectures. It is beyond the scope of this tooling article to describe it in depth, but I invite you to have a look at this very pragmatic approach. We use the C4 model to represent our architecture. It gathers data about the company both from a local repository and from another administration IS (Information System), produces a PDF report, and sends an e-mail to the company's original requester. A second one is made of a job launched periodically and consuming new requests.A first call chain is made of the GUI requests that create requests into the system.We can split our feature "Deliver Companies Data" into two main call chains: gov web application enabling any company to get all its information known to all the public administrations. We illustrate this article with a fictional AllMyData microservices application. As we will see later, it's often a collaborative process taking advantage of several great tools. Following a living documentation approach, we adapt and augment diagrams, text, and tables several times a day. Our current project architecture is fairly complex because of the number of modules (tens of jobs, API, and GUI modules), because of the large number of external partners, and because of its integration with a large legacy information system.Īt this time, we have to maintain more than one hundred architecture diagrams. We use this Open Source Template to document our architecture. The security view, which is mainly transversal.The sizing view dealing with performance. ![]() The infrastructure view (middleware, databases, network connections, storage, operations.) provides useful information for integrators and DevOps engineers.The software view (design patterns, database design rules, choice of programming languages, libraries.) that developers should rely upon.The application view dealing with modules and data streams between them (targeting product stakeholders and developers).I'm responsible for designing different architecture views, each targeting very different audiences, hence different preoccupations: I'm lucky enough to currently work on a large microservices-based project as a solution architect. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |