Before you build anything planning is required. This series talks about what is needed before building any API be it talking to design teams to understand the user experience or building an optimized API to deliver faster experiences to the end customer. These are basic essentials which needs to be planned properly.
6 posts
Microservices I: Pre-Development Before developing, we first need to finalize the web framework that should be used. Go has a number of frameworks that are production-ready. This post considers a few of them before deciding on one. Microservices I: Pre-Development Every application will eventually require a database to persist all the important data. In this post, we’ll be designing a simple data model for our application and set up a relational or SQL database (Postgres) for further development. Microservices I: Pre-Development Before developing microservices, it’s advisable to define APIs first clearly stating the request and the response. And for REST APIs, Open API Specification is the way to go. This post details defining of APIs with OAS and Swagger Microservices I: Pre-Development So here’s the deal. When developing any software application, coding is never your first step. Never! Don’… Microservices I: Pre-Development APIs or Application Protocol Interfaces are the heart of microservices. They like a contract to exchange data between two software systems. This post covers basic concepts of web API, REST, HTTP and also provides some pointers for designing good APIs. Microservices I: Pre-Development The first step during application development is designing. We define flows to understand how data needs to be fetched and stored from the UI which, in turn, helps in database and service design. In this post, we are going to define a basic flow for our pet adoption store application.