I'm glad you found the other answers useful, but I was still left wondering why someone would want a large full-featured framework dedicated to microservices when there are already three large full-featured frameworks for webapps which can each comfortably be used to write a microservice.
Nobody in perl is ever going to produce a dedicated microservice framework if they don't know what they're missing. If you were able to describe how SpringBoot is an improvement over other web frameworks you've used, and why its focus on microservices makes it worth learning an entire framework just for that, that would enlighten us as to why you care so much about this distinction.
Most likely, the answers we would have to that description would be to tell you about modules or configurations for the popular web frameworks that would deliver the same features that you like about SpringBoot. Or, personal anecdotes about microservices we've developed and how we tailored a web service to that purpose. Or, maybe we would see a gap in the feature set of our frameworks that we hadn't seen before, and be inspired to write a module for that. (likely yet another extension of Mojo or Catalyst or Dancer, because nobody has time to invent an entire new framework, nor would anyone else want to spend the time to learn one)
If you're not willing to get involved in a tech stack that hadn't been specifically designed for your exact use case, then that's your choice to make; each of us has limited waking hours, and work to get done, and it makes sense to choose the best tool for the job. But you did kind of leave us guessing with your post.
| [reply] |
I wanted to narrow down the choices but did not know how microservices were done in Perl.
Spring Boot was used as an example and to convey a gist. (Other people ask similar questions with the same motive eg. this
user's reddit post) (I like the à la carte versus kitchen sink analogy and believe the former is more anologous to Perl's approach).
I am seeking uniformity and alignment with the technology direction my company is focused on and for political reasons I prefer not to use a web framework for developing microservices. The sooner I can wrap an API around the Perl parts of the system the sooner I can move on.
As long as the Perl implementation is not awkward I will not have a problem with it.
| [reply] |