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 you
Organization mode- you can access the applications that belong to the currently selected organization
Let’s look at how to use organizations.
You use the top-right dropdown to create an 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.
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
You can change the ownership of an application from yourself to an organization or vice versa using the
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 classes and workshops.
In June, I’ll be teaching a public microservices workshopover Zoom in an APAC-friendly (GMT+9) timezone.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
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 YXEERWTJ to sign up for $195 (valid until May 26th, 2022). There are deeper discounts for buying multiple seats.
Chris offers numerous resources for learning the microservice architecture.
Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help 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.
Delivered in-person and remotely.
Want to see an example? Check out Chris Richardson's example applications. See code
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.
Join the microservices google group
Application architecture patterns
Refactoring to microservicesnew
Cross cutting concerns