article thumbnail

Polyglot persistence vs multi-model databases for microservices

CircleCI

Microservice architecture is an application system design pattern in which an entire business application is composed of individual functional scoped services, which can scale on demand. These features have made microservices architecture a popular choice for enterprises. Database management challenges for microservices.

article thumbnail

EventStorming Modelling Tips to Facilitate Microservice Design

Strategic Tech

The result is that we create better designed software systems and teams of problem solvers rather than order takers. Used judiciously, EventStorming gives us the ability to uncover enough information about our domain and our business that we can use it to design our microservices, bounded contexts, and even our teams.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

The software engineering rule of 3

Erik Bernhardsson

Here’s a dumb extremely accurate rule I’m postulating* for software engineering projects: you need at least 3 examples before you solve the right problem. Example plz. The same reasoning applies to system design but with a very different conclusion. As an example, Luigi was the third attempt at solving the problem.

article thumbnail

Craig St. Jean, From Young Programmer to Chief Technology Architect

Xebia

I went from having fun writing small command line utilities with no thought to how the application was designed to needing to understand the ramifications and testing rigor required to change just one small thing in one library that many critical systems depended on. While there, my career grew quite extensively.

article thumbnail

Consumer-driven Coupling: Patterns and Anti-patterns

Strategic Tech

Organisations maximising the advantages provided by microservices tend to be organisations which view microservices not just as a technical tool, but a sociotechnical tool.The way software systems are shaped determines the communication paths and the coupling between development teams. The rules were moderately intricate.

article thumbnail

The software engineering rule of 3

Erik Bernhardsson

Here’s a dumb extremely accurate rule I’m postulating* for software engineering projects: you need at least 3 examples before you solve the right problem. Example plz. The same reasoning applies to system design but with a very different conclusion. As an example, Luigi was the third attempt at solving the problem.

article thumbnail

New live online training courses

O'Reilly Media - Ideas

Get hands-on training in Docker, microservices, cloud native, Python, machine learning, and many other topics. Pythonic design patterns , June 27. Learning Python 3 by Example , July 1. Microservices Architecture and Design , July 8-9. Domain-driven design and event-driven microservices , July 23-24.

Course 66