We are pleased to announce that the Microservices assessment platform now implements organizations. Organizations enable you to collaborate with your colleagues to assess your application’s microservice architecture and view the results of the assessment.
With the introduction of organizations, applications (along with the assessments and services etc.) belong to either an individual or an organization.
When you are logged in, the user interface is in one of two modes:
Personal mode
- you can access the applications that belong to youOrganization mode
- you can access the applications that belong to the currently selected organizationLet’s look at how to use organizations.
You use the top-right dropdown to create an organization.
First, select Create Organization..
:
Second, enter the name of the new organization.
The newly created organization becomes the current organization. Since no applications are owned by the organization, the list of applications is empty. You can now create applications that are accessible by others in the organization. Alternatively, as I’ll show you later, you can move applications that you created previously to this organization.
You can use the top-right dropdown to invite users to current organization.
First, select Invite User...
:
Then, enter the email address of the person you want to invite,
The Assessment Platform will send that person an invitation email. If they are not a registered user, they can signup before accepting the invitation.
You can use the top-right dropdown to switch between organizations and personal mode.
Select the organization or Personal Mode
:
You can change the ownership of an application from yourself to an organization or vice versa using the Change Ownership
.
If you are in personal mode, you can change the ownership of your application to an organization.
If you are in organization mode, you can change the ownership of an application to a different organization or yourself.
To do so, select the new owner from the popup window:
This will change the owner of the application, along with its services and assessments.
We hope that you will find this feature useful. Please don’t hesitate to contact us.
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.
Learn moreChris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon RESVJCMC to sign up for $95 (valid until September 26th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
Microservices adoption · ancient lore · anti-patterns · application api · application architecture · architecting · architecture · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · developer experience · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · modular monolith · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service architecture · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging
Application architecture patterns
Decomposition
Refactoring to microservicesnew
Data management
Transactional messaging
Testing
Deployment patterns
Cross cutting concerns
Communication style
External API
Service discovery
Reliability
Security
Observability
UI patterns