× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Just happen to be at a WSO2 conference in San Francisco learning the in's and out's of the WSO2 stack.  WSO2 is a software integration platform.  The new CEO opened the conference with a keynote: "Integration is sexy".  YEAH!  WE in the IBM i world KNOW that!    He admitted that the platform with an API Manager, Identity Manager, Enterprise Service Bus, etc had actually contributed the problem of complexity when it comes to mini and micro services.  A true serverless, digital native microservices architecture is incredibly hard to manage and maintain. Even a semi-distributed, external API oriented architecture is very hard to do.  It's for all the reasons stated in this thread:  latency, security, API evolution, services that have dependencies on other services, etc.

My money is on micro-modules on a monolithic stack. Micro-modules because software requirements change and need to be "swappable".  Monolithic stack-wise because it is a heck of a lot easier to manage a single server, or perhaps a cluster of servers (small).  OSGI (a Java architecture) seems a very good fit to me and the ILE environment on i is about as close as we get in a heterogenous environment.

Coordinating dozens of node.js services emanating from dozens of providers sounds cool and bleeding edge.  But the reality of managing the complexity, and the difficulty in doing that, leads me back to IBM i...super scalable, secure and stable....give me that any day...

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
Twitter - Sys_i_Geek IBM_i_Geek

On 7/17/2018 9:18 AM, DrFranken wrote:
>
> My clients who tried to shoehorn the whole legacy modernization onto
> the i itself have all regretted it and moved to multi-tier.
>

My experience is exactly the opposite. Those who broke it apart were frustrated by managing multiple physical systems, multiple operating systems, and understanding multiple technologies. They find it much more difficult to control workloads. Often data requests come flooding in which they cannot controll starting hundreds of QZDASOINIT tasks and crushing system performance.

Updating them became more complicated, backing them up became more complicated. Staff needed additional training and additional contract resources were also engaged.

HA becomes much more complicated as well with many more pieces to consider.

One of them, after going the multi-tier path for a few years, chose to move everything back to IBM i. It's gone so well they won an award for their efforts. It runs well, is a single server to maintain and backup and has far less outside resource for maintenance.

Others have simply stayed with IBM i and continued to move forward and avoid the clutter.

IMHO Rube Goldberg need not apply.

        - Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.