5 Ideas For Writing Better Cloud Native Microservices
Presented by: Todd Sharp
In theory, microservices are easy. The promise of loosely coupled, scalable services that can each be independently built, tested and deployed sounds amazing, doesn’t it? On top of that, each service can be written in whatever language the development deems appropriate – using their framework of choice – without any consequence to the rest of the architecture. Java services mixed with Node, Go, Ruby with each potentially persisting data to a different datastore. Maybe the Java service uses a key/value store?Perhaps the Go service persists to a traditional RDBMS? The future has truly arrived.
But in reality, microservices can present a new set of challenges for developers. Things that used to be easy like simple queries that join data from multiple sources are now handled differently. Tried and true concepts like transactions, referential integrity and DRY no longer mean as much when it comes to microservices. This new way of thinking can be difficult to grasp for some developers.
In this session, I'll show you some new ideas that you may not be familiar with that will help you develop performant microservices that are easy to maintain. Some of what we'll cover will look at new ways to solve some of challenges that microservice development brings and we'll discuss the benefits and downsides of each approach. I'll deploy a simple set of microservices using several languages and frameworks and we'll look at how to share data between the individual services and create a service that combines the data from multiple sources into a single feed of data. We'll also touch on other cloud native features that fit into your microservice application like serverless functions and cloud events.