When you think about microservices, you probably think of open-ended services supporting user facing applications like Netflix or Uber. These services must be "always-on." There's no finish line. Some call these streaming services. But not all microservices fall into this category. Some microservices are finite - they have a beginning and a definitive end. Microservices supporting batch data integration jobs fall into this category. So do those supporting database migrations. These microservices shut down after the job is accomplished.
Finite microservices like these have their own set of development and deployment requirements and challenges that set them apart from streaming microservices. In this episode of Pivotal Insights, host Jeff Kelly speaks with Michael Minella, project lead for Spring Cloud Task at Pivotal. The two discuss what differentiates finite microservices from their streaming counterparts, identify the unique challenges associated with developing and deploying them, and offers tips for overcoming these challenges with Spring Cloud Task.
News and Resources
- Go deeper on finite microservices with this presentation Task Madeness - Modern On-Demand Processing by Minella
- Watch this presentation from Minella on Data Microservices with Spring Cloud Stream, Task and Data Flow
- Download and get started with Spring Cloud Task on its open source project page and visit Spring Cloud Task on GitHub
About the AuthorFollow on Twitter Follow on Linkedin More Content by Jeff Kelly