Hi, Hmmm... It seems that [2] is just a marketing page that doesn't give any arguments about the micronaut.
Anyway, security is a good point. Aleksandr, could you please add some note to the IEP about security related value of the micronaut framework? On Thu, May 26, 2022 at 9:48 AM Mikhail Pochatkin <mpochat...@unison.team> wrote: > > Hello Igniters. > > I see that the main argument against Micronaut is that we need > Micronaut+Swagger to achieve IEP 87 if we can use only Swagger. I agree > this is a valid point and logically. But I think we can take a look into it > from another side, from future vision. Main idea to start using micronaut > to simplify code writing in future just because Micronaut Framework really > helps to develop REST services in practice. For example, I think it's > obvious that Ignite will need to implement some authentication mechanism > and Micronaut can help to achieve it [1]. Moreover Micronaut is based on > the same technology which is currently used in Ignite, I mean Netty. It > means that we should speak only about vulnerabilities inside of Micronaut > implementation, but the Micronaut project has a very big community and a > lot of clients. In context of it I would say that bugs and vulnerabilities > in Micronaut implementation will be found more quickly than in internal > Ignite implementation with pure Netty. Another point about cloud native > support [2] which also can be useful in the context of Ignite. > > [1] https://micronaut-projects.github.io/micronaut-security/latest/guide/ > [2] https://objectcomputing.com/expertise/cloud-engineering > > On Wed, May 25, 2022 at 6:45 PM Andrey Gura <ag...@apache.org> wrote: > > > Why couldn't the handlers be annotated? > > > > I think Kirill Gusakov (as the feature contributor) can give some > > ideas about what and how should be annotated. This may require some > > tweaking. > > > > On Wed, May 25, 2022 at 6:06 PM Aleksandr Pakhomov <apk...@gmail.com> > > wrote: > > > > > > Hi Alexander, > > > > > > Yes, swagger allows to annotate classes > > > and then the spec will be generated. But > > > here is a question. What classes should we > > > annotade? > > > > > > Web framework brings the convention about > > > how to write an endpoint and what to annotate. > > > Our own REST server implementation does not. > > > It is just the number of handlers. > > > > > > > On 25 May 2022, at 17:46, Alexander Polovtcev <alexpolovt...@gmail.com> > > wrote: > > > > > > > > Aleksandr, > > > > > > > > Can we use these annotations without the micronaut dependencies? If > > yes, > > > > why do we need micronaut at all? > > > > > > > > On Mon, May 23, 2022 at 5:34 PM Aleksandr Pakhomov <apk...@gmail.com> > > wrote: > > > > > > > >> Yes, swagger-core has its own set of annotations [1] > > > >> > > > >> [1] > > > >> > > https://github.com/swagger-api/swagger-core/wiki/Swagger-2.X---Annotations#quick-annotation-overview > > > >> > > > >>> On 23 May 2022, at 12:37, Alexander Polovtcev < > > alexpolovt...@gmail.com> > > > >> wrote: > > > >>> > > > >>> I'm not that scared of having a big library, I just believe that it > > might > > > >>> be possible to avoid using it altogether. Don't swagger generators > > have > > > >>> their own annotations? > > > >> > > > >> > > > > > > > > >
