Abstract: Functional-first programming is now a standard technique in the software industry. But what does it mean to succeed with functional-first programming in real business situations? What sort of business problems is it applicable to, and why do those problems matter? What sort of benefits can you expect if you adopt functional-first programming? How do the business needs map through to features of languages such as F#? In this talk, we’ll take a fun walkthrough case studies, observations, anecdotes and hard-nosed revenue figures to answer these questions.
The service architecture of the new millenium has evolved at the Forward Internet Group into a myriad of small, loosely coupled services. While the system is several years old, almost no service is older than six months. We explore the evolution of this architecture and its impact on the organization and processes.
MicroService Architecture adroitly exploits cloud environments. In this session, we will address the lessons learned in 3 companies (so far). The lessons cover overcoming the programmer bias to build "big" services; asynchronous vs. synchronous service flows; successful languages, environments, and frameworks; and impact on development processes. Also addressed is the necessary shift from acceptance test to active system monitoring of business KPI's.
Today's applications are systems, not large applications. They consist of smaller, singly-focused services, usually connected over REST. To achieve maximum velocity, services today are continuously deployed and integrated. Services need to slot into the system with ease, they need to be secure, and they need to be open, transparent. In this talk, join Spring Developer Advocate Josh Long (twitter.com/starbuxman) for a look at how to build smart, REST and hypermedia-ready, OAuth-secured microservices with Spring Boot.
This talk covers some concrete, practical advice for people building, or considering building, microservice arcitectures.
So you’ve heard about the buzz behind Microservices and finer-grained architectures in general? Microservice architectures can lead to easier to change, more maintainable systems which can be more secure, performant and stable than previous designs.
But what are the practical concerns associated with running more fine-grained systems, and what are the new things you’ll need to know if you want to embrace the power of smaller services without the new sources of complexity making your life a nightmare?
This talk will delve deeper into the characteristics of well-behaved services, and will define some clear principles your services should follow. It will also discuss in more depth some of the challenges associated with managing and monitoring more complex distributed systems. We’ll discuss how you can design services to be more fault-tolerant, what technologies may exist in your own platform to get you started. We’ll end by giving some pointers as to when you should consider microservice architectures, and how you should go about introducing them in your own organisation.
This talk gives practical advice to help you adopt Microservice architectures in your own organisations, based on real-world experience of building similar systems gathered from all over the industry.
Sam Newman is a technologist at ThoughtWorks, where he currently splits his time between encouraging and sharing Innovation globally and helping design and build their internal systems. He has worked with a variety of companies in multiple domains around the world, often with one foot in the developer world, and another in the IT operations space. If you asked him what he does, he’d say ‘I work with people to build better software systems’. He has written articles, presented at conferences, and sporadically commits to open source projects. He is currently writing a book on building Microservices, which should be available in the Autumn of this year from O'Reilly.