BOK - Recursos de Arquitetura Software

❗️ATTENTION ❗️ Registration to DevTernity is running: 👉 https://devternity.com Ask somebody in the building industry to visually communicate the architecture of a building and you'll be presented with site plans, floor plans, elevation views, cross-section views and detail drawings. In contrast, ask a software developer to communicate the software architecture of a software system using diagrams and you'll likely get a confused mess of boxes and lines. I've asked thousands of software developers to do just this over the past decade and continue to do so today. The results from these software architecture sketching workshops still surprise me, anecdotally suggesting that effective visual communication of software architecture is a skill that's sorely lacking in the software development industry. Of course, as an industry, we do have the Unified Modeling Language (UML), but asking whether this provides an effective way to communicate software architecture is often irrelevant because many teams have already thrown out UML in favour of much simpler boxes and lines diagrams. Abandoning UML is one thing but, perhaps in the race for agility, many software development teams have lost the ability to communicate visually. This talk explores the visual communication of software architecture based upon my experience of working with software development teams across the globe. We'll look at what is commonplace today, the importance of creating a shared vocabulary, diagram notation, the value of creating a model plus how to use tooling and static analysis techniques to automate diagram generation.

This is the recording of the meetup https://www.meetup.com/Munchen-NET-Meetup/events/270440170/ ********************************************* Details ----------------------------------------------------------------------- "One ring to rule them all, one ring to find them, One ring to bring them all, and in the darkness bind them". Entering the microservice architecture has been going on for quite a few years. The false start we've made in IT adopting a distributed system architecture without legitimate architectural drivers hurts many development and maintenance teams to this day. History repeats itself, which is why the infamous "Monoliths" return to favor. Is monolithic architecture really bad? The presentation will discuss Modular Monolith - the younger brother of the monolith, who cares about the good name of monolithic architecture. The main attributes of such a system as modularity will be discussed - how to achieve and enforce them. Moreover, we will talk about architectural drivers - when to stay in monolith architecture and when to split it into separate services. During the session, one of the ways to design a Modular Monolith will be presented, in line with the best practices and design patterns. Bio ------------------------------------------------------------------------- Architect, Team Leader and programmer, associated with .NET technology for over 12 years. A graduate of the Warsaw University of Technology Computer Science with a specialization in Software Engineering. Supporter of the Software Craftsmanship, Agile, automation, Clean Code approach and pragmatic problem solving according to their class. Enthusiast of topics related to software architecture and system design. Enthusiast and practitioner of Domain-Driven Design. The promoter of Modular Monolith architecture and high-quality object-oriented programming. He describes his thoughts and conclusions on his blog https://www.kamilgrzybek.com and Twitter: @kamgrzybek. He works in ITSG Global company, whereas an architect, programmer and consultant is responsible for software development for companies from the financial, medical and Big Data industries. Privately - a husband, father of his beloved daughter, owner of an unruly dog, runner-amateur and enthusiast of self-improvement living according to the Socrates motto - "I know that I know nothing." Agenda ------------------------------------------------------------------------- 17:45 Virtual doors open 18:00 Welcome note and introduction 18:15 Modular Monolith Architecture by Kamil Grzybek 19:15 Q&A 20:30 End of event!

Subscribe to Devoxx on YouTube @ https://bit.ly/devoxx-youtube Like Devoxx on Facebook @ https://www.facebook.com/devoxxcom Follow Devoxx on Twitter @ https://twitter.com/devoxx Microservices are everywhere. Everyone seems to be either going into that direction or is talking about doing so. But are they really the best choice for you? Developers! Architects! Buckle up as we're going to cut through the hype. Instead of going all-in on microservices or all-in on big ball of mud, we'll introduce a third choice: the Majestic Modular Monolith! We'll look at what it brings to the table, when it may be a good fit and how it compares to the other two approaches in terms of code organization, productivity, scalability and much more. We'll look at how this can be designed and implemented in practice. Get ready. We won't shy away from the hard questions. Axel Fontaine From Boxfuse GmbH Axel Fontaine is the founder and CEO of Boxfuse (boxfuse.com), the easiest way to deploy JVM, Node.js and Go applications to AWS, and the creator of Flyway (flywaydb.org), the open-source tool that makes database migrations easy. Axel is an entrepreneur, a Continuous Delivery expert, an Immutable Infrastructure expert, a Java Champion, a JavaOne Rockstar, a regular speaker at many large international conferences, a trainer and an author.

This presentation was recorded at GOTOpia November 2020. #GOTOcon #GOTOpia http://gotopia.eu Simon Brown - Creator of C4 Software Architecture Model & Author of "Software Architecture for Developers" @simonbrown4821 ABSTRACT The software development industry has made huge leaps in recent years, yet software development teams are often more chaotic than they are self-organizing, with the resulting code being more of a mess than was perhaps anticipated. Successful software projects aren't just about good code, and sometimes you need to step away from the IDE for a few moments to see the bigger picture. This aimed at software developers who want to learn more about software architecture, technical leadership and the balance with agility [...] TIMECODES 00:00 Intro 00:25 1. Software architecture isn't about big design upfront 10:24 2. Every software team needs to consider software architecture 12:35 3. The software architecture role is about coding, coaching & collaboration 17:31 4. You don't need to use UML 24:32 5. A good software architecture enables agility Download slides and read the full abstract here: https://gotopia.eu/november-2020/sessions/1635/five-things-every-developer-should-know-about-software-architecture Check out our upcoming masterclasses with Simon Brown here: https://bit.ly/3sBgPEC RECOMMENDED BOOK Simon Brown • Software Architecture for Developers Vol. 2 • https://leanpub.com/visualising-software-architecture https://twitter.com/GOTOcon https://www.linkedin.com/company/goto- https://www.facebook.com/GOTOConferences #SoftwareArchitecture #Architecture #C4Model #Backend #Culture #Agility #AgileSoftwareDevelopment Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket at https://gotopia.tech SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily. https://www.youtube.com/user/GotoConferences/?sub_confirmation=1

This video presents how to build software architecture diagrams using C4 model and Structurizr tool. Helpful links: Structurizr tool: https://structurizr.com/ C4 Model: https://c4model.com/ Software Architecture for Developers: https://softwarearchitecturefordevelopers.com/

In Simon Brown's talk at AOTB 2019 he explores the visual communication of software architecture based upon a decade of Simon’s experiences working with software development teams large and small across the globe. He looks at what is commonplace today, the importance of creating a shared vocabulary, diagram notation, and the value of creating a lightweight model to describe your software system using the “C4 model”, which he created as a way to help software development teams describe and communicate software architecture, both during up-front design sessions and when retrospectively documenting an existing codebase. It’s very likely that the majority of the software architecture diagrams you’ve seen are a confused mess of boxes and lines. Following the publication of the Manifesto for Agile Software Development in 2001, teams have abandoned UML, discarded the concept of modelling and instead place a heavy reliance on conversations centered around incoherent whiteboard diagrams or shallow “Marketecture” diagrams created with Visio. Moving fast and being Agile requires good communication, yet software development teams struggle with this fundamental skill. A good set of software architecture diagrams are priceless for aligning a team around a shared vision and for getting new-joiners productive fast. Visit www.agileonthebeach.com for more information about the premier annual Agile conference. BIOGRAPHY Simon is an independent consultant specialising in software architecture, and the author of “Software Architecture for Developers” (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He is also the creator of the C4 software architecture model, which is a simple approach for creating maps of your code. Simon is a regular speaker at international software development conferences, travelling the world to help organisations visualise and document their software architecture.

DevDay (http://devday.pl) 26th of September 2014 Simon Brown - "Software Architecture vs Code" "Software architecture and coding are often seen as mutually exclusive disciplines, despite us referring to higher level abstractions when we talk about our software. You've probably heard others on your team talking about components, services and layers rather than objects when they're having discussions. Take a look at the codebase though. Can you clearly see these abstractions or does the code reflect some other structure? If so, why is there no clear mapping between the architecture and the code? Why do those architecture diagrams that you have on the wall say one thing whereas your code says another? In fact, why is it so hard to automatically generate a decent architecture diagram from an existing codebase? Join us to explore this topic further."

This interview was recorded for the GOTO Book Club. #GOTOcon #GOTOBookClub http://gotopia.tech/bookclub Simon Brown - Author of "Software Architecture for Developers Vol. 2" @simonbrown4821 Stefan Tilkov - Co-founder & Principal Consultant at INNOQ @stefantilkov8355 PART 1: https://youtu.be/TE4rKZ7M1aM DESCRIPTION Software architecture concepts will help software developers not only advance their careers but also do a better job in their current work. Simon Brown, the creator of the C4Model talks to Stefan Tilkov about why software architecture is something that every developer should understand, how the C4 Model can help with that and why diagrams are so useful in software development. The interview is based on Simon's book "Software Architecture for Developers Vol. 2": https://leanpub.com/visualising-software-architecture TIMECODES 00:00 Intro 00:48 The C4 model 06:26 The difference between UMLs & the C4 model 11:11 Should UMLs be part of a CS education? 15:29 How to keep diagrams in sync with your code? 20:24 How to visualize software diagrams & documentation? 25:39 Resources for developers getting into architectural work 27:06 Outro Read the full transcription of the interview here: https://gotopia.tech/bookclub/episodes/software-architecture-for-developers-c4-model Check out our upcoming masterclasses with Simon Brown here: https://bit.ly/3sBgPEC RECOMMENDED BOOKS Simon Brown • Software Architecture for Developers Vol. 2 • https://leanpub.com/visualising-software-architecture Mark Richards & Neal Ford • Fundamentals of Software Architecture • https://amzn.to/3qmELt7 Gregor Hohpe • The Software Architect Elevator • https://amzn.to/3tY8evH Michael Keeling • Design It! • https://amzn.to/37y4OGH George Fairbanks • Just Enough Software Architecture • https://amzn.to/3bbjqg3 Nick Rozanski & Eoin Woods • Software Systems Architecture • https://amzn.to/3ajYjsv Peter Coad, Eric Lefebvre & Jeff de Luca • Java Modeling In Color With UML • https://amzn.to/3bVDTHd Eric Evans • Domain-Driven Design • https://amzn.to/3tnGhwm Grady Booch, James Rumbaugh & Ivar Jacobson • The Unified Modeling Language Reference Manual • https://amzn.to/2OA1Qv1 Nick Tune & Jean-Georges Perrin • Architecture Modernization • https://amzn.to/4b5ASiN https://twitter.com/GOTOcon https://www.linkedin.com/company/goto- https://www.facebook.com/GOTOConferences #SoftwareArchitecture #C4Model #SimonBrown #StefanTilkov #AgileManifesto #Structurizr #INNOQ #SoftwareArchitect #Programming #Design #UML #Diagrams SUPPORTER This episode of the GOTO Book Club was made possible thanks to the support of GOTOpia.tech. Created for developers, by developers, the GOTO event series goes beyond annual conferences held in Chicago, Amsterdam and Copenhagen: you can also join online conferences, online masterclasses and meetups with top creators and leaders in tech year-round. And if joining one of these top-rated events isn't enough to satisfy your hunger for the latest in tech, you can watch over a thousand high-quality talks on the GOTO YouTube channel — subscribe now for new videos released (almost) daily and join GOTO in person or online at any upcoming conferences using the promo code ‘bookclub’. http://gotopia.tech Looking for a unique learning experience? Attend the next GOTO conference near you! Get your ticket at https://gotopia.tech SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily. https://www.youtube.com/user/GotoConferences/?sub_confirmation=1