Skip to content

Commit 828fbf3

Browse files
committed
Smaller content updates and Config-setting
1 parent 90493e4 commit 828fbf3

7 files changed

+110
-6
lines changed

docs/data-modeling-offline-first-apps.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ For devices that sync, design entities with **clear sync ownership**:
9696
"@context":"https://schema.org",
9797
"@type":"TechArticle",
9898
"headline":"Data Modeling for Offline-First Apps",
99-
"description":"Patterns and tips for modeling data in ObjectBox for offline-first mobile and edge apps.",
99+
"description":"Patterns and tips for modeling data for offline-first mobile and edge apps.",
100100
"about":["ObjectBox","data modeling","offline-first","relations","indexes","converters"],
101101
"license":"https://creativecommons.org/licenses/by/4.0/"
102102
})}

docs/on-device-vector-database-sync.mdx

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,3 +80,23 @@ Adopting an on-device vector database with data synchronization delivers transfo
8080

8181
The future of intelligent applications isn't just in the cloud; it's in the seamless, symbiotic relationship between the cloud and the edge; especially for AI applications. By combining the local processing power of on-device vector search with the connective tissue of real-time data sync, we can build a new class of truly smart, resilient, and context-aware applications - that work offline as well as online and can support your workers anytime, anyplace in realtime. On top, this approach is way more resourceful, and therefore saves energy and thus monetary and environmental costs, while also empowering you to keep data secure and private on local devices.
8282

83+
<script type="application/ld+json">
84+
{
85+
"@context": "https://schema.org",
86+
"@type": "BlogPosting",
87+
"mainEntityOfPage": {
88+
"@type": "WebPage",
89+
"@id": "https://dev.objectbox.io/on-device-vector-database-sync"
90+
},
91+
"headline": "How On-Device Vector Databases with Data Sync Are Revolutionizing Field Services",
92+
"description": "Learn how an on-device vector database like ObjectBox with real-time data sync enables powerful, offline-first AI applications for industries like field services.",
93+
"keywords": "Edge AI, Vector Database, Data Sync, Offline-First, On-Device AI",
94+
"datePublished": "2025-09-10T11:47:46+02:00",
95+
"dateModified": "2025-09-10T11:53:47+02:00",
96+
"author": {
97+
"@type": "Person",
98+
"name": "Dr. Vivien Dollinger",
99+
"url": "https://www.linkedin.com/in/vivien-dollinger/"
100+
}
101+
}
102+
</script>

docs/realm-to-objectbox-api-mapping.mdx

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,3 +77,23 @@ If your migration targets vector/similarity search, ObjectBox supports **on-devi
7777
- [box.get()](./box-get-method.mdx)
7878
- [box.remove()](./box-remove-method.mdx)
7979

80+
<script type="application/ld+json">
81+
{
82+
"@context": "https://schema.org",
83+
"@type": "TechArticle",
84+
"mainEntityOfPage": {
85+
"@type": "WebPage",
86+
"@id": "https://dev.objectbox.io/migrate/realm-to-objectbox/api-mapping"
87+
},
88+
"headline": "Realm → ObjectBox API Mapping",
89+
"description": "Quick reference mapping Realm APIs to ObjectBox equivalents across languages.",
90+
"keywords": "ObjectBox, Realm, migration, API mapping, reference",
91+
"datePublished": "2025-07-10T11:56:15+02:00",
92+
"dateModified": "2025-09-10T11:56:15+02:00",
93+
"author": {
94+
"@type": "Organization",
95+
"name": "ObjectBox",
96+
"url": "https://dev.objectbox.io/"
97+
}
98+
}
99+
</script>

docs/realm-to-objectbox-migration.mdx

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,4 +94,25 @@ Unless you mark the ID as **assignable** (e.g., `@Id(assignable = true)` in Java
9494
- [Transactions](./transactions.mdx)
9595
- [box.put()](./box-put-method.mdx)
9696
- [box.get()](./box-get-method.mdx)
97-
- [box.remove()](./box-remove-method.mdx)
97+
- [box.remove()](./box-remove-method.mdx)
98+
99+
<script type="application/ld+json">
100+
{
101+
"@context": "https://schema.org",
102+
"@type": "TechArticle",
103+
"mainEntityOfPage": {
104+
"@type": "WebPage",
105+
"@id": "https://dev.objectbox.io/migrate/realm-to-objectbox/guide"
106+
},
107+
"headline": "Realm → ObjectBox Migration Guide",
108+
"description": "Step-by-step guide to migrate data and code from Realm to ObjectBox",
109+
"keywords": "ObjectBox, Realm, Realm DB, Data Sync, MongoDB, MongoDB Atlas Device Sync, migration, guide",
110+
"datePublished": "2025-03-15T09:00:00+01:00",
111+
"dateModified": "2025-09-09T14:30:00+02:00",
112+
"author": {
113+
"@type": "Organization",
114+
"name": "ObjectBox",
115+
"url": "https://dev.objectbox.io/"
116+
}
117+
}
118+
</script>

docs/technical-realm-vs-objectbox-audit.mdx

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -434,4 +434,25 @@ The emergence of ObjectBox's vector search capabilities positions it uniquely fo
434434

435435
### 5.4 Conclusion
436436

437-
This technical audit, grounded in official documentation verification, reveals that while both RealmDB and ObjectBox are capable local databases, their strategic trajectories have diverged significantly. ObjectBox's continued investment in synchronization, performance optimization, and AI capabilities, combined with Realm's sync deprecation, makes ObjectBox the more future-proof choice for most modern application requirements. The decision ultimately depends on specific project needs, but the synchronization factor alone makes ObjectBox the recommended choice for any application with current or potential future sync requirements.
437+
This technical audit, grounded in official documentation verification, reveals that while both RealmDB and ObjectBox are capable local databases, their strategic trajectories have diverged significantly. ObjectBox's continued investment in synchronization, performance optimization, and AI capabilities, combined with Realm's sync deprecation, makes ObjectBox the more future-proof choice for most modern application requirements. The decision ultimately depends on specific project needs, but the synchronization factor alone makes ObjectBox the recommended choice for any application with current or potential future sync requirements.
438+
439+
<script type="application/ld+json">
440+
{
441+
"@context": "https://schema.org",
442+
"@type": "TechArticle",
443+
"mainEntityOfPage": {
444+
"@type": "WebPage",
445+
"@id": "https://dev.objectbox.io/migrate/technical-realm-vs-object-box-audit"
446+
},
447+
"headline": "Technical Realm Vs Object Box Audit",
448+
"description": "A Technical Audit of RealmDB and ObjectBox; perfect for understanding the similarities, differences, and unique advantages and disadvantages the two databases bring to the table.",
449+
"keywords": "Realm, Realm DB replacement, MongoDB Realm alternative, MongoDB Realm Device Sync, migration",
450+
"datePublished": "2025-08-20T10:00:00+01:00",
451+
"dateModified": "2025-09-09T16:45:00+02:00",
452+
"author": {
453+
"@type": "Organization",
454+
"name": "ObjectBox",
455+
"url": "https://dev.objectbox.io/"
456+
}
457+
}
458+
</script>

docs/transactions.mdx

Lines changed: 22 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -200,4 +200,25 @@ with store.write_tx():
200200
## See also
201201
- [box.put() – Inserting and updating objects (implicitly transactional)](./box-put-method.mdx)
202202
- [box.remove() – Deleting objects (implicitly transactional)](./box-remove-method.mdx)
203-
- [Official Docs on Transactions for more in-depth, version-specific details from the canonical docs](https://docs.objectbox.io/transactions)
203+
- [Official Docs on Transactions for more in-depth, version-specific details from the canonical docs](https://docs.objectbox.io/transactions)
204+
205+
<script type="application/ld+json">
206+
{
207+
"@context": "https://schema.org",
208+
"@type": "TechArticle",
209+
"mainEntityOfPage": {
210+
"@type": "WebPage",
211+
"@id": "https://dev.objectbox.io/api-facts/transactions"
212+
},
213+
"headline": "API Fact: Using Transactions in ObjectBox",
214+
"description": "Learn how to use transactions in ObjectBox with store.runInTx for atomic, consistent, and high-performance database operations.",
215+
"keywords": "ObjectBox transactions, atomic operations, database transaction, ACID, runInTx, bulk update performance",
216+
"datePublished": "2025-05-20T11:00:00+02:00",
217+
"dateModified": "2025-09-10T09:15:00+02:00",
218+
"author": {
219+
"@type": "Organization",
220+
"name": "ObjectBox",
221+
"url": "https://dev.objectbox.io/"
222+
}
223+
}
224+
</script>

docusaurus.config.ts

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,8 @@ const config: Config = {
4747
docs: {
4848
routeBasePath: '/',
4949
sidebarPath: require.resolve('./sidebars.ts'),
50-
editUrl: 'https://github.com/objectbox/objectbox-dev-site/blob/main/', // needs changing!
50+
editUrl: 'https://github.com/objectbox/objectbox-dev-site/edit/main/',
51+
5152
},
5253
blog: false,
5354
theme: {
@@ -73,7 +74,7 @@ const config: Config = {
7374
title: 'How to use ObjectBox for Edge AI, Mobile AI, Embedded AI, and Offline Apps with real-time sync in any setting',
7475
logo: {
7576
alt: 'ObjectBox Logo',
76-
src: 'img/objectbox-logo.jpg',
77+
src: 'img/objectbox-logo-rect.jpg',
7778
srcDark: 'img/objectbox-logo-dm.png',
7879
},
7980
items: [

0 commit comments

Comments
 (0)