[Apiman-user] Production Upgrade Recommendation

[Marc Savy]

You can mix and match. In fact, we recommend you keep using ES for metrics
as this provides you flexibility to integrate with a variety of visualisers.

On Thursday, April 26, 2018, Ashish Patel <ashish.patel at futuregroup.in>
wrote:

> Cool, thanks very much Marc, this shall be very helpful.
>
> Just one quick confirmation: The statement "apiman-gateway.metrics=io.
> apiman.gateway.engine.jdbc.JdbcMetrics" means if we use Gateway through
> JDBC the metrics shall also be updated in JDBC DB and not in ES. We can't
> have Gateway reading API definitions from DB and storing Metrics in ES - is
> this understanding correct or am I again missing something ?
>
> Thanks & Regards,
> Ashish Patel
>
> -----Original Message-----
> From: apiman-user-bounces at lists.jboss.org [mailto:
> apiman-user-bounces at lists.jboss.org] On Behalf Of Marc Savy
> Sent: Wednesday, April 25, 2018 21:10
> To: Ashish Patel
> Cc: apiman-user at lists.jboss.org
> Subject: Re: [Apiman-user] Production Upgrade Recommendation
>
> Yes, you can have the gateway on a different storage. Here's JDBC:
>
> https://apiman.gitbooks.io/apiman-installation-guide/
> installation-guide/registries-and-components/jdbc.html
>
> Here are some DDLs to get you started (if needed for your deployment)
> https://github.com/apiman/apiman/tree/master/distro/
> data/src/main/resources/ddls
>
> On 17 April 2018 at 12:26, Ashish Patel <ashish.patel at futuregroup.in>
> wrote:
> > Thanks Marc.
> >
> > Got it, we have ES working as metrics and gateway storage. However
> > from apiman.properties file can't find specific config where it
> > mentions that ES is being used as storage as well
> > (apiman-gateway.metrics.*)
> >
> > Is it possible to have Gateway storage different than ES ? i.e. say
> another MySQL schema ? if yes, how can we configure it - tried checking
> production guide/Installation guide but couldn't locate it.
> >
> > Thanks & Regards,
> > Ashish Patel
> >
> > -----Original Message-----
> > From: Marc Savy [mailto:marc.savy at redhat.com]
> > Sent: Tuesday, April 17, 2018 01:29
> > To: Ashish Patel
> > Cc: apiman-user at lists.jboss.org
> > Subject: Re: [Apiman-user] Production Upgrade Recommendation
> >
> > Hi Ashish,
> >
> > The datastore of the gateway can be separate from the manager (it
> > *can* be the same, but does not need to be).
> >
> > This means that even if the manager goes down, or a particular gateway
> instance goes down, as long as a given gateway's datastore is still
> available then they should keep running.
> >
> > The flow is as follows:
> >
> > 1. The user publishes an API/Client in the Apiman Manager. This causes a
> push to the gateway API.
> > 2. The gateway API receives and inserts the information into the gateway
> datastore, which is shared with the other nodes in its cluster/group.
> > 3. When traffic hits the gateway, the gateway looks into the *gateway*
> datastore, not the manager.
> >
> > Hope this is clear?
> >
> > Regards,
> > Marc
> >
> > On 12 April 2018 at 08:50, Ashish Patel <ashish.patel at futuregroup.in>
> wrote:
> >> Thanks Marc.
> >>
> >> We also want to configure the HA for APIMan Gateway. Referred
> https://apiman.gitbooks.io/apiman-production-guide/ and have one quick
> question - may sound silly. How each APIMan Gateway servers (under HA) gets
> the updated configs from APIMan Manager ? as in APIMan Manager, shall be
> configuring the HA Server's URL and that will redirect to any one of the
> underlying APIGateway servers - can you please help me understand the HA
> architecture.
> >>
> >> Thanks & Regards,
> >> Ashish Patel
> >>
> >> -----Original Message-----
> >> From: Marc Savy [mailto:marc.savy at redhat.com]
> >> Sent: Monday, April 09, 2018 16:19
> >> To: Ashish Patel
> >> Cc: apiman-user at lists.jboss.org
> >> Subject: Re: [Apiman-user] Production Upgrade Recommendation
> >>
> >> Hi Ashish,
> >>
> >> Yes, Vert.x should be your best option for performance, but you should
> give it test in a staging environment to ensure it works without any issues
> for your environment.
> >>
> >> Any of the community using Vert.x in production want to add any
> comments?
> >>
> >> Regards,
> >> Marc
> >>
> >> On 5 April 2018 at 07:07, Ashish Patel <ashish.patel at futuregroup.in>
> wrote:
> >>> Hi,
> >>>
> >>>
> >>> Currently we are in production with APIMan 1.2.7.Final with Willdfly
> >>> 10 (both APImanUI and APImanGateway, Keycloak on separate server).
> >>> We are planning to upgrade to latest version 1.3.1.Final and need
> >>> recommendation on deployment strategy. As per Download page we have
> >>> following options  (please add if any missed).
> >>>
> >>>
> >>>
> >>> For Upgrading from APIman 1.2.7 to APIman 1.3.1
> >>>
> >>>
> >>>
> >>> 1.       APImanUI and APImanGateway both on Wildfly 10 .
> >>>
> >>> 2.       #1 deployment through Docker.
> >>>
> >>> 3.       APImanUI and APImanGateway both on Tomcat8+
> >>>
> >>> 4.       APImanUI on Wildfly10 and APIGateway on Vert.x
> >>>
> >>>
> >>>
> >>> Looking for stable and high throughput deployment choice – as per my
> >>> limited knowledge #4 would be the best – however I may be wrong
> >>> based on actual usage. Appreciate the feedback.
> >>>
> >>>
> >>>
> >>> Thanks in advance.
> >>>
> >>>
> >>>
> >>> Thanks & Regards,
> >>>
> >>> Ashish Patel
> >>>
> >>>
> >>> _______________________________________________
> >>> Apiman-user mailing list
> >>> Apiman-user at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/apiman-user
> >>>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>


-- 
Sent from mobile phone, apologies for brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20180426/5d899359/attachment-0001.html