Software architecture diagram

Documenting Software Architecture When we need to explain to someone else (new developer, product owner, investor, …) how the application works, we need documentation. But what documentation option…

Microservices are currently getting a lot of attention. This blog post is the first in a 7-part series about designing, building, & deploying microservices.

AWS Architecture Diagrams with powerful drawing tools and numerous predesigned Amazon icons and AWS simple icons is the best for creation the AWS Architecture Diagrams, describing the use of Amazon Web Services or Amazon Cloud Services, their application for development and implementation the systems running on the AWS infrastructure. The multifarious samples give you the good understanding of AWS platform, its structure, services, resources and features, wide opportunities, advantages and…

I have read few articles about Microservices architecture in the blogs, discussions on social media etc. It’s inspired me much to write this post on how an Electronic Single Window system …

Ever wondered how large enterprise scale systems are designed? Before major software development starts, we have to choose a suitable architecture that will provide us with the desired functionality…

Create an Enterprise Architecture Framework Diagram Tutorial Help Page on the Dragon1 Platform. Where to start modeling and visualizing your EA baseline.

Recently there has been substantial discussion around the downsides of service oriented architectures and microservice architectures in particular. While only a few years ago, many people readily adopted microservice architectures due to the numerous benefits they provide such as flexibility in the form of independent deployments, clear ownership, improvements in system stability, and better separation of concerns, in recent years people have begun to decry microservices for their tendency…

Learn how to build a telehealth system, using Azure cloud services, that connects a professional healthcare organization to its remote patients.

Our work with legacy code doesn’t often put us in a position to move quickly into new or trendy tooling. And while we almost always introduce Docker very early in our projects, it is usually only for the purpose of standardizing and easing setup of developer environments. Transitioning a live environment to containers, however, can be a daunting prospect, especially for monolith applications. But, the payoffs can be huge.