Presentation Duration: Two Hours
If you’re in the enterprise, it is common to wonder how long your current technology stack going to last.
We encourage our clients to assume that change is going to happen, and to proactively put in place a decoupled system architecture that provides a smaller surface area of change for your applications in the future.
What can help this proactivity come to pass is Microservices. This style of architecture breaks up application function into smaller independent units that are accessed and discovered at runtime, whether over HTTP or a IP/Socket protocol using RESTful APIs. These services are made immutable through operating system containers that allow these services, with all of their required software, to be packaged up in a nice image, moved to servers, and stopped, started, and discovered by other services.
In this breakfast presentation, we will delve into Microservices architecture, assess the pros and cons, and help the audience to better understand if this architectural approach is a good fit for their application development needs.
- An overview of how Microservices is approached from an architectural perspective
- A comparison of Microservices to traditional Monolithic applications, SOA, and distributed computing
- When best to consider Microservices (and when to avoid)
- Suggestions for successful implementation
- A reference application that will walk through implementations of some common Microservice patterns such as Service Discovery, Circuit Breaker, and Api Gateway