GSAS will start in

days
hours
Minutes
seconds

About the event

GSAS (Global Software Architecture Summit) is a one day summit which aims to attract and connect software architecture experts from all over the world as well as all those interested in building working software to improve their skills, share knowledge, and connect.

Robust and scalable software is in the center of every discussion and talk, which makes it a perfect place for people who fight for quality in the software development world.

Over 300 software architects will come together for one day to promote quality in the world of software.

In addition to technical talks, panel discussions and debates, it will be fun! There will be snacks and beers, opportunity to meet like-minded people and generate interesting discussions.

Your demographics doesn't matter, what really matters is your passion for useful, well designed, maintainable and scalable software.

Come, we will be happy to see you there!

Mission

To write and sign the leading software architecture manifesto for the next generation of developers and software architects in 4 years.

To grow the software architecture community, focusing on best practices, innovation, working software and practical solutions for current issues.

Values

We all share the same values that are the foundation of everything we do:

  • Working software over number of features
  • A hunger for continuous learning & improvement over repetitive standards
  • Community benefit over individualism

Our Speakers

Ian Gorton

Author of the book "Essential Software Architecture"

George Fairbanks

Author of the book "Just Enough Software Architecture: A Risk-Driven Approach"

Mark Richards

Author of "Software Architecture Fundamentals" (O’Reilly video) and "97 Things Every Software Architect Should Know"

Len Bass

Author of the book "Software Architecture in Practice"

Ana-Maria Mihalceanu

Co-Founder of "Bucharest Software Craftsmanship Community"

Sandro Mancuso

Author of the book "The Software Craftsman: Professionalism, Pragmatism, Pride"

Eoin Woods

Co-author of the book "Software Systems Architecture"

Michael Feathers

Author of the book "Working Effectively with Legacy Code"

David Farley

Author of the book "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation"

Juan Manuel Serrano

Co-founder of Habla Computing

Álvaro García

Principal Engineer at Apiumhub

Alex Soto

Co-Author of the book "Testing Java Microservices"

Viktor Farcic

Author of "The DevOps Toolkit" series and "Test-Driven Java Development"

Christian Ciceri

Software Architect at Apiumhub

Cristian Cotes

CTO at MusicList

Carlos Blé

Author of "Diseño Ágil con TDD", the first TDD book written in Spanish

Jakub Marchwicki

Principal Engineer at Casumo

Event Schedule

08.30 - 09:30

Registration

09.30 - 09:45

Opening Ceremony by Apiumhub

09.45 - 09:50

Inspirational talk by Gold Sponsor

09.50 - 10:30

Code is your partner in thought

George Fairbanks

We used to build software like bridges. There was time for careful collection of requirements and the analysis of design options. But we don’t do that anymore, in part because the time we spent did not ensure we hit our targets or avoided risks. Today, most companies use some form of continuous design where the software changes in small steps, often weekly or even daily, which makes those companies responsive to environmental changes. The problem is that in just a few years the software becomes over-complicated and usually needs to be rewritten, even when the team refactors. The longer you let the team code, the worse the code gets. That’s a shame because other kinds of engineering don’t have this problem. Car engines, for example, improve every year. I’ll primarily discuss some ideas about why things work out this way and also some promising ideas for how we can practice continuous design longer, if not forever.

10.30 - 11:15

Applying architectural principles, processes, and tools

Len Bass

My position is that an architect needs a good understanding of five things:

  1. The environment in which their system is intended to run. For cloud based systems this is an understanding of distributed system principles, virtualization, networking, containerization, failure in the cloud, and security.
  2. Architectural design principles. These are: quality attribute requirements drive design choices, business goals lead to quality attribute requirements, and design choices are constrained by the environment and by business considerations.
  3. Processes to make the design principles concrete. Translating an architectural design principle into a design repeatedly requires a process. Knowing that quality attributes drive design does not get you a design but a series of questions: what are the important quality attribute requirements, what are the options for realizing those requirements, and what are the trade offs among the requirements that result from these options?
  4. Architectural styles. Systems are not derived from first principles. Knowing the strengths and weaknesses of various architectural styles allows the designer to take advantage of the experiences of the field.
  5. The tools to be used in the development, deployment, and forensic processes. Current tool suites have the side effect of deskilling software engineers. Software architects must understand the tool suite and their characteristics.
11:15 - 11:35

Coffee break

11:35 - 12:35

Software architecture evolution, what to expect? Panel Discussion

Álvaro García, Eoin Woods, Michael Feathers, Ian Gorton

Debate moderated by Ávaro García. Some of the topics and questions we want to tackle during this panel discussion are:

  • Silver Bullets: What are they? Have we seen one in the past 10-15 years? Do you expect to see one?
  • Many good ideas that seem to be good on paper, but turn out to be the opposite. How to detect them early on?
  • Are we trending towards more common principles? More specialized?
  • Is architecture becoming more specific or more generalized? Is it really evolving? How to make this evolution happen?
  • What kind of evolution are we seeing here? Natural selection or Human selection?
12.30 - 13:30

Reactive Architecture Patterns Debate

Jakub Marchwicki, David Farley, Mark Richards, Len Bass, Christian Ciceri

Debate moderated by Jakub Marchwicki. Some of the topics and questions we want to tackle during this debate are:

  • What is "reactive architecture"? Why is it so important today, yet not as widely applied despite being so adamantly advocated by software architects?
  • What are its benefits? And tradeoffs?
  • What are some of its core patterns? What are the consequences of some of these patterns? Are there cases where they shouldn't be used?
  • What are the differences between reactive architecture and reactive programming?
13.30 - 15:00

Lunch

15.00 - 15:40

Architectural Thinking

Mark Richards

Many technologists have an architect title, take on the role of an architect, or even aspire to be an architect, but are they thinking like an architect? Architectural thinking is learning to look at a problem or task from an architect's point of view. In this talk I discuss how to think like an architect - how to understand, recognize, and analyze tradeoffs, how to think in terms of business drivers, and how important technical breadth is to architectural thinking.

15.45 - 16:45

Effective Architecture Practices Debate

Álvaro García, Sandro Mancuso, George Fairbanks, Juan Manuel Serrano, Carlos Blé, Eoin Woods

Debate moderated by Álvaro García. Some of the topics and questions we want to tackle during this debate are:

  • Effectiveness vs Efficiency
  • How to measure the effectiveness & efficiency of certain practices? How can we generate our KPIs? How can we measure waste?
  • Comparison between the Architecture Tradeoff Analysis Method (ATAM) and the Scenario Based Analysis Method
  • Evolution of a software architecture
16.45 - 17:00

Coffe break

17.00 - 17:40

Data-Driven Scalability and Cost Analysis for Evolutionary Architecture In the Cloud

Ian Gorton

An advantage of evolutionary architectures is their facilitation of experimentation and data-driven development. This becomes especially important for cloud-deployed applications as they scale to meet greater loads, while continually balancing costs. Commercial clouds offer a myriad of powerful, competing services that can facilitate scalability through incremental change. However, the performance and scalability characteristics of these services are a priori unknown. They require careful evaluation and testing to ensure they deliver the required quality of service within application budgets. In this talk, we’ll describe the results from a set of experiments on cloud-based micro-benchmarks that explicitly compare cloud services behavior under experimental conditions. The results show how variability in microservice programming language, database platform, database model and runtime configuration settings dramatically effect scalability and associated costs. The results from these experiments can help architects reason about the effects of their architectural decisions and cloud services selections and configurations. We’ll conclude by discussing the implications of this work for evolutionary architecture, and our progress on publishing these results online for architects to access and utilize.

17.45 - 18:45

Choosing the Right Architecture Style Debate

Alex Soto, Viktor Farcic, Ana-Maria Mihalceanu, Cristian Cotes

Some of the topics and questions we want to tackle during this debate are:

  • What is an Architecture Style?
  • Quality Attribute: Relation between Quality Attributes and Architectural Style
  • In the same way that we have the threat modeling environment, how do we move this to our arch environment?
  • The Second System Syndrome
18.50 - 19:30

Closing Ceremony

19.30 - 20:00

Beers & Snacks

VENUE

Hotel Alimara

The event will take place at Hotel Alimara. If you want to spend the night there, we have special discounts for all GSAS attendees! Contact us and we'll give you all the information!

Images:

Location

Hotel Alimara is easily accessible by public transport, just 5 minutes from bus and metro stations.

  • 20 Min. Car/Taxi ride from the Airport
  • Bus: V21-27-60-73-76-B16-B19-N4
  • Metro: Mundet-L3 (Green)

Ticket Pricing

Right now we have Last Minute Birds Tickets available for 465€ (VAT included). Be aware that they'll only be available until September 30th. All tickets are subject to our Payment, Cancellation and Substitution Policies, so make sure you read them before buying yours. If you're still in doubt or want to ask us something, contact us and we'll gladly answer all your questions!

CALL FOR SPONSORS

Are you a technology company? Interested in meeting software architecture influencers from all over the world? This is a great opportunity to participate in a Global Software Architecture Summit and to support the software architecture community.

Immerse yourself in software architecture!