Sebastian Meyen, Chief Content Officer at Software & Support Media, will welcome you and introduce you the JAX Finance and JAX DevOps program.
In the opening keynote Eric Horesnyi will talk about the actors that lead the change in the FinTech movement and the so-called industry disruptors. He invites you on a journey to discover what’s under the hood of this ongoing revolution and to debunk some myths concerning the future of banking and the culture of unicorns. He will also discuss the tech part of the FinTech movement and how it revolutionizes every part of the finance industry and every actor involved.
His keynote is followed by a panel discussion, where we will try and find out whether developers could lead the change or not and how they can benefit from the fact that IT is now at the heart of all businesses.
Sebastian is Chief Content Officer at S&S Media. He has been actively involved with the IT industry for more than 10 years. As a journalist he is constantly in touch with thought leaders in software development and architecture. He is editor in chief of the German speaking Java Magazin and program chair of the JAX conferences since 2001. Prior to joining S&S Media, he studied philosophy and anthropology in Frankfurt, Germany.
Eric was a founding team member at Internet Way (French B2B ISP, sold to UUnet) then Radianz (Global Finance Cloud, sold to BT). He is a High Frequency Trading infrastructure expert, passionate about Fintech, IoT and Cleantech. Eric looks after 3 bozons and has worked in San Francisco, NYC, Mexico and now Paris.
As many startups of the last decade, SoundCloud's architecture started as a Ruby-on-Rails monolith, which later had to be broken into microservices to cope with the growing size and complexity of the site. The microservices initially ran on an in-house container management and deployment platform. Recently, the company has started to migrate to Kubernetes.
With the introduction of microservices, the existing conventional monitoring setup failed both conceptually and in terms of scalability. Thus, starting in 2012, SoundCloud invested heavily into the development of the open-source monitoring system Prometheus, which was designed for large-scale highly dynamic service-oriented architectures.
Migrating to Kubernetes, it became apparent that Prometheus and Kubernetes are a match made in open-source heaven. The talk will demonstrate the current Prometheus setup at SoundCloud, monitoring a large-scale Kubernetes cluster.
The speakers are production engineers at SoundCloud and core developers of the Prometheus project.
Fabian Reinartz is an engineer at CoreOS and one of the Prometheus core developers.
Previously, he was a production engineer at SoundCloud.
Björn is the team lead of Production Engineering at SoundCloud and one of the main Prometheus developers. Previously, he was a Site Reliability Engineer at Google and a number cruncher for science.
Junk goes in, junk comes out. Even the best application architecture is brittle in the face of misconfiguration.
And yet, even as applications grow ever more complex, we are failing to hold our configuration to a higher standard. Best practise is often avoided due to a combination of time pressures and the complexity of formally specifying configuration rules. A rebalancing is required.
What if it were possible to produce an advanced PoJo model, documentation and diagrams in minutes? What if there existed tooling, including an editor, to support common configuration use-cases? What if changes to the configuration model were trivial to maintain, with directions given where changes in source must be made as the model changes?
This session will discuss current configuration technologies before moving onto detailing an upcoming Java-centric modelling technology that aims to simplify application configuration/modelling.
Chris is a clean code enthusiast with a decade of experience in investment banking IT. Chris is active in the development community, being significantly involved in the recent 6.1 release of JavaCC, co-maintaining the AceGWT project, answering questions on stack-overflow, and also has a tech blog.
He has a very low opinion of reducible complexity, an obsession which led him out of his comfortable existence and into the arms of independent development.
Since 2011, Chris has been working full-time and alone on a project which he hopes will be of interest.
Complex, interconnected, legacy application stacks make up modern banking platforms. The challenging environment of digital disruption is impacting the banks, software deployment cycles must speed up in response to this. This presentation explains why containerisation, specifically implemented via the Docker Datacenter toolchain is a key tool in solving this dichotomy. Learn the specific challenges and situations found within banking application delivery which the Docker Datacenter stack helps overcome and why banks need to develop a container strategy to drive successful production deployment of the Docker Datacenter and the elements of a holistic container strategy.
Matt is a pragmatic technical operations architect and leader, using Devops to deliver quality software quickly and efficiently. With a background in both enterprise and start-up worlds, Matt aims to bring the best of DevOps and continuous delivery ideas to software delivery teams of any size, usually using Docker. Matt is also co-organiser of the London DevOps meetup—a group with over 2,500 members which meets monthly.
Dev and product teams in Financial Services have a lot on their shoulders these days. Not only do they have to develop a great product and its supporting infrastructure, but it needs to be fast, performant, it needs to scale and work on the cloud. Most importantly it needs to be secure.
Today’s hackers are not just breaking into servers, they’re attacking how you communicate with your infrastructure—exploiting the billing system, user signup and overall API infrastructure.
The session will show how Varnish Cache, the open source HTTP engine delivers fast, reliable web content at scale and provides a critical layer of protection for an API architecture in Financial Services. Developers, architects, product managers will learn how to build security into modern, highperformance API architectures.
The session will explore:
Federico Schwindt has more than twenty years of experience as a multi platform developer with particular focus on maximizing system performance, efficiency, response time, and overall system security. Federico is currently a senior software engineer at Varnish Software and since more than seventeen years a developer for the OpenBSD project. Prior to Varnish Software he worked six years as technical team lead for RBS Global Banking & Markets, and a myriad of other companies including Core Security, famous for the SSH insertion attack.
Do you want to have faster releases, increased efficiency, less unplanned work, fewer break-fixes, easier maintenance and better quality software?
Maven Central is the world’s largest open source repository for Java libraries and used by over 100,000 organisations globally. Development teams use open source libraries to develop functionally rich applications at speed in an agile manner, however there is an inherent security and license risk that needs mitigating. Sonatype will demonstrate live, in conjunction with Jenkins and Bamboo, how Nexus Lifecycle can produce a 'Bill of Materials’ report to show you what open source libraries are inside your application, what the security and license risks are and then show you how to remediate this from an Eclipse or IntelliJ IDE.
If anyone would like to bring their own Java application, either in EAR or WAR format, then Sonatype would more than welcome the opportunity to scan the application and produce a Bill of Materials report live at the event.
Nick has almost thirty years of technology experience with companies such as Hewlett-Packard, VERITAS, DELL and F5. He is passionate about helping companies mitigate the risk of using open source libraries in their applications.
Andy has over twenty years of application development experience, starting as a graduate with IBM before joining Lloyds Banking Group where he specialised in application release automation. As a Solutions Architect, Andy helps organisations to implement Sonatype solutions within their Devops pipeline.
As DevOps matures from craft, through trade, to a science, we are starting to work on distilling out how we can make DevOps' implementation and the organizational transformation repeatable and predictable, across all kinds of environments. As part of that search, it is time to start looking at humanity's other "operational" endeavors and see what is applicable to DevOps.
This keynote examines one of the largest operational systems built to date:
the national airspace system. We will look at specific aspects of how controllers (operations teams) work with pilots (developers) to safely move millions of passengers (customers) every year, with an incident rate that would make any development shop jealous.
In aviation, harsher, more crowded, and inclement conditions all require additional training: an instrument rating. Similarly, developers and operations teams buying in to "DevOps culture" is a great start, but it's often hard to nail down what that actually means. We'll examine the specific behavioral and operational elements of this other complex system that has been tamed and look at what's applicable to implementing a DevOps culture within our own industry.
Finally, we'll examine some of aviation's hard-learned lessons, and look at ways we can leverage this knowledge, and avoid those classes of pitfalls.
J. Paul Reed has over fifteen years experience in the trenches as a build/release and tools engineer, working with such organizations as VMware, Mozilla, Postbox, Symantec, and Salesforce.
In 2012, he founded Release Engineering Approaches, a consultancy incorporating a host of tools and techniques to help organizations realize how they can "Simply Ship. Every time." He's worked across a number of industries, from financial services to cloud-based infrastructure to health care, with teams ranging from 2 to 2500 on everything from tooling, operational analysis and improvement, team culture transformation, and business value optimization. He regularly speaks internationally on release engineering, DevOps, IT operations complexity, and human factors.
Paul is also the founding host of The Ship Show, a twice-monthly podcast tackling topics related to build engineering, DevOps, and release management.
Workflow engines can do interesting things: wait for events, correlate events, allow you to implement multi-step processing logic with sequence counters, fork-join, mutual exclusion, timeouts and much more. They can even keep a complete history of every processing step performed.
However, the current generation of workflow engines is increasingly unable to deliver the performance required by today's applications. At the same time, these engines are often bloated with high level features that many users do not need.
I believe that we can do much better. The next generation workflow engine is 100 times faster. It is horizontally scalable and delivers 100% uptime. Yet, It is a lot easier to use and comprehend than current generation engines. Come to my talk and see.
I'm passionate about BPM with a particular focus on process automation and process engines. My mission is to deliver the best possible experience to developers who want to use BPM technology in their applications. I'm a Java EE 6 aficionado and believe in polyglot technology stacks based on open standards. I like cooking, eating, traveling, drumming and -ing words.
CloudLens (formerly Zudio) was a traditional ASP.NET MVC 5 and WebAPI 2 application, run in every public Azure data-centre in the world, hosted on IIS in Microsoft Azure Web Sites. Then Microsoft announced the cross-platform, open-source .NET Core and ASP.NET 5, so I spent 2015 porting the application code to the new system, breaking it down into mini- and micro-services, rewriting bits in different languages, and getting it running in Docker containers on Linux VMs with an open-source orchestration platform. In this talk I will share my experiences, the challenges I encountered, the things I learned along the way, the benefits I gained, and my plans for pushing things further in 2016 and beyond.
Founder, CEO and Chief Developer of CloudLens, maker of tools for working with data in the cloud. International speaker, pathological programmer, erstwhile stand-up comic and the first person ever to use the word "unreconfigurablisation".
This presentation gives an overview of the technical solutions for the orchestration of Kubernetes and Docker based services. This means rethinking your IT-business in every area. TocCreate, maintain and modify many machines and containers on your developer notebook, in your data center or the cloud is a challenge. Our applications are constantly being expanded and adapted to different use cases. The Kubernetes and the Docker ecosystem offers promising tools for service discovering, automatic scaling, failover and deployment. The talk presents and discusses the practical benefits of the Kubernetes platform.
Peter is a infracoder, system architect and coach of numerous web systems. His special interest is in the development of complex information systems, including the design and implementation of test-driven processes. Since 1997 Peter Rossbach is active in HTTP server and web container. He is a committer on the Apache Tomcat project and member of the Apache Software Foundation. His special interest is the design of provisioning, monitoring and analysis systems for complex infrastructures. With the bee42 solutions GmbH he realized appropriate infrastructure products and offers training based on the Docker ecosystem current web technologies and cloud platforms.
Do you need to transform your business, deliver faster and better? Confused by all the buzz words and hype or how any of it can help you or your teams? Come with us as we take you on a whistle-stop tour of how we changed our relationship with development from “them and us” to a collaborative DevOps partnership. We’ll share the technologies we introduced (OpenStack, Docker, Jenkins, UCD…), the lessons we learnt and the rewards we are reaping.
Caroline Emmins is a senior software engineer at IBM‘s UK Development Lab where she is currently a lead engineer for the Cloud and Development Platforms Group.
During her 15 years with IBM she has helped develop many different technologies, from their Java SDKs to new SaaS offerings. She’s an automation specialist with a passion for technology, who for the last 18 months has been part of the team building IBM’s world-wide private developer cloud and the pipelines utilising it.
When she isn’t playing with computers she is usually laughing at the antics of her dog, Molly.
Software Engineer with a focus on DevOps, Agile and software development technologies. He has a penchant for mentoring and helping others get the most from their careers.
Starting in a greenfield project, there are many choices for configuration management and orchestration. Three years ago, we introduced SaltStack in consulting a startup company. Over the years, a diverse set of tools was integrated into our continuous integration and delivery stack to efficiently manage the growing local and cloud infrastructure.
In this talk, we will discuss the evolution of our CI/CD pipeline, managing complexity and knowledge in the cross-functional team as well as pitfalls and opportunities that arise using modern tools.
We will present key aspects of our fully automated cloud deployment not only enabling our customer to perform rapid releases but also keeping the DevOps team happy.
Martin is a Senior Consultant at TNG Technology Consulting. He is a strong advocate of DevOps principles and focuses on cloud technology and architecture of distributed systems. Currently, he is involved in the development of a large-scale web application using Salt, Terraform and AWS to automate deployments.
In his spare time, he is active in the Salt community and plays with embedded systems, virtualization and container scheduling technology.
Dr. Johannes Ebke is Software Consultant at TNG Technology Consulting.
He likes finding, fixing and extending tools to implement DevOps methodology in a cross functional team.
While driving the architecture of Continuous Integration, Continuous Delivery and their coupling, his utmost concern in the selection of tools are simplicity, speed and reproducability of deployments.
In his free time, he likes programming in Go.
What really is orchestration? It is one of those abstract topics, much like configuration management, that is defined differently by different organisations and covers a wide range of subject areas? Everything from ssh in a for-loop to container management now fits under the term orchestration. Is all that really orchestration? Why do we need orchestration? How does it fit into the wider configuration management picture? This talk aims to delve into those areas, to try and find a common understanding and to discuss why these problems are interesting, why they are hard and what we can do to try and solve them.
Liam Bennett is an Senior Engineer for OpenTable focused on designing and implementing the infrastructure and tools used by OpenTable’s developers every day. Prior to OpenTable Liam has been a release engineer and developer for several organisations but jumped into operations a few years ago.
Twenty years ago we were just learning how to hook up the new Java language to our relational database to run queries. Five years later and the first IMDGs are starting to appear on the scene and things get faster. Another 5 years and we get NoSQL, finally we can get rid of the ORM, NoSQL works nicely with IMDGs too. Then comes Hadoop and for some bizarre reason we start to see ORM coming back - something’s wrong. Spark has made some improvements over Hadoop but where are we now with this mess?
John will explore the data aggregation and analytics scene, where should you be going, how do these technologies fit and where the future might lie. Some coverage of the technologies combined with a little code and a demo of some very high performance in-memory analytics.
John is co-founder and CTO of C24, a London based fast data company specialising in high-volume, low-latency complex messaging. With customers including many of the world’s largest investment banks, C24 provides data optimisation for standards like SWIFT, ISO-20022, FpML and FIX as well as proprietary formats. C24 has recently released a new data optimization product - PREON - that creates highly optimized binary versions of these complex messages reducing memory and network usage by over 20 times, while significantly increasing performance.
John has been global chief architect at JP Morgan, BNP Paribas and was the original architect behind Visa’s V.me (now Visa Checkout). John has co-authored several Java books and is a frequent speaker at technical and banking conferences around the world. He is married to a French wife and has 3 boys (12, 14 & 17) who all love travelling (as long as there’s internet).
As operational failure becomes more acceptable to discuss within the software and IT operations industries, the necessity for holding constructive, actionable postmortems increases. But most of what we know about postmortems from "pop culture" isn't actually useful for the software systems we work on and within.
In this talk, we'll walk through postmortem techniques, pitfalls, and tools that you can take back to your own environments so you will be able to run healthy, productive postmortems which produces actionable outcomes and helps the company to move toward a so-called "learning organization."
J. Paul Reed has over fifteen years experience in the trenches as a build/release and tools engineer, working with such organizations as VMware, Mozilla, Postbox, Symantec, and Salesforce.
In 2012, he founded Release Engineering Approaches, a consultancy incorporating a host of tools and techniques to help organizations realize how they can "Simply Ship. Every time." He's worked across a number of industries, from financial services to cloud-based infrastructure to health care, with teams ranging from 2 to 2500 on everything from tooling, operational analysis and improvement, team culture transformation, and business value optimization. He regularly speaks internationally on release engineering, DevOps, IT operations complexity, and human factors.
Paul is also the founding host of The Ship Show, a twice-monthly podcast tackling topics related to build engineering, DevOps, and release management.
As a Tester the Ops team can seem grumpy and difficult to work with - is this actually your fault though? Your systems may be causing them pain and if you aren't aware of it you can't take steps to make their lives easier and your system more robust and stable. Is Your Ops Team Grumpy...? And Why You Should Care discusses how to give the Ops team the appropriate logging and monitoring that they need to be able to identify issues in production, report back and go to sleep instead of answering calls at 02:00.
Gwen Diagram is a Software Tester with a specialist interest in monitoring, logging and DevOps related fun. Occasionally works as a Scrummaster, App Support, Ops or DBA. Enjoys electronics, restoring British Leyland cars and beer in her free time outside of working at a Social Media Startup.
Join this session to learn how to create a Java-based microservice using Spring Boot, containerize it, and subsequently deploy a fleet of microservices and dependent components such as Redis using Kubernetes.
Spring Boot makes creating microservices fast and easy – when it comes to running a single instance. Like most Java applications, the harder part is usually the clustering and fail-over configurations.
First, we’ll go over how to get started with Spring Boot, and, subsequently, using Docker and/or Maven plugins to generate and create Docker images during the build process. Next, we'll push the container into a container repository.
Finally, with the images, we’ll deploy the microservice into Kubernetes:
The best part is – we can visualize all these activities happening in Kubernetes.
Ray Tsang is a developer advocate for the Google Cloud platform. Ray had extensive hands-on cross-industry enterprise systems integration delivery and management experience during his time at Accenture, managed full stack application development, DevOps, and ITOps. Ray specialized in middleware, big data, and PaaS products during his time at RedHat, while contributing to open source projects such as Infinispan. Aside from technology, Ray enjoys traveling and adventures.
Let's assume you’ve already had every *Docker 101 tutorial* for breakfast. You’re now ready to take that brilliantly crafted application into production. But wait... first you need to test your container-based microservices architecture. What does the whole DevOps workflow look like? What about performance and security? And last but not least; how the hell do I run my microservices in production, and will it scale?
Let Daniël guide you through the wonderful world of container-based development and running microservice architectures at scale. By attending the talk, you’ll gain insight into how to bootstrap and dive straight into learning what DevOps workflow should look like when using containers.
Daniël van Gils is a polyglot developer advocate at Cloud 66. He helps other polyglot developers craft ruby (on rails) web applications and container based microservice architectures with ♥, to deploy on any server or public cloud. He’s been involved in the web development, creative technologies, and gaming industries. An accomplished creative technologist, Daniel has vast and varied experience in application development, agile workflows, lecturing and building container technologies at scale. In his spare time he experiments with strawberries in his backyard, likes to surf and practices improvisation theater.
Failure is inevitable. We bend our destiny to the computer overlords and cope with the loss by leveraging crash-only software architectures.
This talk introduces the notion of crash-only software as a method to manage failures, by presenting the elements that make a crash only component and how those components communicate together. We approach some tradeoffs inherent to distributed systems and explain how crash-only architectures help us make the right decisions.
A French Canadian DigitalOcean engineer with the crazy idea to get rid of all his earthly possessions and live on a boat and sail the world. other things he is passionate about: meetings, meetings and more meetings.
Long term, he would like to sell his boat (which he doesn't have yet) to start a colony on Mars.
"If you're not in a meeting right now, you need to stop and ask yourself. What am I doing for this company." - Antoine
We are in the middle of a "fintech" revolution right now with much interest in the finance domain and how we can use technology to disrupt both incumbents and business models. This is even a conference about developing software in the finance domain. The question begs then, what makes finance special, if anything? And if it is special why do we care and what can we do about it?
Finance isn't just about developing technology with a few rules and regulations, it's about the complex interactions between people and systems and the events that have helped shape the global economy over the past decade. It's also a domain of contradictions. Corporations that drive the industry and help shape the technology are often hugely resilient to failure allowing bad practices to outlive their natural life. Similarly failure, when it does come, can be very costly, even catastrophic, with technology providers directly culpable.
Developing effectively in the domain of finance requires an appreciation of the wider context of the domain, where it is today and where it will lead in the future. Armed with that knowledge, and an understanding of why it's hard to develop effectively in a domain with hard, ever changing constraints it becomes possible to explore approaches that can help make sense of it all. One of the biggest problems encountered in finance is the mapping from some regulatory obligation all the way through to lines of code that actually provide that.
This talk will look at the problem of finance, where we are today, how we got here and how we might make sense of it all. Along the way we'll ask what things stand out and perhaps a pattern will emerge. Hopefully it will become clear that finance is challenging, but also rewarding. We get to solve real, hard problems with little room for compromise and get to push our tools and languages to their limits, in some cases driving their evolution.
Currently Director of clearpool.io – https://clearpool.io – Jamie is leading the development of a next generation exchange platform targeting MiFID II and emerging economies. Previously at the NYSE he was responsible for their market data platform and next generation projects. Impacted by the Flash Crash in 2010 he acted as a technical witness to the SEC. A member of the BSI C++ ISO Standards Panel and previous co-author of a best seller on C++ he enjoys getting his hands dirty in code. Recently he open-sourced cuppa, a python Scons-based build framework to simplify building complex C++ systems. Passionate about agile development, and a long time speaker on the topic, he particularly relishes helping distributed teams embrace agility.
Spotify has a highly distributed engineering organization with more than 80 autonomous teams and has been experiencing fast growth.
Matching the organization, the Spotify backend consists of hundreds of small services, each owned by one of the teams. Teams not only build their services, they fully operate them.
In this talk, you’ll learn how Spotify went from a small centralized operations team, to fully distributed operations and how that has enabled us to both grow as a company and constantly scale our backend to an ever growing number of users.
Niklas Gustavsson is a backend engineer at Spotify, open source hacker, mountain biker and father of two awesome kids. At Spotify, he has a long history of working on audio playback and content delivery.
Niklas tweets as @protocol7.
By now you’ve probably heard of BitCoin, the famous crypto-currency. Most people are aware that the critical foundational technology supporting BitCoin is called blockchain, which is a distributed record of digital events. Marc Andreesen, a prominent U.S. venture capitalist has called blockchain’s distributed consensus model as the most important invention since the Internet itself.
But how does BitCoin relate to blockchain and why are global banks investigating the use of blockchain in their applications? What problem does blockchain solve, what technologies does it use, why should you care? Why are a variety of industry sectors interested in this mechanism?
John will provide valuable information on blockchain, related technologies and implementations for you to make up your own mind. Explanations of how it works, who’s using it today, who might be interested in the coming months/years and why what it may mean to you.
John is co-founder and CTO of C24, a London based fast data company specialising in high-volume, low-latency complex messaging. With customers including many of the world’s largest investment banks, C24 provides data optimisation for standards like SWIFT, ISO-20022, FpML and FIX as well as proprietary formats. C24 has recently released a new data optimization product - PREON - that creates highly optimized binary versions of these complex messages reducing memory and network usage by over 20 times, while significantly increasing performance.
John has been global chief architect at JP Morgan, BNP Paribas and was the original architect behind Visa’s V.me (now Visa Checkout). John has co-authored several Java books and is a frequent speaker at technical and banking conferences around the world. He is married to a French wife and has 3 boys (12, 14 & 17) who all love travelling (as long as there’s internet).
A significant chunk of DevOps rhetoric centers around “unicorn” companies like Netflix, Etsy, Facebook and many more. They are held up as the models enterprises should emulate. But what makes a place like Netflix so special? What does life inside a unicorn company look like? Is the famous Netflix culture deck true to life or just hype? Most importantly, what lessons can I take back to my employer?
In this talk Mike McGarr, manager of Netflix Developer Productivity, will share with you the reality of working at Netflix. I’ll share details about how people work at Netflix, how we communicate, how we are organized, how work is prioritized, how we manage risk, how we build teams and how our culture plays a central role in everything we do. Lastly, Mike will share what are the important lessons that every manager and executive should learn about Netflix’s culture.
Mike McGarr is the Engineering Manager for the Netflix Developer Productivity team. He is also a co-host of the Ship Show Podcast. He has been developing Java/JVM-based applications for most of his career and been known to dabble in other languages as well. He is passionate about building quality software through automation. Mike can frequently be found talking about Agile, Continuous Delivery, DevOps, or build and test automation. Prior to joining Netflix, Mike was the Director of DevOps at Blackboard and the founder of the DC Continuous Delivery meetup.
Continuous Delivery is still trendy and everyone wants to get there, but there are so many walls you have to break and nerves to spoil! In this talk Eduards will present real-world battle stories of continuous delivery adoption, eight underlooked things that tend to go wrong and what practices can you apply in order to survive.
Eduards is a hands-on architect and software development coach who helps awesome teams around the globe become more awesome – work smarter, run faster and enjoy the journey. He leads Latvian Software Craftsmanship Community, blogs, speaks, and even sleeps. Sometimes.
Testing software is necessary, no matter the size or status of your company. Introducing Docker to your development workflow can help you write and run your testing frameworks more efficiently, so that you can always deliver your best product to your customers and there are no excuses for not writing tests anymore. You’ll walk away from this talk with practical advice for using Docker to run your test frameworks more efficiently, as well as some solid knowledge of software testing principles.
Laura Frank is a software engineer for Codeship. Based in Berlin, she works on developer tools to make developing and deploying code faster and easier.
In this session we shall look at some of the practical challenges in meeting the needs of compliance as it pertains to BCBS 239, MIFID and CCAR. All of these regulations are dominated by a need to demonstrate fidelity of data and process. In the case of BCBS 239 it is almost at a forensic level of showing data lineage and presenting it in terms the business and regulators can understand. In the case of CCAR it is showing the fidelity of a model that is stress tested against different market parameters and for MIFID it is both process and data.
In the last 5 years progress has been made in areas such as process mining and in harvesting data lineage. Coupled with semantic web technology now seen in the EDS’s Fibo standard and coupled with XML grammars such as XBRL (Business Reporting markup language) it is possible to deploy a tool chain and a supporting process to automate much of the gathering and initial analysis of data about data and data about running processes and forensically piece it all back together. Stitching in Fibo like glossaries takes us further in meeting the need for business relevance and at the same time ensuring timely delivery of compliance reports.
In this session we shall look at examples of these tools, demonstrate some of them and show what such a tool chain might look like in practice, how it can be used and what changes in terms of the data and process governance required to wield them in order to deliver something close to STP for compliance.
As a note to the future space we speculate on the role of blockchain as a system of records that could be established by regulators and banks alike to ensure trust between all parties is forever maintained. And we shall look at the relevance of forensic automation to help automate digital transformation from legacy to more modern architectures such as micro-services and the impact on delivery cycles and budgets.
The session will dive into some of the technical nuances that face us.
Steve has been at the forefront of technology since the early 1980’s when he wrote his first SQL compiler, the 1990’s when he built his first object database system, the mid 1990’s when he build the first ECA system that underpinned project HOODINI in the city and SpiritINTELLECT with SpiritSoft. In the 2005 he brought WS-CDL through as a standard from W3C having chaired all of the WS* standards for Sir Tim Berners Lee. And more recently his work on forensic IT and process mining through session types has found a home in compliance circles in driving both process and data lineage.
At LMAX Exchange our team of 20 developers change 30,000 lines of code every month, half our codebase is less than 17 months old and new features are delivered to production fortnightly. We handle 2 trillion dollars-worth of trading every year, so bugs or performance regressions in production can prove very costly. In order to support this workflow, we live and breathe Continuous Delivery - the concept was defined at LMAX and we have continued to improve and refine the process. This session will guide you through our incremental delivery pipeline and the techniques used to minimise bugs making it to production. We will offer practical advice on how to deliver, deploy, test and measure when you don't have the luxury of displaying a humorous 404 page.
Stefanos is a senior software engineer and team lead at LMAX Exchange in London - the pioneers of Continuous Delivery. His career has taken various twists and turns from academia via writing satellite software for the European Space Agency, flight search software for a major airline, test automation for various banks, and steam turbine design software, to his current role in writing low latency code that can process 50,000 orders a second on a single CPU core. His hobbies include iOS development, music and backpacking.
Getting started on AWS is easy, but building a scalable, reliable, and performant product in the cloud can be a challenge for startups and enterprises alike. Netflix has famously migrated all our services to the cloud. Along the way, we have open-sourced large portions of our platform that helped make this a reality. In this talk, Mike McGarr (Manager - Netflix Developer Productivity) will provide a survey of the Netflix OSS products available. Mike will also share patterns and lessons Netflix learned migrating to the cloud. This talk will cover tools such as Nebula, Aminator and Spinnaker. Lastly, Mike will leave you with a roadmap for how to get started with Netflix OSS on your cloud today.
Mike McGarr is the Engineering Manager for the Netflix Developer Productivity team. He is also a co-host of the Ship Show Podcast. He has been developing Java/JVM-based applications for most of his career and been known to dabble in other languages as well. He is passionate about building quality software through automation. Mike can frequently be found talking about Agile, Continuous Delivery, DevOps, or build and test automation. Prior to joining Netflix, Mike was the Director of DevOps at Blackboard and the founder of the DC Continuous Delivery meetup.
In this workshop, John Davies and Peter Lawrey will discuss with you an entire stack for high performing system integration, data persistence and analytics in distributed environments. The full-day experience will feature many hands-on exercises and plenty of opportunities to debate the details.
In the first half of the day, we will cover the following topics:
• Message Ontologies – FIX, FpML, MxML, ISO 20022, SWIFT MT & MX
• Enterprise Integration Architecture overview
• Message handling, content-based routing
• Using Spring Integration and Batch
• Canonicalization & Transformation
• Persistence options, SQL and NoSQL
• In-memory Data Grids and caching
• In-memory and distributed Analytics
• Serialisation and memory pressure issues – performance issues
• Distributed architectures
• Hadoop & Spark
• Microservices as they apply to Trading systems
The second half of the day will be hands on exercises in developing low latency micro-services and setup for deployment of these service to different cores within a server. We will:
• discuss the differences between micro-services and monolith architectures and their relative benefits and disadvantage. Is there a way we can get the best of both worlds?
• look at design patterns which will allow us to utilise these different strategies as a deployment concern without significant changes to the business logic
• look at how micro-service architecture can be implemented under low latency constraints of 10 – 100 micro-second latencies, in Java in particular. How do these strategies reduce the impact of serializing data and logging?
• look at integrating this solution with a websocket client in chrome to receive real time data to a Javascript client
Peter Lawrey has the most Java answers on StackOverflow, he is the founder of the Performance Java User's Group with over 1000 members, and the lead developer of OpenHFT, open source software used by Investment Banks, trading houses, and hedge funds.
John is co-founder and CTO of C24, a London based fast data company specialising in high-volume, low-latency complex messaging. With customers including many of the world’s largest investment banks, C24 provides data optimisation for standards like SWIFT, ISO-20022, FpML and FIX as well as proprietary formats. C24 has recently released a new data optimization product - PREON - that creates highly optimized binary versions of these complex messages reducing memory and network usage by over 20 times, while significantly increasing performance.
John has been global chief architect at JP Morgan, BNP Paribas and was the original architect behind Visa’s V.me (now Visa Checkout). John has co-authored several Java books and is a frequent speaker at technical and banking conferences around the world. He is married to a French wife and has 3 boys (12, 14 & 17) who all love travelling (as long as there’s internet).
Unfortunately this workshop is now fully booked!
In this workshop, Eduards Sizovs will share an insight into Continuous Delivery and how it can be implemented in an efficient and practical way. Additionally the workshop covers the dos and don’ts based on the experience of organizations of different sizes and in-depth information that will help all attendees to pursue their own journeys.
During this workshop, there will be many chances to understand Continuous Delivery through a real-world lens and to grasp the concept through the eyes of a professional.
This interactive training will cover a wide range of topics, including:
...and much more!
Eduards is a hands-on architect and software development coach who helps awesome teams around the globe become more awesome – work smarter, run faster and enjoy the journey. He leads Latvian Software Craftsmanship Community, blogs, speaks, and even sleeps. Sometimes.
The conference is up and running. Here’s my little selfie on stage while welcoming the crowd #jaxfinance #jaxdevops pic.twitter.com/ntIzWYcA56
— Sebastian Meyen (@smeyen) April 27, 2016
@jaxdevops learned a lot the past three days. Even as an OPS-guy.
— Marco van Dinter (@mvdinter) April 30, 2016
Another great presentation – on Docker and it’s applications in testing, by @rhein_wein, thanks #jaxfinance #jaxdevops
— Dean Pullen (@deanpullendev) April 28, 2016
Getting ready to speak @jaxfinance #jaxfinance pic.twitter.com/K8jqbENR74
— Neil Horlock (@_zyxt_) April 28, 2016
Google, Spotify, and Netflix in one day #jaxdevops #jaxfinance
— Dean Pullen (@deanpullendev) April 28, 2016
#jaxdevops fist day after party! @eduardsi @severvam @teamcity pic.twitter.com/j5ojHqS7Ud
— Alla Babkina (@allababkina) April 27, 2016
Never heard of crash-only design before today at #jaxdevops. #Testing a system with no stop/start/restart ability? Interesting problem!
— Ash Winter (@northern_tester) April 28, 2016
.@SonOfGarr ready to rock @jaxlondon next; think you know everything about @netflix‘s unicorn culture?
You sure? pic.twitter.com/UuxFhzcADi
— J. Paul Reed (@jpaulreed) April 28, 2016