In my business (transportation management systems), we have lots of data,
complex business and operations processes, and a very high transaction
rate. If the system is down, the business runs at 10%; most of my
customers have warm or hot backups. Latency would be an issue with order
entry, dispatching, web inquiries, EDI, and revenue accounting happening
concurrently. But once a shipment is delivered--usually in one or two
days--there's very little activity against that shipment's history. This
is an opportunity: with the right set of business rules, older data with
relatively little activity (and economic value) could be pushed into the
cloud. But I'd not recommend such a move because shipment tracking and
data analysis would be handicapped if they had to run to the cloud. After
three years, certain provisions kick in and then the data is really dead.
So, I'd keep three years locally, and if I was going to keep more, I'd
cloudify it.

"If"? Yes, the courts have, on occasion, issued record requests for "all
data" and it can turn into a huge mess (it was crippling financially when
records were paper but the copier salespeople were thrilled). Due to price
and service changes, revenue reporting, without quite a bit of accounting
adjusting, would be very sketchy.

Vertical applications--G/L, trade payables, fixed asset accounting,
etc.--are good cloud candidates--latency and availability can be managed.
I'll asterisk payroll--payroll checks not delivered on time in a union shop
can result in breathtaking penalities. But the increase in direct deposit
offsets much of that risk. An added benefit is that financial apps are
often hyper-secure, even from IT types.

I can think of lots of business models where the cloud is terrific.
Otherwise: NIMBY. Life isn't worthy living if you're not in fear of a mass
storage device crashing.

On Thu, Jul 10, 2025 at 7:53 PM Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:

I know of at least one customer that has never gone to the cloud due to the
nearest data center bumping the latency too far for some tasks they did (I
can't remember right now but I believe it was text recognition for voice
picking in the logistic centers). So, there's always a case for "I want my
server here". Then again, that customer was clearly not a P05 customer
either.

On Thu, 10 Jul 2025 at 21:39, Diego E. KESSELMAN (G) <
diegokesselman@xxxxxxxxx> wrote:

I think this conversation is taking a different direction.

1) The S1022S will be replaced for a particular case of S1122 with 2x4
cores P11 sockets. So I was wrong, there is still a 4-core cap and a
8-core cap for the S1122

"Power S1122 with the 2x4 core processor option supports IBM i natively
(or under VIOS) and can support up to the full 8 cores. Every other
processor option requires IBM i to run under VIOS and limits partition
size to a maximum of 4 cores."

https://www.ibm.com/downloads/documents/us-en/13774247783d5fe6

2) I am not sure what is the pain point about server location. In IBM
Power Virtual Server you can select your Region (ie: DALLAS, WDC,
Montreal) or an specific Datacenter (DAL12).

You can get a complete DC list here:



https://www.ibm.com/docs/en/power-virtual-server?topic=locations-cloud-regions

About who can access physically your server, I guess the major fear is
in US, because the government can access the DC (with the proper judge
order) based on the actual laws, but this is very unlikely.
This is not possible in the other countries hosting IBM Cloud servers,
and you can feel free to chose the one that fits your needs.

About data security, IBM has a lot of certifications to comply with
banking industry standards all around the world.

Communications can be dedicated or using VPNs, is a matter of costs.

That being said... Not all companies can get benefits from the cloud
with IBM Power. It always depends and it is a case-by-case.

It is more than just getting a quote, because you have to exchange data
with your infrastructure ecosystem, and sometimes is not possible
because of communications, regulations, company policies, IT-team
knowledge, IT-culture, etcetera.

Some companies think of "Move-to-cloud-now" , others
"We-are-not-a-cloud-company".

And some companies just need to run a PoC to understand if it really
matters.

Regards

Diego E. KESSELMAN


El 10/07/25 a las 4:18 p.m., Infodorado InfoDorado via MIDRANGE-L
escribió:
Good point, DR2!

My son worked awhile at Burger King headquarters as the last IT guy
before the BK boss finished outsourcing all of IT. The CEO said, "We make
hamburgers". They checked various cloud vendors. My son told me they
rejected Google's offer because Google "could not guarantee" (their
wording) that the data would stay inside US borders.

--Alan



On 07/10/2025 4:55 PM EDT dr2@xxxxxxxx wrote:


Pat,

The biggest issue I have with "the cloud" is not knowing where my data
actually resides and who would have access to it that I wouldn't be
able
to know of or control. Further, if it's in some 3rd world country I
have to be aware of any connectivity issues between me and there, not
to
mention any political issues going on there or between me and there
that
would potentially cause service disruption.

I sleep much better knowing where my data is and who controls it.

DR2

On 2025-07-10 16:51, Patrik Schindler wrote:

Hello Diego,

Am 10.07.2025 um 19:28 schrieb Diego E. KESSELMAN (G) <
diegokesselman@xxxxxxxxx>:

There is a "cloud first" mantra
Here in Europe, people finally start to think if it's a good idea to
outsource more or less complete IT operations to some more or less
arbitrary company who is mainly after your money. And there will always
be
security issues and increased complexity. Too many promises, too many
"save
money", too many shocking bills. Yes, cloud can be comfy, but is it worth
the price?

Rhetorical question.

I hope IBM gets back to remember what the M in IBM means.

:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



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-2025 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.