10:25 a.m.
Hi Donovan,
* Will APIMan form some part of the new 3Scale integration
As per our blog posts in the past, the aim is to integrate the apiman
gateway with the 3scale manager in the community.
In the next release I'll hopefully be providing some initial integration
for folk to play with, but I'm not in a position to comment yet on fuller
integration with the UI, etc -- rest assured as soon as I can, I'll let you
all know.
Of course, I will forward your interest to the relevant parties (and that
of others who contact me -- or have already done so).
(more specifically, the on premise solution/OpenShift)?
I can't really speak about products, but I will put you in touch with
people who can!
If not, why the 1.3.0 release (since this adds new features)?
Some of this work is setting the ground for future work (including the
above), ensuring that we keep the apiman community well-served in terms of
gateway bug-fixes, features, performance, etc.
The reason for the version number bump is (in part) that some small
incompatible changes were introduced -- so, according to semver that
requires a minor increment rather than patch. Plus some substantial new
features released (apiman Vert.x gateway, headless registry, etc).
Regards,
Marc
On 9 May 2017 at 20:27, Donovan Muller <donovan.muller(a)gmail.com> wrote:
> Hi all,
> Having seen the response (from Marc Savy) on the thread
with the subject
> "Response when gateway cannot connect to the API implementation" about a
> 1.3.0 release of APIMan (with the vert.x gateway) and then having seen
> related commits on the GitHub repo (https://github.com/apiman/api
> man/commit/d3cedc5e05f143d45df8aa065e61de40b441c7fc). I'd just like to
> ask about the future of APIMan in relation to the 3Scale integration,
> especially, considering this announcement in relation to OpenShift:
> https://www.redhat.com/en/about/press-releases/re
> d-hat-introduces-fully-containerized-api-management-platform.
> Some questions I have:
> * Will APIMan form some part of the new 3Scale integration
(more
> specifically, the on premise solution/OpenShift)?
> * If not, why the 1.3.0 release (since this adds new features)?
> * If so, what would APIMan be used for?
> I'm asking this in the context of a financial services
organisation
> needing an on premise OpenShift integrated API Gateway solution. We are
> currently using APIMan (based on what was done here:
> https://github.com/openshift/origin-apiman) as a temporary solution until
> whatever 3Scale on premise solution will be released...
> Thanks in advance
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user