![]() ![]() With that basic outline out of the way, lets get stuck in. Handling API calls to cloud vendor services locally.The ability to execute and debug code locally in a repeatable way.What is it we want to accomplish in this article? Lets start with a list of items that we should hopefully have some answers for. It doesn't make any one right or wrong we are all still working out the best ways to accomplish our goals. There will be others with other ideas about how to accomplish the same thing. With Serverless as a development methodology still in its infancy, the ideas expressed here are my own opinion born out of experience building multiple Serverless projects solo and with teams. By the end of this post we should understand how we can reclaim to a large degree the ability we have always had to develop our applications on our local machines but still set us up for integrating our services into a larger team. But it still means we need to figure out what the new dev workflow looks like in a Serverless microservice world. Serverless arrived to help ease that infrastructure burden that building an application consisting of many small services adds. Then microservices came along and things have dramatically changed. Boy does this make development easier if you can just play around with the app as you build it without even requiring access to the Internet. ![]() We've gotten used to having awesome local tooling for us to essentially run our entire application on our local machine. Developing Serverless applications is a very different way of building applications we've been building for decades now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |