What are your thoughts for an #APIfirst #REST API approach but giving API users access to some aggregations.
In the current #BFF based solution our dashboards and some filter dropdowns especially make use of materialized views that are fairly complex UNION/GROUP BY combinations.
I guess we will just have a few specialized endpoints for this and depending on performance impact decide if to include those in the public API or not.
Организационные и технологические трансформации в банке глазами корпоративного архитектора
Корпоративный архитектор — это «демон Максвелла», и его задача — бороться со сложностью ИТ-ландшафта. У нас в Банке это добрый демон, оперирующий подходами Just Enough Enterprise Architecture (JEEA) и Lightweight Architecture Governance (LAG). Именно корпоративные ценности и культура в Банке делают демона добрым. Поверьте мне, ведь я один из них. Привет, Хабр! Меня зовут Дмитрий Клецких. Я Chief Enterprise Architect в Райффайзен Банке. До этого много лет работал корпоративным архитектором в других компаниях: МКБ, СБЕР, Транснефть, Правительстве Москвы. Поговорим об изменениях ИТ-ландшафта, организационных и технологических трансформациях, о роли архитекторов и изменении этой роли с приходом ИИ.
https://habr.com/ru/companies/raiffeisenbank/articles/957316/
#enterprise_architecture #platform_engineering #lag #apifirst #greenpath #jeea #цифровая_трансформация #архитектурное_мышление #ии_в_разработке #ITстратегия_банка
Pessoal,
Estamos iniciando um projeto open source chamado vitae, a ideia é ser o seu curriculo vitae, online, no fediverso.
Será um linkdisney-like, federado, pensando na pessoa profissional, e no ser humano por trás dela.
Não vai ter timeline com coach quântico, até pq já temos o mastodon pra isso né, mas as mudanças no currículo poderão aparecer na TL ou não, de acordo com oq a pessoa usuária quiser mostrar.
O Backend vai ser PYTHON com FASTAPI e quem tá puxando os requisitos e arquitetura é o Dr. @riverfount
O Frontend vai ter o melhor e mais moderno do JS/Deno, quem tá puxando os requisitos e arquitetura é o senhor @jedi.
Eu to cuidando da INFRA.
Quer entrar e ajudar a criar essa maravilha? só vem! ;)
Tem ticket pra todo mundo! :P
Estamos nos organizando o role via https://mattermost.bolha.chat
Aqui o convite para entrar!
https://mattermost.bolha.chat/signup_user_complete/?id=w543hb3aypgyfjy8eh9x9da8oc&md=link&sbr=fa
cc @dunossauro , se puder repassar pros seus alunos, pode ser uma oportunidade de participarem de um projeto open source do zero.
cc @melissawm
cc @ericof
Pythonistas, espalhem!
JSistas, espalhem!
BOOST PLS
Uma iniciativa Bolha.io/Bolha.us
"[T]he vast majority of MCP servers are a waste of time. And that’s normal because the MCP spec is only months old. People jump into it, and they start building for MCP without really thinking it through or understanding what it should be.
The vast majority of MCPs that you can see now are reflections of APIs. I think that’s a complete waste of time. This might be offensive, but let’s take Kubernetes. As an example, Kubernetes is an API-driven platform of sorts. Now let’s say you have a Kubernetes MCP server that basically allows you to get resources, to describe resources, and to see the logs and so on and so forth. They’re basically reflections of the Kubernetes API, just as kubectl is a reflection of the Kubernetes API.
Now, does an AI agent really need that MCP server? Absolutely not. It’s perfectly capable of using kubectl directly. And even if there weren’t a kubectl CLI, it’s perfectly capable of talking to the API as is. And it’s not hard for an AI backed by an agent to execute the URL commands to go to some API, and effectively do the same thing that that MCP server is doing.
What we need is MCPs that are actually providing additional value around user intents. Instead of having a Kubernetes MCP server that is a reflection of its API, have a Kubernetes MCP that will have certain logic or workflow or this or that, that will help you combine resources to get an application up and running. So, something beyond just a one-to-one reflection of an API."
https://nordicapis.com/why-internal-developer-platforms-need-apis/
Kontur Population
Not just a map — a population data engine.
Kontur Population is always up-to-date, API-first, and fully customizable.
Built for decision-making across sectors — from disaster response to logistics & insurance.
🔗 kontur.io
Here is a discussion how the request validation middleware should handle paths that are not defined in your #openapi API description. – Return 404 or skip the validation and pass the request to the upstream app?
Your thoughts would be very much appreciated.