ArchifySpec’s Post

Hi, community! Almost everyone heard about low coupling and high cohesion, standard topic in our live, but there is very very very interesting discussion about this topic from Vlad Khononov. Now i'm waiting for his book :) #architecture

When setting architectural standards it's hard to please everyone. But there are some things you can do to reduce the pain and friction. A few that come to mind are: 1. Explicitly define and communicate. Vague or implicit standards can cause unnecessary debates or low adoption. Make it easy for people to easily and quickly identify what standards are applicable to them. 2. Be transparent about how standards were chosen. People might not agree but they are more likely to understand and accept if a standard doesn't seem random. 3. Bake in standards where possible. E.g. provide platform paved-roads that create standard-compliant applications out of the box. Would love to hear any other tips you may have. #softwareArchitecture

Have you ever stared at a tangled mess of code and wished there was a better way?    The secret behind well-structured, adaptable software is its architecture. Just like a building needs a strong foundation, a software system thrives on a clean and well-defined architecture.   Today, we'll be discussing two popular architectural styles: Clean (or Onion) and Layered (or N-Tier). We'll explore their strengths, weaknesses, and help you give some architectural tips for your next project.   Check out our blog : https://lnkd.in/gSmAdsC4 #softwarearchitecture #cleanarchitecture #onionarchitecture #layeredarchitecture #ntierarchitecture #softwaredevelopment  #Newnop

In thinking about the 'lack' of Software Architecture we see in deployed products today, with time, cost, and competitive constraints -- essentially the fierce competition, it brings to mind Claude Shannon's idea of information-as-resolved-uncertainty thinking in the 1940s. Von Neumann was said to have said that 'information reduces 'entropy'. I wonder of viable Software Architecture could be said to reduce 'product-entropy' by a viable and comprehensible architecture that 'realizes' a best-design, thus reducing the project's overall entropic effects.

Colleagues in architecture, engineering and construction, a question for you: 💭 Do you find logo slides helpful when evaluating new software? If so, what is most helpful about them? If not, what would be more helpful? #buying #software #AEC

Why are design and architecture resources never available when you need them most? discipulus provides architecture-as-service for teams that need to work at pace, securely and safely. Describe your use case, highlight any constraints, and let discipulus do the heavy lifting: system diagrams, diagrams-as-code, infrastructure-as-code, code-from-architecture, and costs - all within industry-standard and enterprise guardrails. cc: buildspace Farza Majeed

🎤 Check out mine and John Kiernan's talk at IUG Conference 2024: 'Irish Rail and Bruhati: Managing the EA operating model with Alfabet', now available on-demand. Follow the link in the comments section below to explore on-demand recordings and slide decks from the conference, and click "Join the event" to register your details to gain access or, login if you previously registered your attendance at IUG Conference 2024. #IUG #EnterpriseArchitecture #EA #Alfabet #SoftwareAG #Bruhati

🏛️ Explore the world of architectural styles and patterns! From timeless classics to modern marvels, our cheat sheet is your guide to designing robust software systems. Get your hands on the high-resolution image now! Subscribe to our newsletter and unlock the key to architectural success. Sign up today: [https://lnkd.in/geTfdTaC) #SoftwareArchitecture #BlueprintForSuccess #DownloadNow 🖼️

In a world that marvels at rapid architectural feats—like a hospital springing up in just 10 days—why do software projects, seemingly less bound by physical constraints, frequently spiral over budget and beyond deadlines? you can find some answers in my article(7mn): https://lnkd.in/estEYEe6

This e-book will show you how Composable Architecture can help you future-proof your software, saving you from the frustration of rigid systems that can’t keep up with market demands. 💡 Discover how a modular approach can cut development time and costs by reusing components, allowing your teams to focus on innovation rather than reinventing the wheel. 😉 👉 https://lnkd.in/eNczSYBw