Microservices are all the rage now, and monolithic applications ("monoliths") are old school. So it makes perfect sense to ditch the monoliths completely and go straight for microservices, right? Not to Mike Gehard, it doesn't, especially for new projects. A software engineer at Pivotal, Mike says that for startups who don't yet know what their business is, microservices may box them in unnecessarily. He advocates for starting with a monolith before moving to microservices--in three easy steps (at least MIke makes them seem easy). The assumption going into the monolith, however, is that it's structured in such a way that moving over to microservices in the future is feasible and easy. SolutionsIQ's Alan Dayley hosts at Agile2016 in Atlanta, GA. About Agile Amped The Agile Amped podcast series connects the community through compelling stories, passionate people, shared knowledge, and innovative ideas. Fueled by inspiring conversations with industry thoughtleaders, Agile Amped offers valuable content – anytime, anywhere. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com. Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter  Like: http://bit.ly/SIQFacebook