Subscribing to a range of topics per instance of a service
If I have a system where my distributed service is sending live scores of 1000s of football games from some hypothetical event to millions of clients. The service subscribes to the games from a source service that publishes the scores. The source publish happens over the id of the game i.e. each game is published on a different topic that my service subscribes to.
Subscribing to a range of topics per instance of a service
If I have a system where my distributed service is sending live scores of 1000s of football games from some hypothetical event to millions of clients. The service subscribes to the games from a source service that publishes the scores. The source publish happens over the id of the game i.e. each game is published on a different topic that my service subscribes to.
Spring/Java multiple shared modules for different databases
I’m implementing a software based on the micro-service architecture using Spring/Java. Each micro-service connects to either a PostgreSQL or a MongoDB database. Is it standard practice to have a shared module that contains database-agnostic components (e.g. entity classes, models, and common repository/service interfaces used by both databases) and then have two other shared modules (one for Postgres and the other for MongoDB) importing the first shared module and implement database-specific implementation of those common components?
How to maintain dependencies shared among microservices?
There is a dependency jar containing tons of service classes mostly used to retrieve data from database, and this jar is used among several different micro services in one cluster.
Muti-tenant Webapp Setup Defaults and Configurations
I have a multi tenant webapp. When a new tenant is created there is a bunch of defaults and configurations that need to be created in the DB for the new tenant, so of these inserts are related to each other and must happen in a specific order so I can get the ID of the related item. Here is an short version of what needs to happen
Encapsulating a central soap service in a microservice?
I am currently developing an application (rest-backend and SPA) that requires information from people (personal data, department, superior… ). Our company has a central directory for this purpose. This provides the data via soap.
Why is it so bad to read data from a database “owned” by a different microservice
I have recently read this excellent article on the microservice architecture: http://www.infoq.com/articles/microservices-intro
Decentralized Data Management – encapsulating databases into microservices [closed]
Closed 9 years ago.
Decentralized Data Management – encapsulating databases into microservices [closed]
Closed 9 years ago.
How to access large amounts of data for machine learning in a microservices architecture
Imagine you are building a product recommendation algorithm for an eccommerce application which is built as a microservices architecture, this architecture having separate services for users and products. The algorithm should be exposed as a recommendation service which, given a user id, returns a list of recommended products based on their buying history.