Polyglot Architectures

There is an ever growing trend for organisations to be mixing and matching several programming languages and platforms in their architectures. This allows teams to use best of breed tools and even heterogenuous programming paradigms, in order to deliver a product faster and in a higher quality. But multi-platform architectures also pose many issues for architects, managers, team leaders etc. This track explores the benefits associated with persuing a polyglot arcitecture - and what the hidden price for doing polyglot programming.

Day of week:

Wednesday

Location:

Legends Ballroom - Robinson-Whitman

Host:

Aaron Erickson

Presentations

Continuous Delivery Unconference

11:30pm - 12:40pm

By: Amr Elssamadisy

Meeting each other in the context of conversations we care about is why at QCon we are giving prime time to the unconference format; it creates a space for peer-to-peer learning, collaboration and creativity.

First we’ll father in a circle to be guided through creating an agenda using open space technology. Then there will be three three 20 minute time slots, each with 5 concurrent break out discussions that were designed by you.

Attendees often know more than the speakers! Bring your questions, ideas - be prepared to be surprised.
Building Polyglot Projects

4:00pm - 4:50pm

By: Kurt Schrader

It's easy to say, "use the best language for the job," but actually setting up a project (and a team) to do so can be extremely difficult. Many development teams choose one language to start a project with and end up stuck there forever, despite their intentions. In this talk we'll explore the patterns and practices that make growing a project in a polyglot way both possible and practical. We'll discuss the easiest ways to integrate multiple languages, when to add a new language, and what to do when things feel like they're getting out of hand, all drawn from real world examples.
E Pluribus Unum: A Survey of Multiparadigm Programming

1:40pm - 2:30pm

By: Paul Snively

You're probably familiar with polyglot programming, especially if you're a web developer. SQL for your relational database, Java or Ruby or Python for your middle tier, JavaScript for your browser. Each of these languages has particular strengths and weaknesses, so we try to use the best tool for the job in each tier. In this presentation, Paul Snively will show how some of these benefits can be obtained without switching languages among tiers using languages that are, by design or by accident, multiparadigm: the increasingly-popular OO/FP hybrid Scala, the reviled-but-still-useful C++, and the wat-inducing OCaml. Be prepared to have your polyglot assumptions challenged and to have fun in the process.
Polyglot Architecture: A Rational Approach to Software Design

2:50pm - 3:40pm

By: Richard Minerich

Functional programming is often a great first choice, but that doesn't mean it's always the best choice. Designing software is an art unto itself because of the huge number of tradeoffs to take into consideration.

Come join a veteran polyglot architect in exploring these design choices with an eye towards building the best software possible with the tools at hand.
User experience driven architecture

10:20pm - 11:10pm

By: Praful Todkar , Cassandra Shum

Coming from a traditional web application background, the definition of user experience was slapping some UI jazz on top of some data received from the server. On a recent project, developing tablet based learning platform, our world was turned upside down because the user experience was a major focus of the platform, almost to the point where it was driving our architecture in a big way. Come experience for yourself the exciting journey we have undertook in building user experience driven architecture.
Polygot Architecture for Rapid Release: Friend or Foe?

5:10pm - 6:00pm

By: Rachel Laycock

Many of us are bought into the idea of rapidly releasing through methodologies like Continuous Delivery. We now want to release when we want as often as we want, but does polyglot programming and architecture support this? Or is choosing the right development language and tool for the job at odds with rapidly releasing your software? For example, if you bring in a language is it suitable to the environment you will release to or will you cause your operations team to cry themselves to sleep at night? Or conversely can the development language and tool choices make build and deploy easier, faster and more maintainable? These are some of the questions I will address in this session. How do we choose the right architecture for our release schedule? What can we mix up at will depending on the problem space and what language and tool choices that you make in the development cycle could cause conflict with operations? We will delve into where language and tool choices are orthogonal and even make operations peoples lives a little easier and demonstrate what a build and deployment pipeline could look like in this context