Assel Meher

aka Segflow - just a security enthusiast.

[RelationalAI @RelationalAI]

🚀 RelationalAI’s Knowledge Graph Coprocessor is GA as a Snowflake Native App!
🧠 With 10x less code and complexity, customers can now build intelligent applications using a data-centric architecture based on relational knowledge graphs.
➡️ https://t.co/mOEgHFyFyT

[RelationalAI @RelationalAI]

🚀 News! RelationalAI, the knowledge graph coprocessor for your data clouds, has just unveiled its Snowflake Native App on the Snowflake Marketplace! Start building enterprise AI today.

https://t.co/5MEp2EmcrX

[RelationalAI @RelationalAI]

🎉 news! We’re delighted that our CEO Molham Aref (@molhamaref) was featured on Forbes. Discover how we’re working with @Snowflake to make it easier to build intelligent applications faster.

https://t.co/77uKNaqUAt

[Assel Meher @segfl0w]

@josephdenne @edgenetwork I worked at https://t.co/DjBEVpVyft few works ago, I'm really glad to see the progress it made.
A project with huge potential lead by very talented people.

[Dr Milan Milanović @milan_milanovic]

𝗪𝗵𝘆 𝗱𝗼𝗲𝘀 𝗚𝗼𝗼𝗴𝗹𝗲 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱 𝗠𝗼𝗱𝘂𝗹𝗮𝗿 𝗠𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝘀 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀?

In the last decade, we have seen a massive trend of using microservices everywhere. We were building systems for a few hundred or thousand users and wanted to know how to make a system for millions of users. This was over-engineering and needed to be corrected. Why it was wrong? Because the development lasted long and we created incredibly complex systems, hard to maintain. This is especially true for startups that must go fast and stay simple.

A recent paper by authors from Google found that most of their developers split binaries for one of the following reasons: it improves performance, fault tolerance, and abstraction boundaries and allows for flexible rollouts.

Yet, splitting applications into microservices has its challenges:

🔸 𝗜𝘁 𝗵𝘂𝗿𝘁𝘀 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲. The overhead of serializing data and sending it across the network is increasingly becoming a bottleneck

🔸 𝗜𝘁 𝗵𝘂𝗿𝘁𝘀 𝗰𝗼𝗿𝗿𝗲𝗰𝘁𝗻𝗲𝘀𝘀. It is incredibly challenging to reason about the interactions between every deployed version of every microservice.

🔸 𝗜𝘁 𝘁𝗮𝗸𝗲𝘀 𝘄𝗼𝗿𝗸 𝘁𝗼 𝗺𝗮𝗻𝗮𝗴𝗲. Rather than having a single bi-nary to build, test, and deploy, developers must manage 𝑛 different binaries, each on their release schedule.

🔸 𝗜𝘁 𝗳𝗿𝗲𝗲𝘇𝗲𝘀 𝗔𝗣𝗜𝘀. Once a microservice establishes an API, it becomes easier to change by breaking the other services that consume the API.

So, they proposed the following approach:

𝟭. 𝗪𝗿𝗶𝘁𝗲 𝗺𝗼𝗻𝗼𝗹𝗶𝘁𝗵𝗶𝗰 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 that are modularized into logically distinct components. A component is a long-lived agent, similar to an actor.

𝟮. 𝗟𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝗮 𝗿𝘂𝗻𝘁𝗶𝗺𝗲 𝘁𝗼 𝗱𝘆𝗻𝗮𝗺𝗶𝗰𝗮𝗹𝗹𝘆 and automatically assign logistical components to physical processes based on execution characteristics. So, if both components are in the same OS process, they are called regular method calls, but if they are co-located, calls are executed as RPCs over the network. Runtime decides whether these modules should be collocated or moved to different machines (and scaled, etc.).

𝟯. 𝗗𝗲𝗽𝗹𝗼𝘆 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝘁𝗼𝗺𝗶𝗰𝗮𝗹𝗹𝘆, preventing different versions of an application from interacting.

This approach consists of two main parts: a programming model with abstraction that allows developers to write modularized applications and a runtime for building, deploying, and optimizing these applications. They claim that it reduces application latency by up to 15x and costs by up to 9x by simplifying application management and deployment.

If you want to check the framework implementing the approach from the paper, check https:// serviceweaver. dev/.

What do you think about this approach? Does it look like EJBs or CORBA?

#microservices

[Assel Meher @segfl0w]

@elmo4forver @JPiepiora You need an average of 11h per day since lunch (6-6-2023) to have 1300h in. Insane man

[Santiago @svpino]

Tracking time is for bureaucrats. If they make you do it, find another job.

The worst part of my job was always filling out a timesheet.

Nothing made me more miserable than an end-of-day email because I forgot to send my timesheet.

Unfortunately, this is common across the industry. Middle managers want to change the world by pushing numbers on a spreadsheet.

I remember this dude who forced us to report time on every task in JIRA.

Every time we worked on something, we had to do two things:

1. Track how much time we spent working on that issue.

2. Update the estimated time to finish it.

It was a nightmare.

He called out anyone who looked like they had spent too long on something.

What do you think happens?

Everyone started cheating. Nobody cared about delivering anything anymore. The only thing that mattered was that your estimates were as close as possible to the time you reported.

It took an act of God to stop that practice, but I had PTSD until the day I quit.

Does everyone have to do this, or does this only happen in certain companies?

[Santiago @svpino]

Scrum is one of the worst experiences I had to endure in my career.

[Assel Meher @segfl0w]

@PlayRavenswatch Will we get 4 steam codes for this?

[Passtech Games @PasstechGames]

We'll add Shrek to the cast of Ravenswatch if this tweet gets 10,000 RTs.

[Assel Meher @segfl0w]

@_bedis @MBFRANCE_ @MercedesBenz @DirectAssurance Maw t3allem sou9 inty

[Yann LeCun @ylecun]

My unwavering opinion on current (auto-regressive) LLMs
1. They are useful as writing aids.
2. They are "reactive" & don't plan nor reason.
3. They make stuff up or retrieve stuff approximately.
4. That can be mitigated but not fixed by human feedback.
5. Better systems will come

[Adam (Human) @madewithrobots]

1/ DNS — we all use it, but what is it? The history of DNS (Domain Name System) is a fascinating one that dates back to the early days of the internet. The purpose of DNS was to provide a human-readable way of accessing resources on the internet, instead of using IP addresses.

[anita @anitakirkovska]

OpenAI is working on a watermarking tool to mark GPT-generated text with a special, hidden signal.

And they have a working prototype.👀

How does it work?👇🏻

[MattyVerse @DCLBlogger]

Want to increase your productivity by 300%?

20 AI tools EVERY human needs to be aware of.

Thread

1/

[Alex Watt @alexcwatt]

Stack Overflow runs nine (9) on-prem servers to host all its sites, and found that giving SQL 1.5 TB RAM was more effective than caching page fragments with Redis.

And it's a monolith 🚀

Awesome interview with @rla4 and @shanselman: https://t.co/ghLqKHWHqh

[Alex Xu @alexxubyte]

What are some of the algorithms we should know before taking system design interviews?

I put together a list and explained why they are important.

To learn more: https://t.co/PczMAd8Jdb

[TradeTalks @TradeTalks]

.@RelationalAI Board of Directors @Bob_Muglia joins @JillMalandrino on @Nasdaq #TradeTalks to discuss the next frontier for AI and data-centric movement.

https://t.co/caDRBzPckR

[Shaundai Person @shaundai]

If the unit test fails, delete that test and move on.

Life's too short for the back and forth