Structuring apps in Scala

•

1 like•1,627 views

Phil Calçado

SOLVING INTERESTING
PROBLEMS

Thursday, March 14, 13

SOLVING INTERESTING
PROBLEMS
meh.

Thursday, March 14, 13

SOLVING BORING
PROBLEMS IN A
INTERESTING WAY

Thursday, March 14, 13

SOLVING BORING
PROBLEMS IN A
INTERESTING WAY
hell yeah!

Thursday, March 14, 13

SOUNDCLOUD
DEVELOPER CHALLENGE’S
TEST SUITE

Thursday, March 14, 13

Recruitment Challenge

W(hy)TF?

Thursday, March 14, 13

Old Challenge

Build me a file uploader

Thursday, March 14, 13

Old Challenge

Build me a file uploader
Boring

Thursday, March 14, 13

Old Challenge

Build me a file uploader
Boring
Use flash plugin

Thursday, March 14, 13

Old Challenge

Build me a file uploader
Boring
Use flash plugin
Not enough code
Thursday, March 14, 13

New Challenge

Given a series of events
and a bunch of connected
clients, who should be
notified of which events?

Thursday, March 14, 13

What I’m used to

Thursday, March 14, 13

Combinators all the way down

Thursday, March 14, 13

not leveraging
the type system

Thursday, March 14, 13

I am pretty sure
I’m doing it wrong.

Thursday, March 14, 13

Instance-Based Injection

Thursday, March 14, 13

Extremely thin, orthogonal, traits

Thursday, March 14, 13

Use method visibility

Thursday, March 14, 13

Modules are abstract

Thursday, March 14, 13

typesafe: self-types for
dependencies

Thursday, March 14, 13

Precog: Instead of import,
extends or with

Thursday, March 14, 13

ACTUALLY, HOW ARE WE
BUILDING APPS?

Thursday, March 14, 13

internet

Legacy Application
(Rails)

Database

Thursday, March 14, 13

internet

API

Sounds Users Stats Stream

Notifications Settings Recommender Messaging

Thursday, March 14, 13

A LOT LIKE
TYPESAFE’S

Thursday, March 14, 13

Controllers define dependency
on components

Thursday, March 14, 13

Components are abstract

Thursday, March 14, 13

One flat instance

Thursday, March 14, 13

I was pretty sure
I was doing it wrong.

Thursday, March 14, 13

I am pretty sure
I’m still doing it wrong.

Thursday, March 14, 13

I am pretty sure
I’m still doing it wrong.

what do you use?

Thursday, March 14, 13

REFERENCES

• http://bit.ly/pcalcado-goto
• http://bit.ly/effective-scala-Dependency-injection
• http://bit.ly/Bakery-from-the-Black-Lagoon
• http://bit.ly/Martin-Odersky-Reflection-and-
Compilers

Thursday, March 14, 13

phil calçado

http://philcalcado.com
@pcalcado

www.soundcloud.com

Thursday, March 14, 13

Viewers also liked

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

Os cuidados e os limites do Responsive Web Design

Diego Eis

CSS 4 - What's coming up

Diego Eis

Cloud Reliability Patterns

rafaelferreira

Desafio dos testes em uma arquitetura de micro serviços

Frederico Augusto Do Carmo Moreira

SoundCloud is the largest repository of audio on the web, used by more than 200 million people every month, who upload more than 11 hours of audio every minute. Like so many others, we have migrated from a typical monolithic architecture to microservices. While the benefits brought by this style of SOA to our productivity and reliability are clear, the architecture required some non-obvious changes in the way we operate systems, and a way to tackle the overhead associated with having hundreds of small moving parts to serve every request. In this talk we’ll share the toolkit and strategy SoundCloud uses to keep its microservices explosion manageable. What do we do about the operations overhead? How to spread devops skills across teams to support the “you build it, you run it” vision? How to deal with breaking changes and asynchronous behaviours? How to deal with chatty interactions? Which protocol? How do I even get a diagram telling me how all this stuff is put together?

Three Years of Microservices at SoundCloud - Distributed Matters Berlin 2015

Phil Calçado

SoundCloud's microservice architecture is built mostly in Scala, using Finagle as its distributed systems workhorse. Finagle is an RPC system for the JVM, and it is based on a pipes-and-filters architecture that maps very nicely to functional programming concepts of higher-order functions and combinators. Over the past few years we have found that it is extremely useful to go even a step further and think of microservices as functions themselves. In this talk let's explore how SoundCloud uses Scala and Finagle, and how we started thinking of a microservices architecture as a special case of a functional system.

ScalaItaly 2015 - Your Microservice as a Function

Phil Calçado

Evolutionary Architecture at Work

Phil Calçado

Rhein-Main Scala Enthusiasts — Your microservice as a Function

Phil Calçado

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

Microservices - Quebrando gigantes em pequenos

Vinícius Krolow

Amadurecendo Equipes com Microservices

sanchez_ivan

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

Microservices

Diego Pacheco

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

Diego Eis

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

Viewers also liked (20)

APIs: The Problems with Eating your Own Dog Food

Os cuidados e os limites do Responsive Web Design

CSS 4 - What's coming up

Cloud Reliability Patterns

Desafio dos testes em uma arquitetura de micro serviços

Three Years of Microservices at SoundCloud - Distributed Matters Berlin 2015

ScalaItaly 2015 - Your Microservice as a Function

Evolutionary Architecture at Work

Rhein-Main Scala Enthusiasts — Your microservice as a Function

Vida longa para SOA com microservices

Microservices - Quebrando gigantes em pequenos

Amadurecendo Equipes com Microservices

Um pequeno estudo sobre a microsoft

Integração utilizando REST API e Microservices

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

Microservices

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

Introdução à Microservices

Workshop soa, microservices e devops

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

Similar to Structuring apps in Scala

Google’s Fuel For Your Marketing Machine - A Workshop In Aspen For Industry P...

Chris DallaVilla

Fed2013_Managing Workplace Productivity

Jason W. Womack, MEd MA

Writing applications for phones has been a daunting task since every platform uses it's own language and API's. PhoneGap will solve this problem for you by utilizing the browser capabilities. In this session we will see how we can turn a web based application into a native app. We will also look at posibilites to integrate native functionality, like the camera or accelerometer, in our application. The final part of the presentation is about deployment of these applications. Adobe offers a cloud based service called PhoneGap Build which easily builds your application for all platforms.

Native Javascript apps with PhoneGap

Martin de Keijzer

Soflophp 2013 - SysAdmin skills for PHP developers

Pablo Godel

Unmoderated User Testing

ZURB

Metadata enables consistency, context and interoperability in a cross-channel context by managing, describing and exchanging information objects. This presentation explores 3 different types of metadata: administrative, descriptive, and structural, and their role in UX practices including content strategy, responsive design, rich snippets, and web forms. We’ll then look at the cross-channel ecosystem, understanding media, channels, interactions and touchpoints. We’ll explore The Internet of Things, and furthermore the importance of information exchanges in cross-channel service design. From there we learn about the nuts and bolts of an information exchange, including semantics, syntax and lexicon, and how these are documented in schema. Then we’ll look at some of the common standards used to specify schema for information exchanges and semantic markup. Last but not least, we’ll explore how linked data and ontologies enable us to progress from the Web of Documents to the Web of Data. Presentation for the Information Architecture Summit in Baltimore, Maryland April 6th 2013. I had a great time & welcome feedback to further the discussion. Thanks everyone!

IAS13: Metadata in the Cross-Channel Ecosystem: Consistency, Context and Inte...

aungstad

The brand experience at colleges and universities has long been rich and multi-faceted. Prospective students tour the campus, current students attend carefully designed classes and alumni return for homecoming and sporting events. But as more university activities move online, our constituents now interact with our brand in different ways. Recruiting students, alumni engagement and even the academic experience are increasingly happening in the digital space. This presentation examines the different ways audiences experience higher education brands in a digital age.

The Changing Nature of Brand Experience in Higher Education

Joel Pattison

Test Driven Infrastructure Development

Puppet

Test driven infrastructure development

Tomas Doran

Future layouts

Chris Mills

THE MISSING MANUAL FOR DATA SCIENCE: REMIX. RESUSE. REPRODUCE from Structure:...

Gigaom

Making meaning with mobile apps

Richard Byrne

TDD at Smartbear

froderik

Engine on Rails

Zigotto Tecnologia

Creating apps usually is a very time consuming process when it comes to development. You need to write your code for all different platforms like iOS, Android, Blackberry, Windows Phone. Sencha Touch solves this problem by giving you a framework for the langauge we as web developers all know and love; Javascript! In this session we will see how Sencha Touch makes it easy to create apps. We will talk about the pro’s and cons of using HTML5 and Javascript. After that I will take you on a tour on how to create a simple tab-based application with an external data source. We will have a look at theming, and look into some performance optimizations.

Hybrid Mobile Web Apps with Sencha Touch 2

Martin de Keijzer

Roncalli i pad intro presentation

Scrappyvore

Drupal is for coders only right? Well, to be fair without the many talented Drupal coders this presentation would'nt even exist! Drupal is a fantastic system capable of building amazing custom solutions, but do you have to be a coder to build a site with Drupal? How far can you get without writing a single line of code and just using your mouse? The presentation uses the photo mapping site www.stefanvanhooft.com as a case study. Read the full presentation description and find out what others say here http://2013.drupalcamplondon.co.uk/session/mouse-photogeometa-land-drupal-without-coding

Drupal without coding

Stefan van Hooft

Connected Educator flenj 2013

Lindeneau Elementary School

NNSTOY A Framework of Fun:Learning Through and From Games

Curtis Chandler

Borg - Resistance is futile: how implementing next generation discovery syste...

IL Group (CILIP Information Literacy Group)

Similar to Structuring apps in Scala (20)

Google’s Fuel For Your Marketing Machine - A Workshop In Aspen For Industry P...

Fed2013_Managing Workplace Productivity

Native Javascript apps with PhoneGap

Soflophp 2013 - SysAdmin skills for PHP developers

Unmoderated User Testing

IAS13: Metadata in the Cross-Channel Ecosystem: Consistency, Context and Inte...

The Changing Nature of Brand Experience in Higher Education

Test Driven Infrastructure Development

Test driven infrastructure development

Future layouts

THE MISSING MANUAL FOR DATA SCIENCE: REMIX. RESUSE. REPRODUCE from Structure:...

Making meaning with mobile apps

TDD at Smartbear

Engine on Rails

Hybrid Mobile Web Apps with Sencha Touch 2

Roncalli i pad intro presentation

Drupal without coding

Connected Educator flenj 2013

NNSTOY A Framework of Fun:Learning Through and From Games

Borg - Resistance is futile: how implementing next generation discovery syste...

More from 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 @ SoundCloud

Phil Calçado

A Brief Talk On High-Performing Organisations

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

SoundCloud Masterclass on Brazil

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

More from 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 @ SoundCloud

A Brief Talk On High-Performing Organisations

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

SoundCloud Masterclass on Brazil

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

Structuring apps in Scala

1. Thursday, March 14, 13

2. Structuring apps in Scala a.k.a. I have no idea what I’m doing phil calçado @pcalcado http://philcalcado.com Scala User Group - Berlin Brandenburg Thursday, March 14, 13

3. WHY BOTHER? Thursday, March 14, 13

4. SOLVING INTERESTING PROBLEMS Thursday, March 14, 13

5. SOLVING INTERESTING PROBLEMS meh. Thursday, March 14, 13

6. SOLVING BORING PROBLEMS IN A INTERESTING WAY Thursday, March 14, 13

7. SOLVING BORING PROBLEMS IN A INTERESTING WAY hell yeah! Thursday, March 14, 13

8. SOUNDCLOUD DEVELOPER CHALLENGE’S TEST SUITE Thursday, March 14, 13

9. Recruitment Challenge W(hy)TF? Thursday, March 14, 13

10. Old Challenge Build me a file uploader Thursday, March 14, 13

11. Old Challenge Build me a file uploader Boring Thursday, March 14, 13

12. Old Challenge Build me a file uploader Boring Use flash plugin Thursday, March 14, 13

13. Old Challenge Build me a file uploader Boring Use flash plugin Not enough code Thursday, March 14, 13

14. New Challenge Given a series of events and a bunch of connected clients, who should be notified of which events? Thursday, March 14, 13

15. What I’m used to Thursday, March 14, 13

16. What I’m used to Thursday, March 14, 13

17. Combinators all the way down Thursday, March 14, 13

18. a LOT of code Thursday, March 14, 13

19. a LOT of wiring Thursday, March 14, 13

20. not leveraging the type system Thursday, March 14, 13

21. I am pretty sure I’m doing it wrong. Thursday, March 14, 13

22. TWITTER Thursday, March 14, 13

23. Instance-Based Injection Thursday, March 14, 13

24. Extremely thin, orthogonal, traits Thursday, March 14, 13

25. Use method visibility Thursday, March 14, 13

26. TYPESAFE/PRECOG Thursday, March 14, 13

27. Modules are abstract Thursday, March 14, 13

28. typesafe: self-types for dependencies Thursday, March 14, 13

29. Precog: Instead of import, extends or with Thursday, March 14, 13

30. SOUNDCLOUD APPS Thursday, March 14, 13

31. ACTUALLY, HOW ARE WE BUILDING APPS? Thursday, March 14, 13

32. internet Legacy Application (Rails) Database Thursday, March 14, 13

33. internet API Sounds Users Stats Stream Notifications Settings Recommender Messaging Thursday, March 14, 13

34. SOUNDCLOUD APPS Thursday, March 14, 13

35. A LOT LIKE TYPESAFE’S Thursday, March 14, 13

36. Controllers define dependency on components Thursday, March 14, 13

37. Components are abstract Thursday, March 14, 13

38. One flat instance Thursday, March 14, 13

39. I was pretty sure I was doing it wrong. Thursday, March 14, 13

40. I am pretty sure I’m still doing it wrong. Thursday, March 14, 13

41. I am pretty sure I’m still doing it wrong. what do you use? Thursday, March 14, 13

42. REFERENCES • http://bit.ly/pcalcado-goto • http://bit.ly/effective-scala-Dependency-injection • http://bit.ly/Bakery-from-the-Black-Lagoon • http://bit.ly/Martin-Odersky-Reflection-and- Compilers Thursday, March 14, 13

43. phil calçado http://philcalcado.com @pcalcado www.soundcloud.com Thursday, March 14, 13

Structuring apps in Scala

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (20)

Similar to Structuring apps in Scala

Similar to Structuring apps in Scala (20)

More from Phil Calçado

More from Phil Calçado (20)

Structuring apps in Scala