Once the pre-development checklists are marked, we start with building the API’s. During this step we assume that design and data interfaces are decided so that engineering teams can start development. Any subsequent change in design and API design will involve updates to the underlying process as well.
6 posts
Microservices II: Basic Microservices Development The Rest layer is the one we call the “User facing” layer. Because it is the one that accepts the user’s requests and returns the appropriate responses. Looking at it technically, we implement all the REST API routes in this layer The service layer is where most of the business logic goes in. It acts as an aggregator of data by calling the required repo functions and adds additional logic which may be required to transform the data. In this post, we are going to implement the service layer Databases are ever-present in microservices. In the previous part, we defined domain models. In this post, we will focus on interacting with the database by using the models. Microservices II: Basic Microservices Development An application usually revolves around a “domain”. We usually start with the defining “models” of the domain and the actions that need to be performed on/by these models. In this post, we’ll be defining these using Go structs and interfaces. Microservices II: Basic Microservices Development Before developing, we need to decide on the code organization and repository structure. Always create a skeleton structure of folders that will act as a foundation for further code development if you want to avoid frequent refactors. Microservices II: Basic Microservices Development Flex your fingers everyone ’cause we are about to code! We’re done with step 1, which covered…