Marc Linster

➰ APIContext's latest insights on cloud-based API performance have been featured on Nordic APIs! In the 2024 report, we delve into crucial aspects affecting API efficiency: 🔐 Authentication is key. Ensuring robust authentication mechanisms in APIs is crucial, yet offloading this function can introduce complex challenges. 📖 DNS configurations matter. How you handle DNS settings can significantly impact API performance, particularly when tied to authentication processes. 🌐 The role of third parties. Critical third-party services play a significant role in 🔗 API transactions, underscoring the need for careful integration and monitoring. ⛅ Not all clouds are created equal. Differences in cloud services can drastically affect API performance, an essential consideration as APIs account for over 80% of all internet traffic. #APIs #CloudComputing #TechInsights #APIContext

15

1 commentaire

We're excited to kick December off with an announcement that we're taking our partnership with New Relic to the next level! Earlier this year, we teased a number of ideas planned on combining build-time and run-time insights to help developers prioritize vulnerabilities. Today, we're excited to launch this into a reality with a deeper integration with New Relic Vulnerability Management. This integration will give developers: 1. A consolidated inventory of their software security posture that combines scanning from build-time, run-time, and infrastructure 2. Prioritization and actionable insights derived via signals of how vulnerabilities flow from code to cloud 3. Comprehensive operational reporting and compliance Connecting build-time and run-time assets is a huge opportunity to unlock more value in our space. A big shoutout to Krystle Portocarrero, Oren Ben-Shaul, Carlos Cheung and the whole team who made this possible! Read More: https://lnkd.in/e3fAmSjh

75

6 commentaires

📷 Had a great Confluent #DataInMotion event yesterday with the support of SingleStore at the #Brussels #MaisondelaPoste. Great conversations about how to simplify development of #AI Applications leveraging SingleStore and Confluent Cloud for #ApacheFlink. Real-time gen AI applications require real-time data processing. #RealtimeData #GenerativeAI #DataStreaming #VectorDatabase

14

2 commentaires

If you want to learn more about tuning Parquet files for your use case, you can now view my PyConDE/PyData Berlin talk

33

The integration with #AWS #Bedrock in AveriSource Platform 3.0 is a game-changer for #mainframe modernization. If you’re ready to explore state-of-the-art #GenAI capabilities, book a demo today!

2

Customers told us that one of the hardest parts of building LLM apps was accurately pulling out content from PDFs. So, we’re excited to announce the release of the #Aryn Partitioning Service: https://lnkd.in/g3_bUyvt It takes complex PDFs and breaks them down into their constituent components and returns JSON objects that you can use with your own data pipelines or #Sycamore. It’s up to 6x more accurate (mAP) and 5X faster than alternatives on real customer workloads. And, it’s free to get started. Try it out yourself: https://lnkd.in/gXtn9bvs Send us your craziest PDFs. Thousands of pages. Lots of complex tables. Headers, footers, sections, graphs, images. No problem! Give it a shot. You can mess around with your PDFs in the Aryn Playground: https://lnkd.in/gu2vTGkF Feel free to reach out and leave feedback in the community Slack. Website: https://www.aryn.ai/ Video: https://lnkd.in/gaAb4uHn Aryn SDK docs: https://lnkd.in/gZ3uuGDP Sycamore GitHub: https://lnkd.in/gVUfgwmw Slack: https://lnkd.in/gBmZ7Mtw #Aryn #Sycamore #LLM #GenAI #RAG #unstructuredanalytics #analytics #PDF #ETL #search #hybridsearch #semanticsearch #tables

122

6 commentaires

🤔 Unlock revenue tied to data streaming or keep your focus on the rest of your roadmap? Good news: that’s a choice you no longer need to make—the Confluent OEM Program is here to empower you to do both! MSPs, CSPs, and ISVs, don’t miss out—learn more about the program on our blog!

14

Managing legacy systems is hard... even for AWS "S3 is showing its age": very nice article by Chris Riccomini on #AWS #S3: https://lnkd.in/e8rPiMdi Object storage is often becoming the primary storage for #data systems such as #WarpStream. AWS S3 once defines the defacto standard API for all object storages and was in the past well in advance in terms of performance/price and features. This is now over and it may become a switching factor in the near future as explained in the article. In the past they managed to overcome the atrocious "4 characters random prefix" to bucketnames that was needed to avoid hotspot scenario and bad performance, but the road ahead is challenging and the competition is real. - No Compare-and-Swap (CAS) Operations: Unlike its competitors, S3 lacks preconditions, forcing developers to use workarounds like DynamoDB. - S3 Express One Zone (S3E1Z): While promising, S3E1Z misses many standard S3 features and comes with high storage costs. - Lack of Multi-Region Buckets: S3 doesn't support dual-region or multi-region buckets, limiting its availability options.

12

Don't miss out! Join us for a free workshop on memory allocation, object lifecycle, and garbage collection strategies within the Java Virtual Machine (JVM). Register now for the webinar on Oct 4th > #developers #Java #JVM

1

.@AWSCloud plans to invest €7.8B into the AWS European #SovereignCloud, set to launch by the end of 2025 | AWS https://buff.ly/3OhE1mF >> Congrats, good to see a schedule. And #Brandenburg is a winner. Data residency and access matter. #Cloud

18

"Imagine a symphony, where each instrument plays a critical role in crafting a harmonious melody." This is the way my colleague Alexander Kirillov explains monitoring of cloud systems. He states that every alert, every check, and every response mechanism is an instrument. Crafting a monitoring system is akin to orchestrating a symphony, where each component must play in harmony to ensure the melody of seamless operations and optimal user experiences. Sounds pretty cool to me. Check the comments for the full article 👇 #cloudmonitoring #aknostic #cloudengineering

4

1 commentaire

𝙆𝙚𝙚𝙥𝙞𝙣𝙜 𝙘𝙤𝙙𝙚 & 𝙙𝙤𝙘𝙪𝙢𝙚𝙣𝙩𝙖𝙩𝙞𝙤𝙣 𝙞𝙣 𝙨𝙮𝙣𝙘 𝙝𝙖𝙨 𝙖𝙡𝙬𝙖𝙮𝙨 𝙗𝙚𝙚𝙣 𝙖 𝙩𝙤𝙪𝙜𝙝 𝙣𝙪𝙩 𝙩𝙤 𝙘𝙧𝙖𝙘𝙠, but after recording an episode of #cloudnativefm [https://lnkd.in/dkucsibi] with Sebastian Huckleberry and Jeremy Lewi [Meet both at Stateful’s #KubeCon booth S51] and watching https://runme.dev/ & https://foyle.io/ in action it's just a matter of time b/c 𝗥𝘂𝗻𝗺𝗲’𝘀 𝗺𝗼𝘀𝘁 𝗽𝗼𝘄𝗲𝗿𝗳𝘂𝗹 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝗶𝘀 𝗲𝘅𝗲𝗰𝘂𝘁𝗮𝗯𝗹𝗲 𝗺𝗮𝗿𝗸𝗱𝗼𝘄𝗻. With it, you can write documentation alongside your code that can be executed directly from the documentation itself. 𝐒𝐞𝐚𝐦𝐥𝐞𝐬𝐬 𝐈𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐰𝐢𝐭𝐡 𝐃𝐞𝐯 𝐄𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭𝐬: Runme integrates into popular developer environments such as VSCode, making it easy for developers to create, maintain, and execute documentation alongside the code they are working on. 𝐔𝐬𝐞 𝐂𝐚𝐬𝐞𝐬 𝐟𝐨𝐫 𝐑𝐮𝐧𝐦𝐞 𝐢𝐧 𝐭𝐡𝐞 𝐑𝐞𝐚𝐥 𝐖𝐨𝐫𝐥𝐝 - Tutorials and Learning - DevOps Pipelines - Runbooks for Incident Management 𝐈𝐧𝐬𝐭𝐚𝐥𝐥𝐚𝐭𝐢𝐨𝐧: You can install Runme via its CLI or use its VSCode extension to get started: https://lnkd.in/dagiWW4C 𝐂𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐚𝐧 𝐄𝐱𝐞𝐜𝐮𝐭𝐚𝐛𝐥𝐞 𝐌𝐚𝐫𝐤𝐝𝐨𝐰𝐧: With Runme, you can create an .md file that contains both your code and documentation. For example, if you want to showcase how to deploy a microservice, you can embed the code snippets and Runme will execute them directly from the markdown. 𝐑𝐮𝐧𝐧𝐢𝐧𝐠 𝐂𝐨𝐝𝐞 𝐟𝐫𝐨𝐦 𝐌𝐚𝐫𝐤𝐝𝐨𝐰𝐧: As you build your documentation, Runme lets you run code blocks in real time, ensuring that your documentation is up-to-date and functional. 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧: Runme integrates with version control systems like Git, making it easy to collaborate with others. 𝐈𝐧 𝐬𝐡𝐨𝐫𝐭: Runme, the challenge of "making code your docs" becomes significantly easier. By introducing executable markdown and seamless integration into the development workflow, Runme could be the perfect tool to adopt for a streamlined, automated, and developer-friendly approach to maintaining accurate, up-to-date documentation. By Integrating Runme with https://foyle.io/ is an open source project to bring an AI assistant into Runme notebooks. It helps you deploy and operate your application by letting you express your intent in natural language and then using AI to generate the commands to achieve that intent. 𝐖𝐚𝐭𝐜𝐡 𝐭𝐡𝐞 𝐟𝐮𝐥𝐥 𝐞𝐩𝐢𝐬𝐨𝐝𝐞: https://lnkd.in/dkucsibi #DevOps #platformengineering #AIOps #MLOps #GitOps #runme #foyle #GenerativeAI #GenAI

10

1 commentaire

[longer-form version behind the link]: https://lnkd.in/er6dzQr6 On July 19th 2004, I spent my first day at Google. I showed up at the Datacenter in Dublin, since that's apparently where SREs and production folks were going to sit. There weren't any other SRE offices outside the US at the time. There wasn't a corp network connection, because this was Google in 2004. A couple of days later, I moved my stuff to Dublin HQ on Barrow Street and commandeered a free desk. A few weeks after that, someone from facilities asked "Hey, isn't your team based in the DC?". "Nope", I said. They shrugged, and updated some spreadsheets, and then SRE was based in Barrow Street. Again, this was Google in 2004. We were making it up as we went along, in the best possible way. I could claim I was doing SRE-adjacent things before this, as I suspect could many people, but I'm going with that day as when I became an SRE in any formal sense. The function was still figuring itself out; in many ways it still is. My work with Busy Teams as a freelancer isn't "SRE work" on paper, but in practice, it very much is. Resilience, defense in depth, common sense, backup plans for backup plans. Across industry, SRE/Reliability/Devops/ProdEng/Whatevsies is many things to many people. So, in the spirit of the core of the function, I've been thinking a little about uncomfortable gaps in capability. What have we not figured out yet? Here's my short list of boiling hot takes (hit the link for more detail, LinkedIn's got a character limit) : 1. - Most companies haven't figured out how much they steady-state care about reliability. I expand on this in my article "6 Reasons you Don't need an SRE Team". https://lnkd.in/eWMD3cFh 2. - Assuming we've figured out that we care, we still can't agree how hard a problem this is. SRE (and traditional ops) begat DevOps, which at its core has the premise that busy developers could side-gig the production bits, and you can just wave your hand and say "You build it, you run it" and that'll cover you. This isn't true today, and was even less true when 'DevOps' started being a thing. 3. - We actually run less and less of our own infra, and practices need updating. Many of the SRE practices as set out in various books/articles kind of assume you own your whole stack. This is becoming mostly untrue, and we are currently a Frog of Moderately Troubling Temperature here. Anyway. It's Friday, it's 22 degrees outside in Dublin, and it's time to go enjoy the next 20. No shortage of things to do.

43

4 commentaires

💡 It's predictions time! This article in APM Digest explores how #observability will impact the business in 2025. 💬 "Observability will evolve from a singular view to a multidimensional approach. Teams will analyze workloads through lenses such as uptime, performance, cost, security, and compliance. This blended perspective will help organizations make better decisions...," said Andreas Prins, VP of Product Marketing at SUSE. 👉 Read more here: https://okt.to/DtLgdT

1

Auto Scaling isn't as straightforward as it sounds. In our latest eBook, The Art of Autoscaling, RapidScale demystifies prevalent misunderstandings and imparts knowledge from more than ten years of Auto Scaling experience within AWS. Uncover the guide to developing scalable, robust cloud infrastructures—secure your copy now! https://gag.gl/t3dDYn #AWS #autoscaling

5

Getting started with Kannika Armory our your backup solution for Kafka data? Easy as 1, 2, 3, ... 4 😅 Read all about it below and find more info on https://lnkd.in/dZJevHTQ #backup #freetrial #kafka

6

Ha. The "Grumpy Customer Problem" is a new one. This is a great blog by Colt McNealy about how to use the SAGA pattern to prevent data loss and Grumpy Customers. Interesting how much simpler the flow is with LittleHorse than if you just wired all the message queues together by hand. Give it a read. https://lnkd.in/giaB6kB6

53

4 commentaires

CTO Srini Srinivasan discusses how the updated #Aerospike #Kubernetes #Operator makes it simpler to back up the company’s namesake real-time database using an ABS. #APIs https://lnkd.in/eAtdvJ92

5