Community Picks·4yTop 10 Microservices Design Patterns and Principles
Microservice architecture is structured on the business domain and it's a collection of small autonomous services. Transaction management is the fundamental advantage of a shared database versus a per-service database. Event Sourcing is based on the idea that any change in an entity's state should be captured by the system. The persistence of a business item is accomplished by storing a series of state-changing events.
Hashnode·4yLearn how to build a microservice using Node.js and RabbitMQ.
Learn how to build a microservice using Node.js and RabbitMQ. This tutorial will teach you about microservices and how to create a simple e-commerce microservice architecture with two services; product and order. In the following section, we will look at some of the prerequisites for this tutorial. Make another folder for the routes, call it routes, then inside it, have a file routes.
Foojay.io·4yBackend-for-Frontend: The Demo
The monolith offers an endpoint for each data source, and a single aggregating endpoint for all of them. In the previous section, we developed a dedicated backend-for-frontend application. In this case, the gateway can be seen as a container where to deploy BFF plugins. I'll be using Apache APISIX to demo how to do it, but the idea can be replicated on other gateways as well.
DZone·4ySimplify Your Microservices Architecture: Data API
The data API gateway takes on the responsibility of managing data persistence for hotels, rates, inventory, and other data types. Data types can be added to the gateway by providing a schema or data model. Document-style endpoints can provide a "schema-less" experience in which any valid JSON document can be stored, such as a hotel description.
Discover .NET·4yShared Database between Services? Maybe!
Is a shared database a good or bad idea when working in a large system that's decomposed of many different services? Or should every service have its own database? My answer is yes and no, but it’s all about data ownership. Using a local cache when executing a command means using stale data.
Permit.io·4yThe four mistakes you make building permissions
Developers often overuse JWTs, sometimes going as far as storing all the routes that a user should access within them. Mixing the authentication and authorization layers messes up our code. The best way to avoid this is to have the JWT only include the claims and scopes for the user's identity and their relationship within the organization and keep all other authorization-related information.