Evolutionary Architecture at Work

•

14 gostaram•3,769 visualizações

Phil Calçado

Tecnologia

Evolutionary
Architecture at Work
phil calçado
@pcalcado
http://philcalcado.com
Monday, April 22, 13

2011: Phil decides
to move to Berlin
Monday, April 22, 13

~ 180 million users / month
> 10 hours of audio
uploaded every minute
Monday, April 22, 13

Organisation challenges
Monday, April 22, 13

SoundCloud was
born on Rails
It allowed us to iterate real
fast and keep
code quality up(-ish).
Monday, April 22, 13

Controller
ActiveRecord
Model
Database
Rails is simple.
Monday, April 22, 13

Controller
ActiveRecord
Model
Database
Rails is simple.
But it leads you to
monoliths
SoundCloud
.com
Monday, April 22, 13

Conway’s Law kicks in
Monolithic applications
lead to monolithic teams
Controller
ActiveRecord
Model
Database
SoundCloud
.com
?
Monday, April 22, 13

Big teams == overhead
Who is doing what?
Monday, April 22, 13

Big teams == overhead
Stand-ups become the
main communication
channel
Monday, April 22, 13

Big teams == overhead
Massive backlog requires
constant grooming and
management
Monday, April 22, 13

Big teams == overhead
In the end you’ll need a full
time “Iteration Manager”
Monday, April 22, 13

technical challenges
Monday, April 22, 13

There is one system
SoundCloud
.com
Monday, April 22, 13

There is one system
not really.
Sounds
& Sets
Social
Graph
Premium
Features Search
Activity
Stream
...
Monday, April 22, 13

Multiple subsystems
Ruby/Rails are a horrible
Golden Hammers
Monday, April 22, 13

Multiple subsystems
The stability of the system
is pretty much the same
as the less stable
subsystem’s
Monday, April 22, 13

Controller
ActiveRecord
Model
Database
SoundCloud
.com
?
Monday, April 22, 13

Sounds
& Sets Social
Graph?
Premium
Features
Monday, April 22, 13

How?
Have an enterprise
Architect?
Monday, April 22, 13

How?
Create an architecture
Steering Group?
Monday, April 22, 13

What about
Everyone is an architect?
Monday, April 22, 13

Step 1)
Stabilise the legacy app
Monday, April 22, 13

Idiomatic Rails is funny
Monday, April 22, 13

Understanding the
Rails mindset:
http://bit.ly/not-a-virtue
Monday, April 22, 13

Understanding the
Rails mindset:
i do not think it means
what you think it
means
http://bit.ly/not-a-virtue
Monday, April 22, 13

Stopgap Solution
(A lot like java circa 2005)
Monday, April 22, 13

Step 2)
Create a common protocol
Monday, April 22, 13

Sounds
& Sets
Social
Graph
Premium
Features Search
Activity
Stream
...
Monday, April 22, 13

Sounds
& Sets
Social
Graph
Premium
Features Search
Activity
Stream
...
Ruby Clojure
Go Haskell
Scala
Ruby
Monday, April 22, 13

We want to try things
before making a call
Monday, April 22, 13

Don’t publish rules,
publish guidelines
Monday, April 22, 13

Step 3)
Minimise non-technical
overhead
Monday, April 22, 13

Step 4)
Minimise technical
overhead
Monday, April 22, 13

Pushing a micro-service to
production should be easy
Monday, April 22, 13

People solving the same
problems over and over
Monday, April 22, 13

(with the same code...)
Monday, April 22, 13

About 6 application teams,
3 engineers + 1 product
person
Monday, April 22, 13

Micro-services in Clojure,
Scala and (J)Ruby
Monday, April 22, 13

Pull Request lead time
reduced from 3 to 1 week
Monday, April 22, 13

Still afraid of deleting
old code
Monday, April 22, 13

We have “black hole”
teams
Monday, April 22, 13

There is a lot of
infrastructure to build
Monday, April 22, 13

Step 1)
Stabilise the legacy app
Don’t stop the world, but
don’t let the code base
deteriorate even more
Monday, April 22, 13

Step 2)
Create a common protocol
Guidelines and examples,
not rules
Monday, April 22, 13

Minimise non-technical
overhead
Small teams
don’t need... a lot
Monday, April 22, 13

Step 4)
Minimise technical
overhead
Only try to
re-use after you use
Monday, April 22, 13

phil calçado
http://philcalcado.com
@pcalcado
www.soundcloud.com
Monday, April 22, 13

Mais conteúdo relacionado

Destaque

Structuring apps in Scala

Phil Calçado

CSS 4 - What's coming up

Diego Eis

Os cuidados e os limites do Responsive Web Design

Diego Eis

SoundCloud's web and mobile properties are all built on top of our Public API. While building the user-interface atop a RESTful layer has proven itself a sound decision, the one-size-fits-all nature of a Public API is not ideal. When it comes to data transfer and HTTP resource modelling, each client has their own needs, and in the end hacks and workarounds have to be implemented in both clients and servers. Feature development also becomes complicated, with coordination between multiple teams required for every single little feature. SoundCloud is now moving to a different model, where clients have their own façade APIs, modelled after their core characteristics and needs. We are also using the architecture to break away from Conway’s Law and building more cross-functional, end-to-end teams. From: http://gotocon.com/berlin-2013/presentation/APIs:%20The%20Problems%20with%20Eating%20your%20Own%20Dog%20food To implement this, a lot of change in our architecture, tech stack and development processes were required. In this talk we will explore the challenges we had, the options we investigated and how ultimately SoundCloud decided to move forward.

APIs: The Problems with Eating your Own Dog Food

Phil Calçado

Cloud Reliability Patterns

rafaelferreira

Desafio dos testes em uma arquitetura de micro serviços

Frederico Augusto Do Carmo Moreira

Microservices - Quebrando gigantes em pequenos

Vinícius Krolow

A arquitetura de micro-serviços é fundamentada na explosão de uma aplicação grande e monolítica em um conjunto de APIs e componentes muito pequenos, com baixíssima capacidade funcional, visando independência e autonomia dessas pequenas partes. Nessa palestra vamos explorar alguns casos de uso desse estilo arquitetural, as motivações para a utilização da arquitetura de micro-serviços, comparando-a com as abordagens tradicionais de SOA e arquiteturas monolíticas. Veremos também quais os benefícios e desafios na composição das equipes de projetos, na comunicação entre os serviços e no gerenciamento dos dados. Apresentação realizada em 2014 no QCon Rio.

Vida longa para SOA com microservices

Fábio Rosato

Amadurecendo Equipes com Microservices

sanchez_ivan

A Brief Talk On High-Performing Organisations

Phil Calçado

Um pequeno estudo sobre a microsoft

Diego Eis

Integração utilizando REST API e Microservices

Denis Santos

Flexbox and Grid Layout: How you will structure layouts tomorrow.

Diego Eis

DOM, CSSOM e RenderThree - Introdução ao Browser Render Path

Diego Eis

Microservices

Diego Pacheco

Introdução à Microservices

André Faria Gomes

Workshop soa, microservices e devops

Diego Pacheco

Microservices é um estilo arquitetural que têm revolucionado o desenvolvimento de aplicações através de pequenos serviços, desacoplados e com foco em executar uma tarefa específica comunicando-se através de Web APis ou mensagens assíncronas. Nesta palestra será apresentado como microservices é capaz de solucionar seus problemas no desenvolvimento de sistemas robustos e escaláveis. Serão abordadas as principais características deste paradigma, quais as vantagens e desvantagens em comparação a arquiteturas monolíticas, exemplos e situações de uso.

Microservices: uma abordagem para arquitetura de aplicações (Devcamp 2015)

Tiago Marchetti Dolphine

O que você precisa saber para se tornar um dev front-end

Diego Eis

Destaque (19)

Structuring apps in Scala

CSS 4 - What's coming up

Os cuidados e os limites do Responsive Web Design

APIs: The Problems with Eating your Own Dog Food

Cloud Reliability Patterns

Desafio dos testes em uma arquitetura de micro serviços

Microservices - Quebrando gigantes em pequenos

Vida longa para SOA com microservices

Amadurecendo Equipes com Microservices

A Brief Talk On High-Performing Organisations

Um pequeno estudo sobre a microsoft

Integração utilizando REST API e Microservices

Flexbox and Grid Layout: How you will structure layouts tomorrow.

DOM, CSSOM e RenderThree - Introdução ao Browser Render Path

Microservices

Introdução à Microservices

Workshop soa, microservices e devops

Microservices: uma abordagem para arquitetura de aplicações (Devcamp 2015)

O que você precisa saber para se tornar um dev front-end

Semelhante a Evolutionary Architecture at Work

Video and slides synchronized, mp3 and slide download available at http://bit.ly/1cghaiX. Mat Wall describes some of the tools & techniques that are used within the UK Government Digital Service to try and make the government behave less like an enterprise and more like a startup.Filmed at qconlondon.com. Mat Wall is a technical architect who can still actually make things and now works for the Cabinet Office, a rare thing indeed. Mat works on elements of the GOV.UK website, as well as working within departments on transactional services. Twitter: @matwall

Green Shoots in the Brownest Field: Being a Startup in Government

C4Media

Implementing AutoComplete for Freemarker and Velocity languages in ACE Editor

peychevi

StackEngine Demo - Docker Austin

Boyd Hemphill

*Source - towards the semantic annotation of digital content / Wittgenstein S...

Alessio Piccioli

Evolving Operational Maturity in a Startup Environment

Adrian Spender

Desenvolvedores são os novos donos do jogo

Eduardo Rabelo

Molly Holzschlag - FOWD London 2009

Carsonified Team

Drupal, rotative numérique pour un groupe de presse

Audaxis

Drupal - Digital publishing platform for Press & Media group

Eric Fesler

Introduction to Drupal 7

Gerald Villorente

StackEngine has talked to over 100 businesses about the direction and needs of companies ranging from start ups still in Stealth mode to the Fortune 100. Combine these learnings with the features currently included in the StackEngine Controller and a solution to production operation begins to come to light. To think about a production operation we: * Establish the characteristics of an ideal containerized application. * Motivate those characteristics in terms of business benefit. * Discuss the "final mile" problem of taking a containerized service and making it available to the operations team. * Now that containers are running, how do we inventory what we have and the state that it is in? * Demo Host, Container and Search pages as a means of inventory management. * When our monitoring tells us something is wrong on a host, what do we do? * How do services find each other? * Discuss how StackEngine will provide service discovery. * Provide a roadmap overview

StackEngine Demo - Boston

Boyd Hemphill

การทำซอฟท์แวร์ภายใน 30 วัน

ทวิร พานิชสมบัติ

W/BO project - Wi-Fi over AIBO

guestf7f4e8

Google Developer Day 2007 - Nestoria: From Mash-up To Business

lokku

Understanding and building Your Own Docker

Motiejus Jakštys

Drupal 8 for site builders

swentel

Thegraphrevolution

Rickard Öberg

MySQL Software Repositories

Akhil Mohan

From HTML5 to Hardware - Simonyi Conference Budapest April 15

Jan Jongboom

OSDC - Open and Accessible

Christian Heilmann

Semelhante a Evolutionary Architecture at Work (20)

Green Shoots in the Brownest Field: Being a Startup in Government

Implementing AutoComplete for Freemarker and Velocity languages in ACE Editor

StackEngine Demo - Docker Austin

*Source - towards the semantic annotation of digital content / Wittgenstein S...

Evolving Operational Maturity in a Startup Environment

Desenvolvedores são os novos donos do jogo

Molly Holzschlag - FOWD London 2009

Drupal, rotative numérique pour un groupe de presse

Drupal - Digital publishing platform for Press & Media group

Introduction to Drupal 7

StackEngine Demo - Boston

การทำซอฟท์แวร์ภายใน 30 วัน

W/BO project - Wi-Fi over AIBO

Google Developer Day 2007 - Nestoria: From Mash-up To Business

Understanding and building Your Own Docker

Drupal 8 for site builders

Thegraphrevolution

MySQL Software Repositories

From HTML5 to Hardware - Simonyi Conference Budapest April 15

OSDC - Open and Accessible

Mais de Phil Calçado

PicPay is the largest digital wallet in Latin America. We offer peer-to-peer payments, BNPL, credit cards, personal loans, insurance, investing, trading, and other financial products to 60 million people and 5 million merchants, processing over $20 billion yearly. But just three years ago, in 2019, PicPay was 30 engineers in a small office working on a single product for a few million users. Growing our product portfolio, team size, and the number of transactions by several orders of magnitude so quickly was as chaotic as you might imagine—but we've done it! Our approach gave teams and engineers radical autonomy to choose the best tool, process, and technology for their area. This strategy was invaluable in handling hypergrowth, but as we stabilize as a business and product, we have realized that what took us here isn't what will keep us moving forward. In this talk, let's explore the consequences of how we dealt with our hypergrowth phase and what are the changes and initiatives we have put in place to make sure that we keep growing and pushing the envelope—but at a manageable pace this time around. Phil Calçado is the Global CTO at PicPay. Before PicPay, Phil was Senior Director of Engineering at SeatGeek, leading the team that built the live events platform used by 44 million people worldwide. He has also led the platform team at Meetup/WeWork, worked on Linkerd - the pioneering Service Mesh, and headed product engineering for DigitalOcean and SoundCloud, both pioneers in adopting Microservices architectures. https://plus.qconferences.com/plus2022/presentation/afterparty-refactoring-after-100x-hypergrowth

the afterparty: refactoring after 100x hypergrowth

Phil Calçado

Presented at LeadingEng New York 2022 (https://leaddev.com/leadingeng-new-york/video/dont-try-home-how-practice-self-improvement-senior-leader) -- Most of us have developed our expertise as engineers through a mix of literature and experimentation. The software industry moves at a higher speed than others because we can try and study complex, real-world systems in the comfort of our bedrooms and personal Github accounts. When you become a leader, especially one who leads other leaders, things get a little more complicated. There are books, but they tend to contain generic advice. There are patterns, but the nature of the job makes it harder to identify when and how to apply them. In this session, I want to walk through a few things that have worked for me when you don't have a lab to try things out. Let's explore processes, tools, and resources to continuously improve your skills and expertise when there is no StackOverflow and no coding dojos. Phil Calçado is Global CTO at PicPay, the largest digital wallet in Latin America. He leads a team of more than 1,500 engineers building financial products for 60 million users and processing over four billion dollars yearly. Before PicPay, Phil was Senior Director of Engineering at SeatGeek, where he led the team that built the live events platform used by 44 million people worldwide. He also has led the platform team at Meetup/WeWork, worked on Linkerd - the pioneering Service Mesh, and headed product engineering for DigitalOcean and SoundCloud, both pioneers in the adoption of Microservices architectures.

don't try this at home: self-improvement as a senior leader

Phil Calçado

The Economics of Microservices (redux)

Phil Calçado

From microservices to serverless - Chicago CTO Summit 2019

Phil Calçado

For the last ten years or so, many companies have focused on migrating from larger, monolithic systems and applications towards a specific style of Service-Oriented Architecture called Microservices. The promise was that these smaller, loosely-coupled, and independently developed components would increase productivity and safety for organizations, as large and complex business challenges can be broken down into smaller and simpler components. However, even before most organizations were able to fully migrate to this new architecture and enjoy its promised benefits, a new iteration of cloud computing has been made available in the shape of Serverless platforms such as AWS Lambda, and Google Cloud and Microsoft Azure Functions. Now lots of companies found themselves conflicted between abandoning their traditional microservices approach towards Serverless, often even before they have fully migrated to it from the legacy systems. After leading successful Microservices adoption at SoundCloud and DigitalOcean, recently at Meetup I have faced the challenge of pivoting from a traditional monolith-to-microservices migration to a cloud-native platform. In this talk, let's discuss the fundamental concepts, technologies, and practices behind Microservices and Serverless, and how a software architect used to distributed systems based on microservices needs to change their mindset and approach when adopting Serverless.

The Not-So-Straightforward Road From Microservices to Serverless

Phil Calçado

Ten Years of Failing Microservices

Phil Calçado

How are microservices in 2017 different from how we used to build them at the beginning of the decade? More traditional Service-Oriented Architectures were defined by protocols and standards published and curated by industry consortiums. Knowledge of the architectural style usually called "microservices", on the other hand, is often in the form of patterns, cautionary tales, and tools extracted from real-world reports and software made available by organisations that have adopted this style. Almost ten years since the first wave of such reports, the landscape has changed considerably. Many hard challenges from the past have been eased or completely solved, and a lot of the custom software created by the microservices pioneers have been made off-the-shelf open source software. In this talk, Phil Calçado will contrast what we first found in the first generation of microservices architectures against the current generation's landscape. Let's talk about which previous common knowledge and patterns are deprecated, which ones are still active, and introduce some of the ones that have been recently added to our toolbox.

The Next Generation of Microservices

Phil Calçado

The Next Generation of Microservices — YOW 2017 Brisbane

Phil Calçado

The Economics of Microservices (2017 CraftConf)

Phil Calçado

TALK #2: Microservices vs. The First Law of Object Design We've been breaking systems and application into smaller components for a long time now. From Component-Based Design to Distributed Objects to SOA to what is today's preferred golden hammer: microservices. One definition of microservices is that it is a flavor of SOA that emphasizes many specialize services versus a few more generalist ones. Often these microservices are so small that they take care of a single "object". Distributed objects aren't new to this industry, and in 2003, Martin Fowler wrote a classic article where he discusses several problems with this model, and proposes the First Law of Distributed Objects: "Objects have been around for a while, and sometimes it seems that ever since they were created, folks have wanted to distribute them. However, distribution of objects, or indeed of anything else, has a lot more pitfalls than many people realize, especially when they're under the influence of vendors' cozy brochures. This article is about some of these hard lessons-lessons I've seen many of my clients learn the hard way... my First Law of Distributed Object Design: Don’t distribute your objects!" Reinventing the wheel is nothing new in our field, but if microservices are meant to be small, how can we avoid the same problems from the past? What are the technologies, architectures, protocols, and practices we need in place to make sure that our microservices architecture isn't just the largest bowl of spaghetti this organization has ever cooked? SPEAKER: Phil Calçado, Director of Software Engineering at DigitalOcean Phil Calçado works at DigitalOcean, where he helps build the cloud for developers. Before that, he spent four years building the team and architecture behind SoundCloud's move from a monolith to microservices. He tweets at @pcalcado writes at http://philcalcado.com.

Microservices vs. The First Law of Distributed Objects - GOTO Nights Chicago ...

Phil Calçado

Finagle-Based Microservices at SoundCloud

Phil Calçado

An example of Future composition in a real app

Phil Calçado

From a monolithic Ruby on Rails app to the JVM

Phil Calçado

Applying Evolutionary Architecture on a Popular API

Phil Calçado

SpeakerConf: my findings in trying to use this functional programming busines...

Phil Calçado

[GOTO Copenhagen 2012] The Startup Hangover: Supporting 15 mil Users

Phil Calçado

When writing Object-Oriented software these days, few developers doubt the benefits of TDD. The Software Craftsmanship movement even goes one step further, and says that it is just plain irresponsible to write software without this tool. More and more projects are using Functional programming languages, though, and TDD is not so common in this side of the software development world. Maybe TDD doesn’t make sense outside Object-Oriented software? After experimenting with the TDD mindset and Functional languages in real-world projects, my experience is that those also benefit a lot from using tests as design aid. In this talk, let’s investigate what is generally accepted as good practices in Functional Programming and how to use TDD to take us there, with examples in Clojure.

(v2.0) Better Functional Design Through Test-Driven Development

Phil Calçado

(In Portuguese) Seu produto é um sucesso, e agora? desafios técnicos que uma...

Phil Calçado

mistaeks i’ve made developing software products

Phil Calçado

Berlin-Brandenburg Scala User Group: objects can still teach us one or two th...

Phil Calçado

Mais de Phil Calçado (20)

the afterparty: refactoring after 100x hypergrowth

don't try this at home: self-improvement as a senior leader

The Economics of Microservices (redux)

From microservices to serverless - Chicago CTO Summit 2019

The Not-So-Straightforward Road From Microservices to Serverless

Ten Years of Failing Microservices

The Next Generation of Microservices

The Next Generation of Microservices — YOW 2017 Brisbane

The Economics of Microservices (2017 CraftConf)

Microservices vs. The First Law of Distributed Objects - GOTO Nights Chicago ...

Finagle-Based Microservices at SoundCloud

An example of Future composition in a real app

From a monolithic Ruby on Rails app to the JVM

Applying Evolutionary Architecture on a Popular API

SpeakerConf: my findings in trying to use this functional programming busines...

[GOTO Copenhagen 2012] The Startup Hangover: Supporting 15 mil Users

(v2.0) Better Functional Design Through Test-Driven Development

(In Portuguese) Seu produto é um sucesso, e agora? desafios técnicos que uma...

mistaeks i’ve made developing software products

Berlin-Brandenburg Scala User Group: objects can still teach us one or two th...

Último

This presentations targets students or working professionals. You may know Google for search, YouTube, Android, Chrome, and Gmail, but did you know Google has many developer tools, platforms & APIs? This comprehensive yet still high-level overview outlines the most impactful tools for where to run your code, store & analyze your data. It will also inspire you as to what's possible. This talk is 50 minutes in length.

Powerful Google developer tools for immediate impact! (2023-24 C)

wesley chun

Heather Hedden, Senior Consultant at Enterprise Knowledge, presented “The Role of Taxonomy and Ontology in Semantic Layers” at a webinar hosted by Progress Semaphore on April 16, 2024. Taxonomies at their core enable effective tagging and retrieval of content, and combined with ontologies they extend to the management and understanding of related data. There are even greater benefits of taxonomies and ontologies to enhance your enterprise information architecture when applying them to a semantic layer. A survey by DBP-Institute found that enterprises using a semantic layer see their business outcomes improve by four times, while reducing their data and analytics costs. Extending taxonomies to a semantic layer can be a game-changing solution, allowing you to connect information silos, alleviate knowledge gaps, and derive new insights. Hedden, who specializes in taxonomy design and implementation, presented how the value of taxonomies shouldn’t reside in silos but be integrated with ontologies into a semantic layer. Learn about: - The essence and purpose of taxonomies and ontologies in information and knowledge management; - Advantages of semantic layers leveraging organizational taxonomies; and - Components and approaches to creating a semantic layer, including the integration of taxonomies and ontologies

The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf

Enterprise Knowledge

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

Advantages of Hiring UIUX Design Service Providers for Your Business

Pixlogix Infotech

Created by Mozilla Research in 2012 and now part of Linux Foundation Europe, the Servo project is an experimental rendering engine written in Rust. It combines memory safety and concurrency to create an independent, modular, and embeddable rendering engine that adheres to web standards. Stewardship of Servo moved from Mozilla Research to the Linux Foundation in 2020, where its mission remains unchanged. After some slow years, in 2023 there has been renewed activity on the project, with a roadmap now focused on improving the engine’s CSS 2 conformance, exploring Android support, and making Servo a practical embeddable rendering engine. In this presentation, Rakhi Sharma reviews the status of the project, our recent developments in 2023, our collaboration with Tauri to make Servo an easy-to-use embeddable rendering engine, and our plans for the future to make Servo an alternative web rendering engine for the embedded devices industry. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://ossna2024.sched.com/event/1aBNF/a-year-of-servo-reboot-where-are-we-now-rakhi-sharma-igalia

A Year of the Servo Reboot: Where Are We Now?

Igalia

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

The presentation explores the development and application of artificial intelligence (AI) from its inception to its current status in the modern world. The term "artificial intelligence" was first coined by John McCarthy in 1956 to describe efforts to develop computer programs capable of performing tasks that typically require human intelligence. This concept was first introduced at a conference held at Dartmouth College, where programs demonstrated capabilities such as playing chess, proving theorems, and interpreting texts. In the early stages, Alan Turing contributed to the field by defining intelligence as the ability of a being to respond to certain questions intelligently, proposing what is now known as the Turing Test to evaluate the presence of intelligent behavior in machines. As the decades progressed, AI evolved significantly. The 1980s focused on machine learning, teaching computers to learn from data, leading to the development of models that could improve their performance based on their experiences. The 1990s and 2000s saw further advances in algorithms and computational power, which allowed for more sophisticated data analysis techniques, including data mining. By the 2010s, the proliferation of big data and the refinement of deep learning techniques enabled AI to become mainstream. Notable milestones included the success of Google's AlphaGo and advancements in autonomous vehicles by companies like Tesla and Waymo. A major theme of the presentation is the application of generative AI, which has been used for tasks such as natural language text generation, translation, and question answering. Generative AI uses large datasets to train models that can then produce new, coherent pieces of text or other media. The presentation also discusses the ethical implications and the need for regulation in AI, highlighting issues such as privacy, bias, and the potential for misuse. These concerns have prompted calls for comprehensive regulations to ensure the safe and equitable use of AI technologies. Artificial intelligence has also played a significant role in healthcare, particularly highlighted during the COVID-19 pandemic, where it was used in drug discovery, vaccine development, and analyzing the spread of the virus. The capabilities of AI in healthcare are vast, ranging from medical diagnostics to personalized medicine, demonstrating the technology's potential to revolutionize fields beyond just technical or consumer applications. In conclusion, AI continues to be a rapidly evolving field with significant implications for various aspects of society. The development from theoretical concepts to real-world applications illustrates both the potential benefits and the challenges that come with integrating advanced technologies into everyday life. The ongoing discussion about AI ethics and regulation underscores the importance of managing these technologies responsibly to maximize their their benefits while minimizing potential harms.

Artificial Intelligence: Facts and Myths

Joaquim Jorge

GenCyber Cyber Security Day Presentation

Michael W. Hawkins

In this session, we will delve into strategic approaches for optimizing knowledge management within Microsoft 365, amidst the evolving landscape of Copilot. From leveraging automatic metadata classification and permission governance with SharePoint Premium, to unlocking Viva Engage for the cultivation of knowledge and communities, you will gain actionable insights to bolster your organization's knowledge-sharing initiatives. In this session, we will also explore how to facilitate solutions to enable your employees to find answers and expertise within Microsoft 365. You will leave equipped with practical techniques and a deeper understanding of how there is more to effective knowledge management than just enabling Copilot, but building actual solutions to prepare the knowledge that Copilot and your employees can use.

Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...

Drew Madelung

With more memory available, system performance of three Dell devices increased, which can translate to a better user experience Conclusion When your system has plenty of RAM to meet your needs, you can efficiently access the applications and data you need to finish projects and to-do lists without sacrificing time and focus. Our test results show that with more memory available, three Dell PCs delivered better performance and took less time to complete the Procyon Office Productivity benchmark. These advantages translate to users being able to complete workflows more quickly and multitask more easily. Whether you need the mobility of the Latitude 5440, the creative capabilities of the Precision 3470, or the high performance of the OptiPlex Tower Plus 7010, configuring your system with more RAM can help keep processes running smoothly, enabling you to do more without compromising performance.

Boost PC performance: How more available memory can improve productivity

Principled Technologies

Choosing the right accounts payable services provider is a strategic decision that can significantly impact your business's financial performance and operational efficiency. By considering factors such as expertise, range of services, technology infrastructure, scalability, cost, and reputation, businesses can make informed decisions and select a provider that aligns with their unique needs and objectives. Partnering with the right provider can streamline accounts payable processes, drive cost savings, and position your business for long-term success. https://katprotech.com/accounts-payable-and-purchase-order-automation/

Factors to Consider When Choosing Accounts Payable Services Providers.pptx

Katpro Technologies

Discord is a free app offering voice, video, and text chat functionalities, primarily catering to the gaming community. It serves as a hub for users to create and join servers tailored to their interests. Discord’s ecosystem comprises servers, each functioning as a distinct online community with its own channels dedicated to specific topics or activities. Users can engage in text-based discussions, voice calls, or video chats within these channels. Understanding Discord Servers Discord servers are virtual spaces where users congregate to interact, share content, and build communities. Servers may revolve around gaming, hobbies, interests, or fandoms, providing a platform for like-minded individuals to connect. Communication Features Discord offers a range of communication tools, including text channels for messaging, voice channels for real-time audio conversations, and video channels for face-to-face interactions. These features facilitate seamless communication and collaboration. What Does NSFW Mean? The acronym NSFW stands for “Not Safe For Work,” indicating content that may be inappropriate for professional or public settings. NSFW Content NSFW content encompasses material that is sexually explicit, violent, or otherwise graphic in nature. It often includes nudity, profanity, or depictions of sensitive topics.

Understanding Discord NSFW Servers A Guide for Responsible Users.pdf

UK Journal

Scaling API-first – The story of a global engineering organization

Radu Cotescu

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Presentation on how to chat with PDF using ChatGPT code interpreter

naman860154

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

The Raspberry Pi 5 was announced on October 2023. This new version of the popular embedded device comes with a new iteration of Broadcom’s VideoCore GPU platform, and was released with a fully open source driver stack, developed by Igalia. The presentation will discuss some of the major changes required to support this new Video Core iteration, the challenges we faced in the process and the solutions we provided in order to deliver conformant OpenGL ES and Vulkan drivers. The talk will also cover the next steps for the open source Raspberry Pi 5 graphics stack. (c) Embedded Open Source Summit 2024 April 16-18, 2024 Seattle, Washington (US) https://events.linuxfoundation.org/embedded-open-source-summit/ https://eoss24.sched.com/event/1aBEx

Raspberry Pi 5: Challenges and Solutions in Bringing up an OpenGL/Vulkan Driv...

Igalia

Enterprise Knowledge’s Urmi Majumder, Principal Data Architecture Consultant, and Fernando Aguilar Islas, Senior Data Science Consultant, presented "Driving Behavioral Change for Information Management through Data-Driven Green Strategy" on March 27, 2024 at Enterprise Data World (EDW) in Orlando, Florida. In this presentation, Urmi and Fernando discussed a case study describing how the information management division in a large supply chain organization drove user behavior change through awareness of the carbon footprint of their duplicated and near-duplicated content, identified via advanced data analytics. Check out their presentation to gain valuable perspectives on utilizing data-driven strategies to influence positive behavioral shifts and support sustainability initiatives within your organization. In this session, participants gained answers to the following questions: - What is a Green Information Management (IM) Strategy, and why should you have one? - How can Artificial Intelligence (AI) and Machine Learning (ML) support your Green IM Strategy through content deduplication? - How can an organization use insights into their data to influence employee behavior for IM? - How can you reap additional benefits from content reduction that go beyond Green IM?

Driving Behavioral Change for Information Management through Data-Driven Gree...

Enterprise Knowledge

Explore 'The Codex of Business: Writing Software for Real-World Solutions,' a compelling SlideShare presentation that delves into digital transformation in healthcare. Discover through a detailed case study how Agile methodologies empower healthcare providers to develop, iterate, and refine digital solutions that address real-world challenges. Learn how strategic planning, user feedback, and continuous improvement drive success in deploying technologies that enhance patient care and operational efficiency. Ideal for healthcare professionals, IT specialists, and digital transformation advocates seeking actionable insights and practical examples of technology making a real difference.

The Codex of Business Writing Software for Real-World Solutions 2.pptx

Malak Abu Hammad

A Call to Action for Generative AI in 2024

Results

Evolutionary Architecture at Work

1. Monday, April 22, 13

2. Evolutionary Architecture at Work phil calçado @pcalcado http://philcalcado.com Monday, April 22, 13

3. 2011: Phil decides to move to Berlin Monday, April 22, 13

4. Monday, April 22, 13

5. Monday, April 22, 13

6. Monday, April 22, 13

7. ~ 180 million users / month > 10 hours of audio uploaded every minute Monday, April 22, 13

8. Organisation challenges Monday, April 22, 13

9. SoundCloud was born on Rails It allowed us to iterate real fast and keep code quality up(-ish). Monday, April 22, 13

10. Controller ActiveRecord Model Database Rails is simple. Monday, April 22, 13

11. Controller ActiveRecord Model Database Rails is simple. But it leads you to monoliths SoundCloud .com Monday, April 22, 13

12. Conway’s Law kicks in Monolithic applications lead to monolithic teams Controller ActiveRecord Model Database SoundCloud .com ? Monday, April 22, 13

13. Big teams == overhead Who is doing what? Monday, April 22, 13

14. Big teams == overhead Stand-ups become the main communication channel Monday, April 22, 13

15. Big teams == overhead Massive backlog requires constant grooming and management Monday, April 22, 13

16. Big teams == overhead In the end you’ll need a full time “Iteration Manager” Monday, April 22, 13

17. technical challenges Monday, April 22, 13

18. There is one system SoundCloud .com Monday, April 22, 13

19. There is one system not really. Sounds & Sets Social Graph Premium Features Search Activity Stream ... Monday, April 22, 13

20. Multiple subsystems Ruby/Rails are a horrible Golden Hammers Monday, April 22, 13

21. Multiple subsystems The stability of the system is pretty much the same as the less stable subsystem’s Monday, April 22, 13

22. We need to split Monday, April 22, 13

23. Controller ActiveRecord Model Database SoundCloud .com ? Monday, April 22, 13

24. Sounds & Sets Social Graph? Premium Features Monday, April 22, 13

25. How? Have an enterprise Architect? Monday, April 22, 13

26. How? Create an architecture Steering Group? Monday, April 22, 13

27. What about Everyone is an architect? Monday, April 22, 13

28. Enabling the teams Monday, April 22, 13

29. Step 1) Stabilise the legacy app Monday, April 22, 13

30. Idiomatic Rails is funny Monday, April 22, 13

31. Understanding the Rails mindset: http://bit.ly/not-a-virtue Monday, April 22, 13

32. Understanding the Rails mindset: i do not think it means what you think it means http://bit.ly/not-a-virtue Monday, April 22, 13

33. Stopgap Solution Monday, April 22, 13

34. Stopgap Solution Monday, April 22, 13

35. Stopgap Solution (A lot like java circa 2005) Monday, April 22, 13

36. Step 2) Create a common protocol Monday, April 22, 13

37. Sounds & Sets Social Graph Premium Features Search Activity Stream ... Monday, April 22, 13

38. Sounds & Sets Social Graph Premium Features Search Activity Stream ... Ruby Clojure Go Haskell Scala Ruby Monday, April 22, 13

39. We want to try things before making a call Monday, April 22, 13

40. Don’t publish rules, publish guidelines Monday, April 22, 13

41. Step 3) Minimise non-technical overhead Monday, April 22, 13

42. Social Graph? Monday, April 22, 13

43. Step 4) Minimise technical overhead Monday, April 22, 13

44. Pushing a micro-service to production should be easy Monday, April 22, 13

45. Monday, April 22, 13

46. Monday, April 22, 13

47. Monday, April 22, 13

48. Monday, April 22, 13

49. People solving the same problems over and over Monday, April 22, 13

50. Monday, April 22, 13

51. (with the same code...) Monday, April 22, 13

52. Monday, April 22, 13

53. Monday, April 22, 13

54. Current status Monday, April 22, 13

55. About 6 application teams, 3 engineers + 1 product person Monday, April 22, 13

56. Micro-services in Clojure, Scala and (J)Ruby Monday, April 22, 13

57. Pull Request lead time reduced from 3 to 1 week Monday, April 22, 13

58. Still afraid of deleting old code Monday, April 22, 13

59. We have “black hole” teams Monday, April 22, 13

60. There is a lot of infrastructure to build Monday, April 22, 13

61. In 4 slides Monday, April 22, 13

62. Step 1) Stabilise the legacy app Don’t stop the world, but don’t let the code base deteriorate even more Monday, April 22, 13

63. Step 2) Create a common protocol Guidelines and examples, not rules Monday, April 22, 13

64. Minimise non-technical overhead Small teams don’t need... a lot Monday, April 22, 13

65. Step 4) Minimise technical overhead Only try to re-use after you use Monday, April 22, 13

66. phil calçado http://philcalcado.com @pcalcado www.soundcloud.com Monday, April 22, 13

Evolutionary Architecture at Work

Recomendados

Recomendados

Mais conteúdo relacionado

Destaque

Destaque (19)

Semelhante a Evolutionary Architecture at Work

Semelhante a Evolutionary Architecture at Work (20)

Mais de Phil Calçado

Mais de Phil Calçado (20)

Último

Último (20)

Evolutionary Architecture at Work