How to keep a popular API up an running 24 hours a day, 365 days a year.
Presentation by Federico Hernandez, Västtrafik from Nordic APIs Copenhagen in May 2013.
How to keep a popular API up an running 24 hours a day, 365 days a year.
Presentation by Federico Hernandez, Västtrafik from Nordic APIs Copenhagen in May 2013.
State of APIs: API trends from Nordic APIs Copenhagen & SundsvallAndreas Krohn
An overview of where we are coming from, where we are and where we are going in the API world. Presentation from Nordic APIs in Copenhagen and Sundsvall in May 2013.
Pie for Sale: Timeless Lessons in API Advocacy (Adam DuVander)Nordic APIs
This is a session given by Adam Duvander at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
API that nobody uses is almost as sad as a pie that nobody eats. Yet, both of these occur every day. Regardless of whether your API is for partners, internal, or external usage, it needs an advocate to help it be adopted. There are good reasons why an API gets no usage, and there’s a lot we can learn from how pies are made, sold, and consumed.
Don’t expect short-term tactics, but the timeless fundamentals from Adam DuVander’s lessons learned in developer relations, within a large enterprise, and as one of the earliest journalists covering APIs. You’ll learn the importance of knowing your competition (yup, even for internal APIs), sharing your vision, being ever-present, and helping developers get started fast. And don’t forget the delicious, flaky crust.
DuVander has seen the same approach work at database-as-a-service Orchestrate.io, internally at its parent company CTL.io, at his neighborhood bakery, and in discussions with hundreds of API providers over the last eight years.
How to keep a popular API up an running 24 hours a day, 365 days a year.
Presentation by Federico Hernandez, Västtrafik from Nordic APIs Copenhagen in May 2013.
State of APIs: API trends from Nordic APIs Copenhagen & SundsvallAndreas Krohn
An overview of where we are coming from, where we are and where we are going in the API world. Presentation from Nordic APIs in Copenhagen and Sundsvall in May 2013.
Pie for Sale: Timeless Lessons in API Advocacy (Adam DuVander)Nordic APIs
This is a session given by Adam Duvander at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
API that nobody uses is almost as sad as a pie that nobody eats. Yet, both of these occur every day. Regardless of whether your API is for partners, internal, or external usage, it needs an advocate to help it be adopted. There are good reasons why an API gets no usage, and there’s a lot we can learn from how pies are made, sold, and consumed.
Don’t expect short-term tactics, but the timeless fundamentals from Adam DuVander’s lessons learned in developer relations, within a large enterprise, and as one of the earliest journalists covering APIs. You’ll learn the importance of knowing your competition (yup, even for internal APIs), sharing your vision, being ever-present, and helping developers get started fast. And don’t forget the delicious, flaky crust.
DuVander has seen the same approach work at database-as-a-service Orchestrate.io, internally at its parent company CTL.io, at his neighborhood bakery, and in discussions with hundreds of API providers over the last eight years.
Public Transport APIs – How we are using and creating long lasting APIs at No...Nordic APIs
This is a session given by Urika Park and Petter Kvarnfors at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
Nobina is the largest bus operator in the Nordic countries. With about 10 000 employees and 3600 vehicles we strive to simplify the every day traveling for our customers by deliver simple, friendly and priceworthy public transport services.
In this session we share experiences from consuming the API’s from Trafiklab.se, which started in 2011 as a national initiative for public transport. One of our applications that consumes these API’s is the travel planner “Res i Sthlm”. This app has over 700 000 active end users in Stockholm who rely on it and Trafiklab for their daily transport, so we’re constantly working with reliability and quality with the data we expose.
We also talk about how we contribute to European Standards for API’s in vehicles, and how we implement these standards in our vehicles/busses in traffic – in other words our IoT-units on wheels. For instance, the European initiative ITxPT and the MQTT standard.
We share some thoughts and discuss with you what data we think Nobina and other bus operators will and should publish in the future from vehicles and other public transport data.
When dealing with public transport, it’s extremely important to work with a long term mindset, since consequences for travelers can be severe if every operator and type of transport implements different solutions and designs.
API Creation to Iteration without the FrustrationNordic APIs
This is a session given by Steve Rice at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
Once you have an API out in the wild (be it one that’s well designed, or one that grew organically), how do you evolve that API in the future? How do you take something everyone is using in a variety of ways, and distill those needs down into improvements?
This talk will walk through a recent major API version update we went through at PagerDuty from beginning to end. This will include details on what kinds of usage data we gathered, how we engaged with users of the API to understand what worked well and what didn’t, and how to break out of some of the existing antipatterns we had.
Audience members of this talk will be able to walk away with strategies they can apply to their own APIs (internal or external), testing patterns to consider, and ways to communicate engineering efforts in terms of business and customer value.
Lean and Mean – Authorization for kick-ass APIs (Jonas Markström)Nordic APIs
This is a session given by Jonas Markström at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
So you’ve decided to go down the API path. You’re fitting your enterprise’s architecture with the best in REST services, micro services, and API gateways. You’ve convinced your management that opening up your most precious assets – your data – to the outside world will have considerable benefits. Just imagine: your partners, customers, and contractors will all be able to interact with your systems.
Now, of course, there is just this little nagging doubt in your head: did you code that service correctly? Are you positive only the right people have access to the relevant data? Did you thoroughly test that 10,000-line code that implements access control?
Of course you didn’t… Because you didn’t hard-code the authorization. You went for Attribute Based Access Control, the weapon of choice of API Ninjas. Right?
In this talk, we will cover the basics of externalizing authorization using ABAC and how it can be applied to your APIs:
– Secure API endpoints no matter the technology
– Control access to API functionality
– Control access to data: dynamic data masking
– Implement access control as centrally-managed policies
– Reuse the access control across other technologies in the stack.
Benefits include:
– Leaner APIs
– Slashed development time
– Faster time-to-market
Automotive Grade APIs – designing for longevityNordic APIs
This is a session given by Henrik Segesten at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
In the automotive industry, the term “automotive grade” is in common use applied to hardware. It means that the hardware has been tested for longer durability and more extreme conditions than consumer grade hardware. But how does this apply to software and more specifically APIs?
This is a session given by Audrey Neveu at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
We know interactivity is the key to keep our user’s interest alive but we can’t reduce animation to UI anymore. Twitter, Waze, Slack… users are used to have real-time data in applications they love. But how can you turn your static API into a stream of data?
When talking about data streaming, we often think about WebSockets. But have you ever heard of Server-Sent Events? In this tools-in-action we will compare both technologies to understand which one you should opt for depending on your usecase and I’ll show you how we have been even further by reducing the amount of data to transfer with JSON-Patch.
And because real-time data is not only needed by web (and because it’s much more fun), I’ll show you how we can make drone dance on streamed APIs.
Versioning strategy for a complex internal API (Konstantin Yakushev)Nordic APIs
This is a session given by Konstantin Yakushev at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
API versioning is a very heated topic in API design world. Common approaches are passing version number explicitly (with a lot of fairly useless discussion on where exactly to put that number) or only introducing backwards-compatible changes.
When creating internal API for Badoo applications we found those approaches to be too limiting. Passing version number requires implementers to accommodate for all breaking changes when bumping version – even when it’s not required for business goals of that application at the time. Instead of driving value for business, application developers are in constant race to keep up with the API.
Never introducing incompatible changes is also not an option. After several feature redesigns (something that may happen at Badoo once every few weeks) protocol becomes bloated and half of the fields transmitted over the wire start being useless.
This talk is about our approach to versioning as part of client-server component negotiation. Client announces features and capabilities it supports and server replies with features status: whether they are enabled or disabled and whether they can be enabled by some user action (e. g. by buying some paid product).
Beside those componentized features, client also sends support flags such as SUPPORT_IMAGE_SIZE_VIA_URL which affects how API works. We use those flags where in typical API a version number bump would be required.
This approach allows both server and client to understand their current state and adjust their code accordingly – essentially, a tailor-made API for every client. Gathering data on feature and flag support among clients allows us to remove old code branches while continuing to evolve the API.
As a result, we are not afraid to change something when that change is required. Old clients continue to work while protocol rot is kept at low level.
In this talk I will give details on how exactly this versioning scheme work, how we test those changes, how and when we deprecate our old clients and note some stats and insights from using this scheme at Badoo for several years.
Lessons Learned from Building Enterprise APIs (Gustaf Nyman)Nordic APIs
This is a session given by Gustaf Nyman at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
In enterprises the majority of APIs are internal and may count in hundreds. APIs are often implemented in and used from a variety of languages and platforms, and legacy system and protocols are ever-present. As APIs are increasingly part of business strategies, API management becomes an important concern of the whole organisation.
Gustaf has spent more than 15 years building API infrastructure for enterprises. In this talk, he shares his thoughts on designing and implementing a long-lasting API management strategy.
TDD for APIs in a Microservice World (Michael Kuehne Schlinkert)Nordic APIs
This is a session given by Michael Kuehne at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
It can be tough to test an apparently simple service comprehensively. A microservice architecture brings a new level of complexity to the question “How can we validate that our API is working as intended?”
In this talk Michael will explain how to use test driven development for APIs and even further how TDD can drive an API Design towards a more usable design, and how to build an well-tested ecosystem of microservices.
This approach is applicable for different kinds of services (REST APIs, websockets, industrial protocols). Independent from the type of interface we always ran into similar problems when we build an ecosystem of services.
We have to deal with dependency, asynchronous behaviours, fallback mechanisms, endpoint versioning and sometimes even shared databases.
It’s not trivial to apply TDD to these kinds of problems cause you have to think of scenarios. But there are ways of identify these scenarios and to test them.
As an API specialist Michael worked with various clients designing, building, testing, maintaining and even redesigning private and public services. Based on his project experience he developed a practical approach to apply TDD to APIs in microservice ecosystems.
Introduction to The 6 Insights of API Practice (Bill Doerrfeld)Nordic APIs
This is a session given by Bill Doerrfeld at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
At Nordic APIs, our goal is to help businesses make smart tech decisions using APIs. To that end, via events and content Nordic APIs has treaded the business and technical sides to consider holistic best practices for providing an API. In this introductory Summit keynote talk, I’ll introduce what we’ve learned in the form of 6 core tenants of API practice which we’ve also designed this conference to address. Together they define a functional and evolving API:
Platformification: Becoming an API-first company means undergoing a platformification process. This represents a global trend that many argue needs to be adopted to keep your business competitive within the digital economy.
Strategy: Even before development begins, it’s important to consider your core API strategy. This is a defensible position that aligns your tech with platform goals, strategically exposing internal assets catered to an industry niche.
Business Models: APIs have the power to improve efficiency, reduce overhead cost, open up complementary revenue streams, extend R&D, or even alter an existing business model entirely. Thus, you’ll want to determine the right monetization method that improves overall business and leads to end profitability.
Security: With new major data breaches reaching the public ear every month, the importance of digital security can never be underestimated. For APIs, much of that lies in monitoring usage, access management, and identity control.
Design: No developer wants to use an API with an ugly developer portal, unintuitive URL structures, outdated technology, or terrible lag time. In order to keep your developer consumer happy, paint the API portal and overall developer experience with an aesthetic brush.
Marketing: In order to spark adoption, you need to have more than awesome functionality. I’ll review evangelism and discovery techniques you can use to get an API in the hands of more developer users.
We’ll look at specific successful implementations of these philosophies in the wild, and mention examples from our blog and eBook content that have brought in industry experts to share their insights. I’ll initiate dialogue and open the conference up to see where we’re heading. What you can get out of embracing the core tenants of API practice?
This slides deck about Microservices architecture and why do we need it. Architecture patterns which we need to follow doing Microservices architecture: Microservice, API Gateway, Service Discovery, Stateless/Shared-Nothing, Configuration/Service Consumption, Fault Tolerance (Circuit Breaker), Request Collapsing. And a bit about API Versioning
APIs as The Source of Truth (Zane Claes)Nordic APIs
This is a session given by Zane Claes at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
Too often, APIs are only consumed by mobile apps and external services. This leads to inconsistencies between web and API implementations of core business logic. This talk will discuss how Airbnb created an API infrastructure that also powers our website, to create a single source of truth.
This is a session given by Peter Drougge at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
In the fast paced world of cloud awesomeness there’s a new buzzword in town, and it’s called “serverless computing”.
Deposit 20 minutes of your time at this session and you’ll leave knowing how to leverage the power of Azure Functions to build and run an API without worrying about what server it’s hosted on or how it will scale.
API management solutions help enterprises manage, secure, and mediate API traffic, ensure that developers and partners are productive, and grow their API programs to meet the increasing demands of a digital world. APIU management capabilities including Backend as a Service (BaaS) solutions, analytics engines, and monetization enable developers to develop and extend apps with modern features, provide deep insights into the APIs, and allow API providers to monetize their APIs and developers to share in the revenue.
Co-Founder and CTO, Paul Fremantle and Solutions Architect, Senaka Fernando facilitated this workshop at Jax London 2014. The workshop illustrated how API management helps organizations participate in the API Economy; with the first half of the workshop looking at the overall landscape and approaches, while the second half focusing on using Open Source API Management tooling to expose, monitor and manage APIs.
MySQL Document Store -- SCaLE 17x PresentationDave Stokes
The MySQL Document store is a way to use MySQL as a NoSQL JSON Document Store so that you do not need to make queries with SQL, avoid having to set up relational tables before using the data, or need to wait for a DBA to set up tab;es
Public Transport APIs – How we are using and creating long lasting APIs at No...Nordic APIs
This is a session given by Urika Park and Petter Kvarnfors at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
Nobina is the largest bus operator in the Nordic countries. With about 10 000 employees and 3600 vehicles we strive to simplify the every day traveling for our customers by deliver simple, friendly and priceworthy public transport services.
In this session we share experiences from consuming the API’s from Trafiklab.se, which started in 2011 as a national initiative for public transport. One of our applications that consumes these API’s is the travel planner “Res i Sthlm”. This app has over 700 000 active end users in Stockholm who rely on it and Trafiklab for their daily transport, so we’re constantly working with reliability and quality with the data we expose.
We also talk about how we contribute to European Standards for API’s in vehicles, and how we implement these standards in our vehicles/busses in traffic – in other words our IoT-units on wheels. For instance, the European initiative ITxPT and the MQTT standard.
We share some thoughts and discuss with you what data we think Nobina and other bus operators will and should publish in the future from vehicles and other public transport data.
When dealing with public transport, it’s extremely important to work with a long term mindset, since consequences for travelers can be severe if every operator and type of transport implements different solutions and designs.
API Creation to Iteration without the FrustrationNordic APIs
This is a session given by Steve Rice at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
Once you have an API out in the wild (be it one that’s well designed, or one that grew organically), how do you evolve that API in the future? How do you take something everyone is using in a variety of ways, and distill those needs down into improvements?
This talk will walk through a recent major API version update we went through at PagerDuty from beginning to end. This will include details on what kinds of usage data we gathered, how we engaged with users of the API to understand what worked well and what didn’t, and how to break out of some of the existing antipatterns we had.
Audience members of this talk will be able to walk away with strategies they can apply to their own APIs (internal or external), testing patterns to consider, and ways to communicate engineering efforts in terms of business and customer value.
Lean and Mean – Authorization for kick-ass APIs (Jonas Markström)Nordic APIs
This is a session given by Jonas Markström at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
So you’ve decided to go down the API path. You’re fitting your enterprise’s architecture with the best in REST services, micro services, and API gateways. You’ve convinced your management that opening up your most precious assets – your data – to the outside world will have considerable benefits. Just imagine: your partners, customers, and contractors will all be able to interact with your systems.
Now, of course, there is just this little nagging doubt in your head: did you code that service correctly? Are you positive only the right people have access to the relevant data? Did you thoroughly test that 10,000-line code that implements access control?
Of course you didn’t… Because you didn’t hard-code the authorization. You went for Attribute Based Access Control, the weapon of choice of API Ninjas. Right?
In this talk, we will cover the basics of externalizing authorization using ABAC and how it can be applied to your APIs:
– Secure API endpoints no matter the technology
– Control access to API functionality
– Control access to data: dynamic data masking
– Implement access control as centrally-managed policies
– Reuse the access control across other technologies in the stack.
Benefits include:
– Leaner APIs
– Slashed development time
– Faster time-to-market
Automotive Grade APIs – designing for longevityNordic APIs
This is a session given by Henrik Segesten at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
In the automotive industry, the term “automotive grade” is in common use applied to hardware. It means that the hardware has been tested for longer durability and more extreme conditions than consumer grade hardware. But how does this apply to software and more specifically APIs?
This is a session given by Audrey Neveu at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
We know interactivity is the key to keep our user’s interest alive but we can’t reduce animation to UI anymore. Twitter, Waze, Slack… users are used to have real-time data in applications they love. But how can you turn your static API into a stream of data?
When talking about data streaming, we often think about WebSockets. But have you ever heard of Server-Sent Events? In this tools-in-action we will compare both technologies to understand which one you should opt for depending on your usecase and I’ll show you how we have been even further by reducing the amount of data to transfer with JSON-Patch.
And because real-time data is not only needed by web (and because it’s much more fun), I’ll show you how we can make drone dance on streamed APIs.
Versioning strategy for a complex internal API (Konstantin Yakushev)Nordic APIs
This is a session given by Konstantin Yakushev at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
API versioning is a very heated topic in API design world. Common approaches are passing version number explicitly (with a lot of fairly useless discussion on where exactly to put that number) or only introducing backwards-compatible changes.
When creating internal API for Badoo applications we found those approaches to be too limiting. Passing version number requires implementers to accommodate for all breaking changes when bumping version – even when it’s not required for business goals of that application at the time. Instead of driving value for business, application developers are in constant race to keep up with the API.
Never introducing incompatible changes is also not an option. After several feature redesigns (something that may happen at Badoo once every few weeks) protocol becomes bloated and half of the fields transmitted over the wire start being useless.
This talk is about our approach to versioning as part of client-server component negotiation. Client announces features and capabilities it supports and server replies with features status: whether they are enabled or disabled and whether they can be enabled by some user action (e. g. by buying some paid product).
Beside those componentized features, client also sends support flags such as SUPPORT_IMAGE_SIZE_VIA_URL which affects how API works. We use those flags where in typical API a version number bump would be required.
This approach allows both server and client to understand their current state and adjust their code accordingly – essentially, a tailor-made API for every client. Gathering data on feature and flag support among clients allows us to remove old code branches while continuing to evolve the API.
As a result, we are not afraid to change something when that change is required. Old clients continue to work while protocol rot is kept at low level.
In this talk I will give details on how exactly this versioning scheme work, how we test those changes, how and when we deprecate our old clients and note some stats and insights from using this scheme at Badoo for several years.
Lessons Learned from Building Enterprise APIs (Gustaf Nyman)Nordic APIs
This is a session given by Gustaf Nyman at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
In enterprises the majority of APIs are internal and may count in hundreds. APIs are often implemented in and used from a variety of languages and platforms, and legacy system and protocols are ever-present. As APIs are increasingly part of business strategies, API management becomes an important concern of the whole organisation.
Gustaf has spent more than 15 years building API infrastructure for enterprises. In this talk, he shares his thoughts on designing and implementing a long-lasting API management strategy.
TDD for APIs in a Microservice World (Michael Kuehne Schlinkert)Nordic APIs
This is a session given by Michael Kuehne at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
It can be tough to test an apparently simple service comprehensively. A microservice architecture brings a new level of complexity to the question “How can we validate that our API is working as intended?”
In this talk Michael will explain how to use test driven development for APIs and even further how TDD can drive an API Design towards a more usable design, and how to build an well-tested ecosystem of microservices.
This approach is applicable for different kinds of services (REST APIs, websockets, industrial protocols). Independent from the type of interface we always ran into similar problems when we build an ecosystem of services.
We have to deal with dependency, asynchronous behaviours, fallback mechanisms, endpoint versioning and sometimes even shared databases.
It’s not trivial to apply TDD to these kinds of problems cause you have to think of scenarios. But there are ways of identify these scenarios and to test them.
As an API specialist Michael worked with various clients designing, building, testing, maintaining and even redesigning private and public services. Based on his project experience he developed a practical approach to apply TDD to APIs in microservice ecosystems.
Introduction to The 6 Insights of API Practice (Bill Doerrfeld)Nordic APIs
This is a session given by Bill Doerrfeld at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
At Nordic APIs, our goal is to help businesses make smart tech decisions using APIs. To that end, via events and content Nordic APIs has treaded the business and technical sides to consider holistic best practices for providing an API. In this introductory Summit keynote talk, I’ll introduce what we’ve learned in the form of 6 core tenants of API practice which we’ve also designed this conference to address. Together they define a functional and evolving API:
Platformification: Becoming an API-first company means undergoing a platformification process. This represents a global trend that many argue needs to be adopted to keep your business competitive within the digital economy.
Strategy: Even before development begins, it’s important to consider your core API strategy. This is a defensible position that aligns your tech with platform goals, strategically exposing internal assets catered to an industry niche.
Business Models: APIs have the power to improve efficiency, reduce overhead cost, open up complementary revenue streams, extend R&D, or even alter an existing business model entirely. Thus, you’ll want to determine the right monetization method that improves overall business and leads to end profitability.
Security: With new major data breaches reaching the public ear every month, the importance of digital security can never be underestimated. For APIs, much of that lies in monitoring usage, access management, and identity control.
Design: No developer wants to use an API with an ugly developer portal, unintuitive URL structures, outdated technology, or terrible lag time. In order to keep your developer consumer happy, paint the API portal and overall developer experience with an aesthetic brush.
Marketing: In order to spark adoption, you need to have more than awesome functionality. I’ll review evangelism and discovery techniques you can use to get an API in the hands of more developer users.
We’ll look at specific successful implementations of these philosophies in the wild, and mention examples from our blog and eBook content that have brought in industry experts to share their insights. I’ll initiate dialogue and open the conference up to see where we’re heading. What you can get out of embracing the core tenants of API practice?
This slides deck about Microservices architecture and why do we need it. Architecture patterns which we need to follow doing Microservices architecture: Microservice, API Gateway, Service Discovery, Stateless/Shared-Nothing, Configuration/Service Consumption, Fault Tolerance (Circuit Breaker), Request Collapsing. And a bit about API Versioning
APIs as The Source of Truth (Zane Claes)Nordic APIs
This is a session given by Zane Claes at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
Too often, APIs are only consumed by mobile apps and external services. This leads to inconsistencies between web and API implementations of core business logic. This talk will discuss how Airbnb created an API infrastructure that also powers our website, to create a single source of truth.
This is a session given by Peter Drougge at Nordic APIs 2016 Platform Summit on October 26th, in Stockholm Sweden.
Description:
In the fast paced world of cloud awesomeness there’s a new buzzword in town, and it’s called “serverless computing”.
Deposit 20 minutes of your time at this session and you’ll leave knowing how to leverage the power of Azure Functions to build and run an API without worrying about what server it’s hosted on or how it will scale.
API management solutions help enterprises manage, secure, and mediate API traffic, ensure that developers and partners are productive, and grow their API programs to meet the increasing demands of a digital world. APIU management capabilities including Backend as a Service (BaaS) solutions, analytics engines, and monetization enable developers to develop and extend apps with modern features, provide deep insights into the APIs, and allow API providers to monetize their APIs and developers to share in the revenue.
Co-Founder and CTO, Paul Fremantle and Solutions Architect, Senaka Fernando facilitated this workshop at Jax London 2014. The workshop illustrated how API management helps organizations participate in the API Economy; with the first half of the workshop looking at the overall landscape and approaches, while the second half focusing on using Open Source API Management tooling to expose, monitor and manage APIs.
MySQL Document Store -- SCaLE 17x PresentationDave Stokes
The MySQL Document store is a way to use MySQL as a NoSQL JSON Document Store so that you do not need to make queries with SQL, avoid having to set up relational tables before using the data, or need to wait for a DBA to set up tab;es
MySQL Without the SQL - Oh My! August 2nd presentation at Mid Atlantic Develo...Dave Stokes
MySQL Document Store allows you to use MySQL as a JSON Document Databases without needing to set up relational tables, normalize data, or use Structured Query Language.
Data Con LA 2020
Description
MySQL is an ubiquitous relational database that can also be used as a NoSQL JSON document store. That means you do not need a DBA to set up tables - just connect and start saving data. And you can access the NoSQL data from the SQL side or the SQL data from the NoSQL side which gives you the best of both the SQL and NoSQL worlds on the same server.
*Learn how to use the X DevAPI protocol for CRUD based operations
*See how to use JSON_TABLE() to turn unstructured data temporarily structured
*Understand how JSON really makes your relational database faster
*How to extract JSON data into a relational column
Speaker
Dave Stokes,Oracle, MySQL Community Manager
Microservices in GO - Massimiliano Dessì - Codemotion Rome 2017Codemotion
In this talk we'll see how to write a cloud native microservice with Go language, the microservices will be: Cloud native A twelve factor app Scalable with the GO built in concurrency Monitored with a distributed tracing system to check the latency Testable with a load test during the development Communications with different protocols.
Experimental Alternative Technological Stack. Web is terrible... We are going to remove everything except JavaScript.
• Impress (Highload Cloud Application Server for Node.js)
https://github.com/metarhia /Impress
• JSTP (JavaScript as a Transport Protocol)
https://github.com/ metarhia/JSTP
• Global Storage (JavaScript data structures as in-memory DBMS)
https://github.com/metarhia /GlobalStorage
• Console (is an Application Browser, no HTML, DOM, CSS, etc.)
https://github.com/metarhia /Console
How to write clean & testable code without losing your mindAndreas Czakaj
If you create software that is to be developed continuously over several years you'll need a sustainable approach to code quality.
In our early days of AEM development, however, we used to struggle with code that is rigid, hard to test and full of LOG.debug calls.
In this talk I will share some development best practices we have found that really work in actual AEM based software, e.g. to achieve 100% code coverage and provide high confidence in the code base.
Spoiler alert: no new libraries, frameworks or tools are required - once you know the ideas, plain old TDD and the S.O.L.I.D. principles of Clean Code will do the trick.
by Andreas Czakaj, mensemedia Gesellschaft für Neue Medien mbH
Presented at the adaptTo() 2017 conference in Berlin (https://adapt.to/2017/en/schedule/how-to-write-clean---testable-code-without-losing-your-mind.html).
Presentation video can be found on YouTube (https://www.youtube.com/watch?v=JbJw5oN_zL4)
MongoDB Europe 2016 - Debugging MongoDB PerformanceMongoDB
Asya is back, and so is Sherlock Holmes and his techniques to gather and analyze data from your poorly performing MongoDB clusters. In this advanced talk we take a deep look at all the diagnostic data that lives inside MongoDB - how to interrogate and interpret it to help you solve those frustrating performance bottlenecks that we all face occasionally.
How I Built Bill, the AI-Powered Chatbot That Reads Our Docs for Fun , by Tod...Nordic APIs
A presentation given by Todd Kerpelman, Developer Advocate at Plaid, at our 2024 Austin API Summit, March 12-13.
Session Description: Have you ever thought about building your own chatbot to help developers be more successful using your APIs? Well, we made one for Plaid’s documentation site, and in this talk, I’ll cover some of the things we learned!
This presentation will cover topics like:
– How does it work? What does it mean to “train” a bot on your docs?
– Setting appropriate expectations: Do you still need to write documentation? Do you still need a support team?
– The trade-offs around building your own vs. buying a 3rd party solution
– Some decisions around the underlying tech
– How to build a decent “conversational mode” so you can ask follow-up questions
– How you evaluate the quality of a chatbot, and some surprises we ecountered along the way
– What do you do when things go wrong?
– Security considerations
And much more! Actually, probably not that much more. That already sounds like a lot.
The Art of API Design, by David Biesack at ApitureNordic APIs
A presentation given by David Biesack, Chief API Officer at Apiture, at our 2024 Austin API Summit, March 12-13.
Session Description: API Design is truly an art. While ChatGPT can spit out seemingly detailed APIs, there is still much to be said for well-crafted, consistent APIs designed by organic intelligence, in a broader context, with the consumer and Developer Experience in mind.
A good (or dare we dream, great) Developer Experience (DX) is an important aspect of API design and the success of your API program. Attendees will grok the interplay of API design, patterns, and language constraints and limitations. See how and why artful API Design Matters to DX and "good" API outcomes, and why fluency in the myriad languages of APIs matters. Learn how choosing guiding principles can shape all your APIs for success. Learn how to stay relevant as an API designer when the API generating robots are breathing down your neck.
ABAC, ReBAC, Zanzibar, ALFA… How Should I Implement AuthZ in My APIs? by Dav...Nordic APIs
A presentation given by David Brossard, CTO at Axiomatics, at our 2024 Austin API Summit, March 12-13.
Session Description: So you've just built your cool new API and figured out the authentication part. You're even using OAuth for access delegation, scopes, and claims. So, you're good, right? Well what about fine-grained authorization? What about OWASP's #1 security threat, broken access control? How do you handle that? Maybe you need an authorization framework to help with that. But which one? Is ABAC the way to go? Policies? Graphs? In this presentation, we'll give you the tools to understand what authorization for APIs entails, what options you have, and how to successfully implement a secure authorization strategy for your APIs. We will cover approaches such as ALFA, ReBAC, and Zanzibar and illustrate with a live demo.
Crafting a Cloud Native API Platform to Accelerate Your Platform Maturity - B...Nordic APIs
A presentation given by Budhaditya Bhattacharya, Developer Advocate at Tyk, at our 2024 Austin API Summit, March 12-13.
Session Description: APIs and microservices are powering domain-driven design architectures and have become the fabric of modern cloud-native applications. However, focusing on technology isn't enough - there is a need for a synergy between people, processes, and tools.
Based on the CNCF platform maturity model, we will look to bridge the gap between an org's current and desired platform maturity level when creating cloud-native API platforms. We'll discuss:
1. The platform team model - team topologies and key roles for developing internal API platforms
2. Processes like platform discovery, jobs-to-be-done analysis, and continuous feedback loops to understand and meet developer needs
3. Applying a "platform as a product" mindset to measure and communicate platform success
4. Architecting for discoverability, security, observability and integration capabilities 5. The role of technologies like service meshes, API gateway, identity management, internal developer portals and OpenAPI specifications
The Federated Future: Pioneering Next-Gen Solutions in API Management - Marku...Nordic APIs
A presentation given by Markus Müller, CTO at APIIDA, at our 2024 Austin API Summit, March 12-13.
Session Description: In an era where digital transformation is pivotal, the management and governance of APIs have emerged as critical components in the technological infrastructure of businesses. "The Federated Future: Pioneering Next-Gen Solutions in API Management" is a forward-looking talk that delves into the evolving landscape of API governance, with a particular focus on Federated API Management as a groundbreaking approach.
Over the course of this presentation, we will explore the paradigm shift from traditional, centralized API management towards a more dynamic, federated model. This approach not only offers scalability and flexibility but also fosters innovation by enabling diverse teams to collaboratively manage APIs while adhering to consistent governance policies.
Key topics include:
- The current challenges in API governance and how federated management addresses these.
- The principles and architecture of Federated API Management, distinguishing it from traditional models.
- Real-world implications of adopting a federated approach, including case studies that illustrate its transformative impact on businesses.
- Strategies for implementing Federated API Management, focusing on best practices for seamless integration.
- The future outlook of API governance, anticipating emerging trends and technologies.
API Authorization Using an Identity Server and Gateway - Aldo Pietropaolo, SGNLNordic APIs
A presentation given by Aldo Pietropaolo, Director of Solutions Engineering at SGNL, at our 2024 Austin API Summit, March 12-13.
Session Description: Securing APIs and ensuring you are protected from threats by implementing authentication and authorization while keeping the request context intact can be challenging. This session will show us how to leverage SGNL, Curity, and the Kong API Gateway to protect fictitious patient records. The session will be a technical session focused on the architecture and integration points for implementing continuous access management.
API Discovery from Crawl to Run - Rob Dickinson, GraylogNordic APIs
A presentation given by Rob Dickinson, VP of Engineering at Graylog, at our 2024 Austin API Summit, March 12-13.
Session Description: Discovering the attack surface presented by your APIs is the first step to improving API security. But APIs are fundamentally dark and constantly changing, which presents serious challenges for security teams trying to assess and manage new risks. There are several reasonable ways to perform API discovery, but each has its own tradeoffs and implications about what is actually being counted. This talk covers taking an API discovery program from start to best-of-breed, and strategies for measuring and monitoring your API attack surface.
Productizing and Monetizing APIs - Derric Gilling, MoseifNordic APIs
A presentation given by Derric Gilling, CEO of Moseif, at our 2024 Austin API Summit, March 12-13.
Session Description: The talk would target product owners looking to turn APIs into revenue centers. Specifically, how to price and package APIs, different strategies around prepaid, postpaid, and PAYG billing, and how to choose the right metric to charge, etc. Then, we’ll chat on the go-to-market to drive developer adoption.
Securely Boosting Any Product with Generative AI APIs - Ruben Sitbon, SipiosNordic APIs
A presentation given by Ruben Sitbon, Lead Solutions Architect at Sipios, at our 2024 Austin API Summit, March 12-13.
Session Description: ChatGPT has been a tidal wave, changing forever the way people and companies perceive the value of Artificial Intelligence. Many startups have launched products with ChatGPTI at its core, innovative SaaS players have all integrated Generative AI extensions or plugins, but it is now clear that users will be expecting more and more Generative AI to boost the features of products they use on a daily basis.
In this talk, I will describe how a framework relying on Generative AI in-house APIs that allows:
- Easily « boosting » any product feature with Generative AI
- Improving the answers through a « trainer API » that allows experts to improve the accuracy and tone of the model
- Bundling security and continuous compliance in the APIs to enjoy the benefits even within risk averse large corporates.
Security of LLM APIs by Ankita Gupta, Akto.ioNordic APIs
A presentation given by Ankita Gupta, Co-Founder and CEO, Akto.io, at our 2024 Austin API Summit, March 12-13.
Session Description: In this session, I will talk about API security of LLM APIs, addressing key vulnerabilities and attack vectors. The purpose is to educate developers, API designers, architects and organizations about the potential security risks when deploying and managing LLM APIs.
1. Overview of Large Language Models (LLMs) APIs
2. Understanding LLM Vulnerabilities:
- Prompt Injections
- Sensitive Data Leakage
- Inadequate Sandboxing
- Insecure Plugin Design
- Model Denial of Service
- Unauthorized Code Execution
- Input attacks
- Poisoning attacks
3. Best practices to secure LLM APIs from data breaches
I will explain all the above using real life examples.
I'm an API Hacker, Here's How to Go from Making APIs to Breaking Them - Katie...Nordic APIs
A presentation given by Katie Paxton-Fear, API Security Educator, Traceable AI, at our 2024 Austin API Summit, March 12-13.
Session Description: Have you ever wanted to be the villain or anti-hero? In this talk, we'll cover how to hack APIs, with permission, of course. First, we'll look at the tools of the trade for API hackers, some of the most common security vulnerabilities and how we test for them, and finally, I'll tell some of my API hacking stories. The aim of the session will be to learn a little API hacking and encourage people to have a go at API hacking themselves. Participants will also join me as I hack live, giving suggestions for the next steps, for an interactive and engaging session.
Unleashing the Potential of GraphQL with Streaming Data - Kishore Banala, Net...Nordic APIs
A presentation given by Kishore Banala, Senior Software Engineer, Netflix, at our 2024 Austin API Summit, March 12-13.
Session Description: Extend the advantages of GraphQL beyond the UI layer by creating data streams that seamlessly transfer data from Federated GraphQL to your preferred destination. This presentation explores the myriad use cases that can be unleashed, such as Search, Analytics etc., sparing you from the complexity of extensive ETL jobs. Join us for an in-depth exploration of the advantages that arise from seamlessly connecting GraphQL with data streams, opening new dimensions of efficiency and capability.
Reigniting the API Description Wars with TypeSpec and the Next Generation of...Nordic APIs
A presentation given by Gareth Jones, API Architect at Microsoft, at our 2024 Austin API Summit, March 12-13.
Session Description: Didn't the API description wars end in 2017 when we all agreed that OAS was the way forward?
Yes, and yet how satisfied with your API descriptions are you? Are they thousands of lines of hard to read yaml or JSON? When someone makes a change, is it easy to review for correctness and completeness? Do visual tools make this easier? Do they support change management?
I'll make the case that the next generation of more abstract DSLs for defining APIs such as Smithy from Amazon and TypeSpec, open sourced by Microsoft, move us back to a more intentional approach to design and give us the opportunity to highlight the business characteristics that matter most at design-time.
Establish, Grow, and Mature Your API Platform - James Higginbotham, LaunchAnyNordic APIs
A presentation given by James Higginbotham, Executive API Consultant, LaunchAny, at our 2024 Austin API Summit, March 12-13.
Session Description: Building and growing an API platform takes more than building and organizing your APIs. It requires understanding the needs of your ecosystem, establishing lightweight processes that drive discoverability, providing the resources for self-service enablement, and delivering a federated API coach program to scale your efforts. This talk will explore the practices and patterns implemented by global organizations that will help your API ecosystem shift from a functional program to a transformational API platform.
Inclusive, Accessible Tech: Bias-Free Language in Code and Configurations - A...Nordic APIs
A presentation given by Adrienne Moherek, Developer Experience Technical Leader, Cisco, at our 2024 Austin API Summit, March 12-13.
Session Description: Heard of suss? You can suss out more information or you can find someone’s information to be suss. “Suss” shows the flexibility of language. It’s an ongoing process to change how we use certain words. It’s important to choose words carefully to convey the correct meaning and avoid harmful subtext or exclusion. Let’s explore some of the tools and triage methods that it takes from an engineering viewpoint to make bias-free choices. How can you ensure that biased words do not sneak into code, UI, docs, configurations, or our everyday language? First, let’s walk through how to take an inventory of assets from code to config files to API specifications to standards. Next, by placing those findings into categories, prioritize the work to substitute with inclusive alternatives. Let’s examine some examples using both API and code assets. Next is a demonstration of how to automate analyzing your source code or documentation with a linter, looking for patterns based on rules that are fed into the tool. What’s in the future for these efforts? Inclusive language should expand beyond English and North America efforts. To do so, let’s organize the work with automation tooling, as engineers do.
Going Platinum: How to Make a Hit API by Bill Doerrfeld, Nordic APIsNordic APIs
A presentation given by Bill Doerrfeld, Editor in Chief of Nordic APIs, at our 2024 Austin API Summit, March 12-13.
Session Description: As it turns out, making a hit API is a lot like making a hit music album. You have to find a niche, you need good naming, and you need quality content. Also, on the production side, design, style, experience, and collaboration all matter a lot. At the end of the day, both are products, requiring the right management tools, marketing know-how, and infrastructure to scale. In this SXSW-inspired opening keynote, I'll look into the parallels between the two endeavors, providing a fun and informative look into specific things API providers should be considering on their journey toward becoming API platform rockstars.
Getting Better at Risk Management Using Event Driven Mesh Architecture - Ragh...Nordic APIs
A presentation given by Raghavan Sadagopan, Sr. Director from CapitalOne & Lakshmi Narayana, Sr. Lead Software Engineer from CapitalOne, at our 2024 Austin API Summit, March 12-13.
Session Description: Managing Risk is critical to the success of an organization. Managing Risks starts with identifying potential Risks which in the digital world are signals emanating from varying source systems. Identifying potential risks real-time enables organizations to mitigate / better prepare for potential exposures. The session will share our point of view on implementing an API centric event mesh architecture that routes events in real-time through a scalable and resilient cloud-native service on AWS.
GenAI: Producing and Consuming APIs by Paul Dumas, GartnerNordic APIs
A presentation given by Paul Dumas, Senior Director Analyst at Gartner, at our 2024 Austin API Summit, March 12-13.
Session Description:
GenAI will be, well, generating APIs. We are entering the era where software creates software. It will develop APIs faster than humans are capable of. Humans cannot compete with this compute power. How do we marshal this power, govern what it produces, and leverage it to support our business objectives and strategies? We will become more dependent on the capabilities we have as humans that elude machines. This talk provides insight to software leaders about the challenges of leading and managing this new software development power. The key lies in skills that are unique to humans: foresight, intuition, and agility.
The SAS developer portal –developer.sas.com 2.0: How we built it by Joe Furb...Nordic APIs
A presentation given by Joe Furbee, Developer Advocate and Developers Communities Manager at SAS Institute, at our 2024 Austin API Summit, March 12-13.
Session Description: Sure, we could have hired someone to (re)create our developer portal, developer.sas.com. However, we wanted the freedom to build our portal from the ground up. But, it takes more than an API architect and a developer advocate to create a modern, interactive developer experience. This session provides an overview of the steps we took to relaunch the SAS AI and analytics platform developer portal. Who was involved? How did we accomplish what we wanted to build? We’ll explore the stakeholders involved, the importance of open-source technologies, and why focusing on the developer’s perspective matters. This is not a marketing pitch to promote SAS services. Instead, it’s a detailed look at the process we followed to deploy our new developer portal.
How Netflix Uses Data Abstraction to Operate Services at Scale - Vidhya Arvin...Nordic APIs
A presentation given by Vidhya Arvind, Staff Software Engineer, Netflix, at our 2024 Austin API Summit, March 12-13.
Session Description: At Netflix, Data abstraction plays a pivotal role in hosting 100s of use cases that scale, they are widely adopted and depended on by mission-critical systems. In this talk, I show how to design reliable APIs and layout data for Key-Value services for petabyte-scale datasets. Key-value service uses a control plane and data plane to abstract the data, uses some novel techniques to reliably store and safely scale the service to 100s of instances.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
19. Write program that do
one thing and
do it well
Unix philosophy
Doug McIlroy
20. Eric Raymond’s 17 Unix
Rules
...
Rule of Modularity
Rule of Composition
Rule of Separation
Rule of Simplicity
Rule of Parsimony
Rule of Robustness
...
47. Statistik för Sun 2013-05-19
============================
Antal sökningar
---------------
Searches: 918967
Klienter
--------
WEB: 84957 (9.245%)
IPHONE: 414562 (45.112%)
IPAD: 1554 (0.169%)
ANDROID: 110725 (12.049%)
REST: 306560 (33.359%)
XHTML: 609 (0.066%)
48. Typ av förfrågningar
--------------------
XMLCON (till/från eller till och från address): 347464 (37.810%)
XMLSTATIONBOARD (nästa tur): 326501 (35.529%)
XMLCON-BASIC (till och från hållplats): 117693 (12.807%)
XMLLOCATING (sökning med gps från mobilen): 110491 (12.023%)
XMLJOURNEY: 6815 (0.742%)
XMLTARIFF (prisförfrågning): 5678 (0.618%)
XMLGIS: 3871 (0.421%)
XMLSIMPLEHANDLESTRING (SMS): 454 (0.049%)