How I designed a microservice unknowingly.
Once in a while, I was so focused in creating a CMS for a blog web app and created two applications one for the public view and one for the admin view. Both the application used a single centralized database, but they were separated in two different independent domains. My primary aim was to revoke access to the admin panel from anonymous users. And attempt to login the admin acesss, oftenly user tries /login, wp-admin, dashboard or more other common terminologies.
So what I did was I separated the view in www.view.com and served the admin view in www.admin.view.com
After a couple of years, when I joined my first job, I was introduced with a term called microservice. So when going through a couple of article and thinking hard, I realized this is something I have done without knowing the primary architecture.
Dear software engineers nothing is ever wrong, you might always be doing it right unknowingly, it’s only that you weren’t known about the technology.
For knowing about the microservice please go through the Microservice design at medium for complete detail about microservice.