#5 magma™ oldTeck™, newTeck™, IDEASFORSALE™, THE UNIVERSALGRID™, HUGEDATA™, COMPUTATIONAL SCIENCE AND SELF-RELIABLE MULTI-INSTANTANEOUS TASKING SYSTEMS.

Link here to: Activate #6

Welcome to magma™ — THIS particular story and all of them in the series is currently [work in progress] and you may find errors in them. Please point them out, it’ll help us focus on fixing them. These are live documents which chronicle our Corporate Journal Entries; and they are geared towards documenting the progress of our processes. Please check back or subscribe to get notifications, as daily changes are made. — Thank you for your support; we love your well thought of and constructive feedback. Sunday, April 23, 2023 01:58.00 PM — La Jolla, California 92137 USA

CATO5Q (Where five = [Q]) (Image Credit: magma™/SKYROCK STARTRADE™)
Smash, like or hit the play button and listen to this story; — magma™ [] Nooo, not this one, Up ^ that one! :P [Listen]

STRUCTURED SOLUTIONS for FUTURE Ai DRIVEN COMPUTATIONAL MULTI-PROBLEMS.

Challenge One

db tasking

How do CURRENT data services, (CDS™); perform tasks between Application Programming Interfaces, (APIs); and DataBase Software Clusters when trillions of message queries requests happen in non-vm scenarios.

FUTURE POSSIBILITIES WITH Artificial Processes in Computation, (ApIC™) — There is [NO] Artificial -and- Intelligence. These two do not go together in the same sentence.) Scratch your head and begin wondering why… because this thing alone when resolved, will bring forth the next generation Beyond Digital™.

Computation is a set of instructions executed after a request for a task to be performed has been made by [The] User(s). Intelligence however, requires awareness and it isn’t multi-task generated. It his [high-er] A-L-L at once and simultaneous. IN-TELLING this story. Intelligent is the GENTLE-MAN who finds the answers [_Blank] provocative. (God Damn, F$%@, anyway, fill it in with your own adjective(s)).

AWARE-NESS — IS…

and W-H-A-T is… IS?

IS, is… (more on this later… =)

FIRST: HOW MANY MILLIONS IN A BILLION?

1000

HOW MANY 1000 MILLIONS IN A QUINTILLION?

5000

QUINTILLION SIMULTANEOUS TASK REQUESTS AND HOW TO HANDLE THEM simul a tion (Simultaniously) all at once. ;)

SI — MULA =P

How many millions of people making cellphone calls, sending and receiving texts at this concert? hehehe…

The FUTURE implementation of Computational Artificial Task Oriented (CATO™) and Process-less Intensive protocols (PLIP™) for what is to come after Machine Learning… or KNOWLEDGABLE BASED NETWORKS (NaNs™) and other menial tasks.

Scenario One: Your airplane is about to take off from the Miami International airport.

You are taking a selfie, your friend is saying goodbye to her mom on her cellphone the kid in-front of you is playing a multiplayer game online, the passenger across from you is taking video of the cute stewardess smiling at the passengers with a belt on her left hand about to give instructions; and all other passengers begin turning their cellphone off, after the captain asked them to… ([One passenger-You] Now, times that how many airplanes in the world and how many passengers like you, are doing the exact same thing… How many, do you think?!?)

Meanwhile, in the flight control tower… hundreds if not thousands of tasks are being required; so that everyone has a safe flight until that flight reaches its destination.

Imagine the loads these databases ALL handle… per second tasks take WAY too long... In the near future, all of these dbs HAVE to out-perform the current models. Because, with whom does the responsibility of you getting safely to your destination lies? — What if… scenarios where everything [is] are possible; and it [will] be possible… and [without] YOU at the wheel of your life; [who is…] responsible for it; (YOUR LIFE) — [IF] anything goes wrong? Your CAT -O™

yeah, hopefully.

but-BUT we KNOW the CATO™ hasn’t been invented YET!

…and-AND where is MY UNIVERSALGRID™ god Damn System too!??

THIS IS NOT A CHALLENGE; THIS IS A SERIOUS PROBLEM.
All current data services models perform tasks between APIs and DataBase Clusters. [C-L-U-S-T-E-R-S]

What is a cluster?

According to you know who of the [big] search En-s:
The definition for a cluster is: — a group of similar things or people positioned or occurring closely together.”

“clusters of creamy-white flowers”

yeah, FOR YOUR FUNERAL!

Potentially speaking that is… [IF] — anything goes wrong.

So, how do YOU un-cluster f@$K a solution for FUTUREs where happen that happen to get you home safe?

Well, let’s first explore the “Remote Procedure Call (RPC) framework endpoint; or gRPC per database query. Intentionally, some do not contain business logic.

Imagine this crowd sending and receiving messages, cellphone calls; taking images and videos and uploading them to their favorite social media sites.

and there is Voila! a single tunnel of white light receiving their tasks; one by one. Also known as: SINGLE DATABASE worker spinUp task query. (I’m inventing here…) SpinUp or Spinning Color Wheel of Hell?

All current data services models perform tasks between the API and database clusters.

All current data services models perform tasks between the API and database clusters and one gRPC endpoint per database query. — Intentionally, some may not contain business logic; but the future of huge data is upon us and big infrastructure has to begin now. Another feature of wireless API Database + Data Clusters and gRPC endpoint requests per data base coalescing needs updating. When multiple users requesting tasks they are done in the same row and at the same time; some models only query the database once. Worker task driven queries access the database and return the row to all subscribers; however, this train (follow the engine) mentality and current limitations will be out scaled here pretty soon.

THE CURRENT MODEL
a) API
b) task requests
ab) Database Clusters

c) endpoints per db

d) query

(request static cooling)

IF {
Multiple db call requests take place at the same time.
}

[One query per multiple user requests (in a row)]

THEN {
worker task to spin up in the database service will…
}

Output: Subsequent requests will check for task;

THE FUTURE SOLUTION-BASED STUFF:

Stable UNIVERSALGRID™
UNIVERSALGRID™ testing
UNIVERSALGRID™ testing
UNIVERSALGRID™ testing
UNIVERSALGRID™ testing STABLE FIELD ONE
Guess how big these Rfs Are?

“Oh, did I mention? This is my friend?” :D

“Yah-Ha, One Hot Invention, coming Right Up!”

“Echo State to Alpha State”

Now, that’s a cluster. ;)

(Question: When does management get involved?)

Subscription takes place. (How will the requests get managed?)

First solution: FIELD VIBRATES task once
~No spinUp~ occurs
~No need for query
The return is simultaneous and not in a row
to all subscribers.

SolutionX:

ProblemSolvingManagement PSM™
current model:
SINGLE: [db single row query (task intensive absorbed)]
INPUT
TASK
OUTPUT

Beyond Digital™ — The Future:
MULTIPLE users requests:
INPUTS
RESOLVEDMULTILEVELTASKING, (RMLT™)
OUTPUTS

More content — coming up soon — “like, subscribe, smash that love <carrots?> button and Read, Research, and Go Educate Your Mom and your Dad on the benefits of this great universal play building adventure; — magma™.” :D by SKYROCK STARTRADE™

More content — coming up soon — “like, subscribe, smash that love <carrots?> button and Read, Research, and Go Educate Your Mom on the benefits of this great universal adventure; — magma™.” :D

That is all; for now.

— g. m. marckwordt
junior-junior Designer at SKYROCK STARTRADE™
Honorable, USMC 0311 ret
Professor of computational geometry
Former Operations VP International (France) and Intercontinental Logistics Firm in Los Angeles, California USA.

Last login: Th Mar 9 16:50:33 on skrk000
magma@workstation01 ~ % sudo vim /etc/passwd
Password: magmaplatform
111 is not in the sudoers file. This incident will be reported.
ws01@magma01 ~ %
[Restored Mar 9, 2023 at 14:40:49 PM]

Last login: Th Mar 9 14:41:08 on ttsxz000
magma@workstation01 ~ % sudo vim /etc/passwd
Password: magmaplatform
112 is not in the sudoers file. This incident will be reported.
ws02@magma02 ~ %
[Restored Mar 9, 2023 at 14:41:10 PM]

Last login: Thu Mar 9 14:44:45 on console
Restored session: Thu Mar 9 14:45:33 PST 2023
magmaplatform@magmaplatform ~ %
dynamic content permission [granted]

Links to previous written works by magma™:
Activate #1 @ SKYROCK STARTRADE™ Saturday March 4th 2023 6:21 PM|
Activate #2 @ SKYROCK STARTRADE™ Saturday March 4th 2023 8:20 PM|
Activate #3 @ SKYROCK STARTRADE™ Sunday March 5th 2023 6:45 AM|
Activate #4 @ SKYROCK STARTRADE™ Monday March 7th 2023 5:33 AM|
Activate #5 @ SKYROCK STARTRADE™ Wed March 8th 2023 12:51 AM|
Activate #6 @ SKYROCK STARTRADE™ Thu March 9th 2023 3:00 PM|
Activate #7 @ SKYROCK STARTRADE™ Thu March 9th 2023 3:00 PM|
Activate #8 @ SKYROCK STARTRADE™ Thu March 9th 2023 7:44 PM|
Activate #9 @ SKYROCK STARTRADE™ Thu March 9th 2023 9:32 PM|
Activate #10 @ SKYROCK STARTRADE™ Thu March 9th 2023 9:32 PM|

Activate #twitter @angelmarckwordt Friday March 10th 2023 5:55 PM|

Activate #twitter @ SKYROCK STARTRADE™ Friday March 10 2023 5:55 PM|

Note: “All referenced material in video and/or written form; and its copyrights; owned by its respective owners.”

All other original content:
Copyright © 2022, 2023 — Forever. SKYROCK STARTRADE™., LLC. All rights reserved.

--

--

[] magma™ -UNIVERSAL INDUSTRIAL STARSHIP BUILDERS™

junior-junior designer, --magma™ at SKYROCK STARTRADE™ La Jolla, California, USA. Copyright © 2022, 2023, 2024 ∞. SKYROCK STARTRADE™., LLC. All rights reserved.