Track: Sponsored Solutions Track I
Location: Shubert - Uris, 6th fl.
Day of week:
Track Host: Nitin Bharti
Over the last decade, Nitin has helped build several notable online developer communities including TheServerSide.com, DZone, and The Code Project. He is known for his extensive editorial work in the Enterprise Java, .NET, SOA, and Agile communities. As Managing Editor and Product Manager at C4Media - the producer of InfoQ.com and QCon events - Nitin continues to pursue his primary passion: helping spread knowledge and innovation throughout the enterprise software development community.
Data-Driven Off A Cliff
Metrics and analytics are crucial for building successful products at scale. Data is powerful. However, the room for misuse is significant — hence the cliche about lies, damned lies, and statistics. In this talk, we explored some of the ways you can use data to drive yourself right off a cliff. Specifically, we talked about anti-patterns in evidence-based decision making, meaning we described exactly what not to do with your data.
Engineer Innovation Through Rapid Prototyping
Even the best ideas need to be shaped and refined to succeed in the market. Hatchery, Vistaprint's innovation lab, launched many products and services since being formed two years ago and we've refined our process for developing innovative products. We'll walk through how Hatchery generates ideas and uses rapid prototyping to make progress in the face of uncertainty.
I Have A NoSQL toaster
NoSQL is a catch-all term that covers a lot of different types of data storage. Is it really helpful to group them together by one thing they don't have? Think about it like this: my toaster is as much NoSQL as any database! So, how can we make more sense of this new breed of database management systems?
In this talk I cover the four main data models that have been part of the past ten years' NoSQL movement: key-value, document, columnar and graph. I explain how they differ and when you might want to use each one.
Design Systems for Developer Communication
Designers and developers build better products when they communicate with a common language. A Design System defines a common language–the words, phrases and rules of composition–used to describe content, visual design and interactions. Learn how designer/developer collaboration led to a set of principles and patterns for defining Design Systems.
When Microservices Meet Event Sourcing
Microservices are becoming quite a popular architectural pattern, both in the development of brand new systems and when decomposing legacy monoliths into smaller independent modules. However, the typical microservices approach based on HTTP and REST brings with it critical cross-functional challenges for performance, data consistency, and even the HTTP protocol when it comes to describing complex user interactions. The fundamental idea of event sourcing is to describe the state of the system: instead of storing only the current state (as most traditional systems would do) event sourcing stores a sequence of immutable events describing everything that has happened so far. Typically, those events are caused by the execution of commands, which represent the user’s intent.
Events can be published and consumed by other services and used to build query-friendly representations of the aggregated state. When microservices are combined with event sourcing, services no longer need to communicate with each other explicitly and synchronously. Instead, they exchange information indirectly through event publishing/subscribing, which enables those services to be almost completely unaware of the existence of each other, since the events are now the only contract needed. At the same time, the persistence of the event history enables us to be flexible when it comes to answer time-based business queries and accommodate future requirements without impacting many components in the system at once. Vinicius Gomes explains how the combination of microservices and event sourcing helped his team successfully build and evolve a banking services platform.
You’ll learn details of this architectural style in comparison to the traditional HTTP/REST approach, its benefits and challenges, and the first steps on the practical implementation.
Along the way, Vinicius introduces the most important concepts and components, like the event store, event listeners, command handlers, and aggregates and outlines the first steps to their practical implementation. Vinicius also discusses the different levels of testing on this architecture and the most relevant challenges his team has faced so far before sharing a live demo.
DevOps @Scale
As in a good Greek Tragedy, scaling devops to big teams has 3 stages and usually end badly. In this play (it’s more than a talk!) we’ll present you with Pentagon Inc, and their way to scaling devops from a team of 3 engineers to a team of 100 (spoiler – it’s painful!)