Hi Rukshani,
Where is it in the hierarchy?
On Mon, Mar 14, 2016 at 12:25 PM, Rukshani Weerasinha
wrote:
> Hi Nirmal,
>
> At the moment, Tooling is already documented for some products as a
> separate section within the product documentation space (e.g. [1]). Can we
> follow the same approach fo
Hi Nirmal,
At the moment, Tooling is already documented for some products as a
separate section within the product documentation space (e.g. [1]). Can we
follow the same approach for Analytics?
[1] https://docs.wso2.com/display/ESB490/Installing+the+ESB+Tooling+Plug-In
Best Regards,
Rukshani.
O
Hi All,
Shall we decide where we gonna host APIM analytics related docs? Would it
make sense to create a new doc space hierarchy with the introduction of
product, tooling and analytics?
APIM-X.X
|_ Product
|_About X
|_Getting Started
|_Tooling
|_ ..
|_Analytics
|_ ..
--
+architecture
*Lasantha Samarakoon* | Software Engineer
WSO2, Inc.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 (71) 214 1576
Email: lasant...@wso2.com
Web:www.wso2.com
lean . enterprise . middleware
On Mon, Mar 14, 2016 at 12:02 PM, Manuranga Perera wrote:
> I think we have to keep
On Mon, Mar 14, 2016 at 7:18 AM, Lakmal Warusawithana
wrote:
> Hi Azeez,
>
> Without server side circuit breaker, can't we achieve this simply in load
> balancers? See nginx "Passive Health Monitoring". It has implemented this
> into some level.
>
Yes, it can be achieved to a certain degree, but
On Mon, Mar 14, 2016 at 7:41 AM, Lakmal Warusawithana
wrote:
> Actually even client side circuit breakers are not going to work, if we
> fronted micro services via LB.
>
Cct breakers work within time time windows, and within a time window, if
many calls failed, the client side cct breaker should
Hi Susinda,
On Mon, Mar 14, 2016 at 10:22 AM, Susinda Perera wrote:
> Hi Lahiru
>
> Is there tooling requirement for AppManager? If so shall we have a chat
> and build a tooling plan.
>
We haven't plan tooling for AppManager immediate release (1.2.0). But, yes
we could have a chat and include i
Hi,
Let me try to clarify few things here.
- Initially we implemented Netty HTTP transport with conventional thread
model (workers) and at the same time we also tested the Disruptor based
model for the same Gateway/Header based routing use case. Disruptor based
approach gave us around ~20k of pe
Hi Lahiru
Is there tooling requirement for AppManager? If so shall we have a chat and
build a tooling plan.
Thanks
Susinda
On Thu, Mar 10, 2016 at 1:18 AM, Lahiru Cooray wrote:
> Hi All,
>
> WSO2 App Manager team pleased to announce the WSO2 APP Manager 1.2.0 -
> Milestone 2 release. It conta
Actually even client side circuit breakers are not going to work, if we
fronted micro services via LB.
On Mon, Mar 14, 2016 at 7:18 AM, Lakmal Warusawithana
wrote:
> Hi Azeez,
>
> Without server side circuit breaker, can't we achieve this simply in load
> balancers? See nginx "Passive Health Mon
Hi Azeez,
Without server side circuit breaker, can't we achieve this simply in load
balancers? See nginx "Passive Health Monitoring". It has implemented this
into some level.
My point is all these micro services going to be fronted by a load
balancers and if clients not implementing client side c
We are not leaving out anything. We are in the process of implementing
circuit breaker, bulkhead, timeout. Basically, core features people look
for when evaluating microservices frameworks. We have started with circuit
breaker.
Thanks
Azeez
On Sun, Mar 13, 2016 at 6:57 PM, Frank Leymann wrote:
I do have a more general question: what justifies the focus on the "circuit
breaker" pattern at all? It is just one patter to solve recurring problems
with stability, i.e. other patterns are there too that are important (e.g.
"timeout" - see Michael Nygard's nice book).
Thus, what are the criteria
13 matches
Mail list logo